It never used to be like this. I think management has reacted to the traits they perceive in programmers - get distracted too easily, work on things that don't need doing, take too long, cannot provide work-time estimates, etc - by putting in place this micro-managing approach: "only do it if it's on the kanban and tell us each and every day what you have done and will be doing". I know agile, etc, weren't designed to do that, but that's what they've been used for whenever I've been subjected to them.
Programming and dev-ops used to be fun, self-directed, creative work which kept me interested for a couple of decades. Now the pace of change (much of it unnecessary or over-sold) and the constant micro-management have me looking for other things to do.
We just started doing "by the book" Agile with daily stand ups. Now that you mention it, it does feel like I'm being micro managed. Put in your time every day so we can email everyone the burn down chart. Lets add some more pressure to the job if you are behind a day. There are no milestones, just an endless grind. I don't know why programmers don't push back against that stuff.
At the end of the day programmers are mostly just factory workers of the 21st century. The best ones are perhaps closer to the mechanics of the industrial revolution.
Compared to programmers 25 years ago? Absolutely not. The pay is worse (inflation-adjusted), and the working conditions are far, far worse (see: open-plan offices).
Let's see what I was doing 25 years ago:
* Private office with a door that closed.
* Status updates mail to $SOMEONE once a week that were mostly auto-generated from the tools we used. Took 30 seconds.
* Sat down to a chunk of work uninterrupted for long periods of time because no one was micro-managing me or bugging me on Fashionable-Chat-App-of-the-Week.
* Used development tools that had a half-life measured in years, not months.
* Got to really, *really* know my tools because they weren't swapped out for the new hotness every six months. Man, the ways I used to abuse FoxPro bordered on criminal. I can't do that these days since the tools get swapped from under me so often.
* Was paid well, and treated with professional respect. Sometimes a collared shirt was required, but I didn't mind when everyone else had to wear ties.
* Was provided with good equipment, often without asking. "I have a quad-core server box with an assload of RAM for a...mikestew?" "That's me, but I didn't order it." Boss: "oh, thought you might need that for multithreaded testing." Thanks, boss!
* Went in at 9:00, went home at 5:00. Every day.
Today: * Today I'm sitting in a retasked storage room because I refuse to sit at the "hotel desks" (note that I'm currently a consultant, so it's not *as* egregious. But 20 years ago, clients that wanted me on-site provided a desk or sometimes an office.) My last full-time position was in an open office plan sitting next to people that literally (and I use that word literally) spent more time talking about the fucking Seahawks than they did working.
* Daily stand-ups to justify my existence.
* Treated like an interchangeable line worker.
* Working on the cheapest Macbook Pro that Apple would sell the client. With a 120Gb drive, I spend at least a billable hour a week trying to free up space what with Android/iOS dev environments and the multi-gig simulator images. But, hey, at least they saved $100 on the cost of the machine!These are also traits of junior developers, who now get boosted into non-junior roles due to demand for developers.
Hiring cheaper juniors and trying to micro-manage them into intermediates... The same approach suffocates eventually when "unaccounted for" tech debt creeps in.
That said, there is also something to certain devs wanting to play with shiny tech (and build their cvs) rather than the best tools for the job. This, along with " cannot provide work-time estimates" point to the need for some senior role who can management overall project development, including goals, estimates, planning and tech stack choices; and this has to be a senior technical role, not a MBA-ed middle manager with a list of methodology-derived rules carved into stone tablets.
I think using/not using agile is like doing business with a contract vs a handshake. When there are few enough people who trust each other, you can get by on a handshake. When you get into larger dollar amounts (like paying an office full of developers), sometimes its better to use a contract so you have some perception and promises about where your money is going.
Now, agile is of course not a contract, but if teams meet their deliverables, the business can at least see where their money went, which they are entitled to do.
Just don't expect the big software firms to be knocking on your door if you need those bullets on your resume (unless you have a PHD).
Also, prepare to work in a formal-verification development environment. Some aerospace jobs are like this, which basically means code moves as slow as molasses. If it's flight control software, you may find yourself writing 20 pages of documentation/paperwork for every one page of code. (Think about it, if your code could destroy a $12 million jet engine, you should be pretty confident your code actually works, right ?). So research CMMI [1] and if that is a dealbreaker for you, make sure you avoid those kinds of jobs.
[1] https://en.wikipedia.org/wiki/Capability_Maturity_Model_Inte...
What kind of company is this?
There are still elements that I enjoy. I still love the creative, mathematical problem-solving aspects, but those moments feel few and far between.
I also feel at times I'm taking my position for granted - I'm not sure what else I'd do besides programming. I've always had a casual interest in security, so I'm thinking I might look into that. Being a "bug bounty-hunter" seems like a dream, though I'm not entirely sure how realistic that would be!
I also love music, but I think that's even less feasible. I'm not proficient enough to be able to teach it. But I would like to be able to dedicate more time to learning/producing it.
Good luck - here's hoping we find something more fulfilling :).
London appears to have a lot of jobs atm...
Also, web tech isn't nice to work with...
Going the graphics programmer route (OpenGL, DirectX, Vulkan) would make for some fun work in a stack that changes in a different way and not as fast.
Bottom line though, technology is the business of change and we enable change for those that we work for.
As I've mentioned before I own a gym business (multiple locations) with my wife and some other business partners. Part of the purchase process was financial disclosures of everyone so we all know what each other makes on paper, what we actually take home, household wealth and assets, etc.
I'm 30, younger than my business partners by multiple decades, and am the only one not in a strictly management position. Two of the partners are PEs and I make more than anyone else.
I say this not to brag but only to point out that it takes a lot to leave programming simply because the money isn't there is a lot of other professions. I almost went into civil engineering and I'm glad I didn't, because apparently I would've had to bust my ass to make it into management only to be 20 years older and making less money to boot.
I find the data a whisker suspicious, but this is BLS data. Supposedly, the media salary for a software developer in SF is $118k a year. Keep in mind, in San Jose, it is $142k, which sounds more like it.
http://money.usnews.com/careers/best-jobs/software-developer...
But now look at salaries for other fields. A registered nurse in SF earns a median salary of $123k. Every time I point this out, I always make sure to emphasize that I am not complaining that registered nurses earn a lot of money in SF - they should! And yes, it is a hard job, but perhaps a rewarding one as well. Would you rather do a hard job that is important and pays well, or log into JIRA to fix bugs and report on them in your daily "standup"?
Dental Hygienists, according to this roundup of BLS data, earn about $102k a year. Ok, that's less than developers, but do 45 year old dental hygienists get run out of the field because they are too old, or because they withdrew for a few years with kids and family responsibilities?
And keep in mind, salaries for lawyers, nurse practitioners, physicians, physician assistants, and other professionals or para-professionals often substantially exceed what software developers get paid. If you want a relatively low stress job, there are better options. If you're ambitious, there are better options as well. In short, you'd better really like code if you ant to do this, and you may find you don't, once you discover what that means on an "agile" team. Great for hobby, sure, so is music, dance, and painting. Do you like it more than music, dance and painting?
The unspoken truth is that Software development isn't really that great a job for the pay, career prospects, and working conditions. It's not horrible, either, but there's no need to scratch our heads about an alleged "shortage". I know the industry has a bunch of reasons they promote for the "shortage", but in the end, it's a market response to pay and working conditions. People with the skill to do this have realized they're better off in a different field.
Software dev is less about enjoyable hacking, and more about "housekeeping", or a million yak-shaving data management tasks that you are paid to care about.
I'd sooner do something else that merely involves software, but has some other domain of knowledge, and keep the majority of my coding as off-work hobbying.
Sounds like you're writing code with hard specs (enterprise company?) where you just feel like a cog in this vast code outputting machine. In that case, it's totally natural to feel like you're dying inside. That's natural. We're creative beings, and you either need to find a different job or calibrate other dimensions of your life to meet that need (physical fitness, start a family, serious hobbies, be part of a community).
The actual company feels more on the other side of the spectrum, and has a fairly 'young' culture, along with an overwhelming amount of 'social coding', for want of a better phrase, including various guilds for different technologies, tech meetings, demos, meetups, ad nauseum.
I feel pretty out of place, but I can't help feeling like I just can't cope with this much day-to-day interaction. I just want something quieter, more low key, if that makes sense?
You might also dig deeper into discovering what you like and don't like about the programming profession: Do you prefer going to meetings? Do you like solving new problems constantly? What drives your satisfaction? What do you not like about programming? What do you like about programming?
What one person considers to be a lucky profession may not be the same view shared by another :)
When I picture someone with a strong background in programming and CS going into another field I always imagine there's a lot of potential for really understanding problems in that field and applying computing to solve them. Essentially, using computing to really support work in another field rather than just computing for it's own sake.
I enjoy coding and understanding how computer systems work, but I don't care for the constant changes in tools and techniques in certain domains of development. I'd rather practise with and improve my existing knowledge of a subject, instead of constantly playing catch-up with someone else's tools and workflow. I also don't care about waterfall, agile, scrum, kanban, scrumban or any other development methodology that I've missed. I hate that my job has me chained to a desk (sitting or standing) instead of being able to use my body. All of this makes me think that real-world software development doesn't really suit me.
I'm about six weeks into a new job after leaving a company I worked at for just over five years. Amongst many other reasons for leaving, I thought that a new environment would change how I felt about continuing a career in software development, but I'm not sure that it has. I'm aware of how lucky programmers have it, but I can't help feeling like I just want something else. Grass is always greener, etc.
What are the career options that allow one to work mostly by oneself in one-to-two week stretches without having to play the development workflow game with the daily standups and so on?
Sadly I'm not sure what I'd do if not programming, but music is a big interest and I'd considered teaching music.
tl;dr Woe is me ;)