@Tina_Sea Probably because I don't talk as much

Hahah nah I don't know really I think it's just not as popular and a lot of people have retired from TWP

@Twyxz I just start in here when that happened it looks like a few of them werent very happy

@Tina_Sea Yeah a lot of people didn't agree with what had been happening

@Twyxz Most of the regulars I knew from a couple of years back seem to have retired. Happens to most communities I guess.

hello

hi

started a private room if you like

it's fine also here

Ok, fine

well

thank you in advance for your time

so as i understand you screwed bad, you are in a weak position, and besides things kinda stink in management

well

during the last meeting my senior told me that he saw an improvement

so I wouldn't say it's a non-recoverable position

I just paid extra attention to everything

but I fell kinda like if I am biking with the safety wheels on

i know the feeling, its not nice..

while maybe I could learn a lot more without those safety wheels

anyways

my manager is not a developer

so I can understand that for him there is no difference between not being able to do something for being not skilled, or not motivated enough

he just doesn't get it

but I think that if I say it I would get into an even worse position

it would just read as "I didn't like it, so I didn't do it well"

it sounds really bad to say

yea, to be honnest, you just have to play it like this is your fault, even if the situation is a bit more complex than that

I think it is my fault, even if not totally

i once got blamed really hard for sending things to Q/A without prior testing, despite being otherwise a skilled dev

it's my first job and I don't know what is common in other companies

what is common is to test before send others to test, you won't cut past that

but let's say that you only modify one line of code

you test, still

which is the 1% of the task

and 99% is testing + configuration

yeah

so i think you should anticipate that and say "hey can we include xyz change with this task to only have one test round, this would be faster"

i dont see any better way, on the short run at least

well

we have something like 20 apps and 11 devs

so most of the times we only have one task per app

let's say we have to change all of our banner

every team does it for 4-5 apps

and that's what we do in half sprint

frankly, taking half a sprint to change a banner is pathological, you must know that

well

nobody seems to be concerned about that

I am in a team of 3 people

it's considered normal ;(

I don't know... I would be curious to know how it is in other companies

I would be trying to change job if I were you, but that doesn't mean you would be done with that one, just a backup plan

yeah

this sounds like the best option for me

How is it in your company?

does it happen that you don't write one single line of code in an entire day?

well, im a backend dev, and tests are very long, but usually the requested changes are somewhat complex

it doesn't happen no

when i say long i mean 20 mins, and besides, you can still code when the test is running

that's what I'm thinking, that maybe I would perform well if the coding part of the tasks was bigger

I agree, and if your management is aware of how long tests take, they should agree, but that's the part where they are faulty

they agreed that they want to automate the tests

but they don't want to let all developers contribute to the tests

this is nonsensical, frankly

only a very experienced developer who likes to program a lot in his free time

everyone should test his own code

would start configuring the tests

and then after an initial "trial period"

we will be also writing tests

would you want to wait that long ?

well

I think I have no choice: I am a junior with only one year of experience. I can try to find more jobs but my chances are low, as most of the vacancies require 3 years of experience

I can still try though

you found once, why not twice ?

well

I was living in Italy

I am an iOS developer and I am looking for iOS dev jobs specifically

and I jumped to the first iOS dev that I got, which was in the Netherlands

now since I already have an apartment and everything

I want to find another job but close to where I live

in the Netherlands

and you're a bit in a niche...

so let's say that I am filtering out like 99% of the world's available jobs for me

it was easier when I had no requirements and I was willing to move to any country

but if things get bad I can also accept to move away from the Netherlands

it's just not my first option now

ok, i see

so this is clear, you have to work hard to make things more rational and manageable

in a "sane" dev environment you are about 50/50 testing and developing

well it also depends on the period

this period was the worst

what would you want to progress on ? You mentionned backend, but you also said you want to work as iOS specialist, so ?

I'd like to progress as an iOS specialist with some backend knowledge. With the recent developments it's possible to write the backend in the same language as the frontend (swift), but we still have everything in PHP

so there will be a transition and we will rewrite our backend services in Swift

but I fear that also hear all the interesting tasks will go to the "tiger team" and to the tech lead

and "common developers" will not learn a lot on it

does the backend guy is a swift specialist ? It seems like he could use your help though, a rewrite is a lot of work

he is kinda full stack, I'd say

yes I think (and also hope) that he will delegate a lot to the teams

anyways I can still check his commits between one task and another

ok, thank you very much for your time and your suggestions. I am going to bed now

goodbye

you need to find motivating things about this job, anyway, if that's not the work or learning, it has to be colleagues, anything

good night then