2 ms·
In general this is good advice, but it is important to mention there are companies and jobs out there someone just starting out should definitely steer clear fr
by Roark66 3y ago
In general this is good advice, but it is important to mention there are companies and jobs out there someone just starting out should definitely steer clear from. I specifically mean developer jobs in certain huge corporations where a developer is expected to take part in 1~3 1h long meetings every day, each with 30+ participants talking at length about things like "architecture", "policy", "planning". In addition to a daily 1h long "catch up"(previously known as stand up). Also one is expected to produce multipage written comparisons of certain technologies to justify every little choice and no actual programming work ever gets done(but if you look at the planning software there are hundreds of work items whizzing by). If you, as a junior dev or a trainee end up in a job like this, run. If you don't, your skills will atrophy. If you get used to the nice paycheck and you stay for years you'll not be able to do any "actual programming" and you'll both despise your current work and be terrified of loosing it at the same time. In my consulting career I met many people and teams in such position. If you want to get a good dev job seek one that makes you do the actual programming first. Preferably with some experienced people.
- fuzztester 3y ago>where a developer is expected to take part in 1~3 1h long meetings every day, each with 30+ participants talking at length about things like "architecture", "policy", "planning". Other buzzword red flags: mission, vision, teamwork, team spirit, offsite, messaging, team building, culture fit (more in startups), etc. Many, if not all, of those buzzwords are corporatespeak or startup speak for "we want people to think and act (just) like us", or, IOW, "the nail that sticks up gets hammered down.