If I had a few hours to spare I could come up with much more.
After 14 years in the industry, I still find programming difficult
161–170 of 207 posts
Re: After 14 years in the industry, I still find programming difficult
#162I think the hard part of programming, or programming related things, is environment setup. Even with things like Docker, you can still run into SO many issues. Programming by myself is always easy. Programming within a company can be difficult because of this. There are definitely places out there that make environment setup super simple. Even then, you can still run into something that hasn't been encountered before…
Re: After 14 years in the industry, I still find programming difficult
#163Been programming over 30 years, since I was 8 years old and my dad’s coworker gave me his old BASIC programming books and I was hooked. I have always found programming easy, and still do. It is just fun, and I still love learning new languages and tools and paradigms. It is still my favorite hobby. However, WORK is hard. Dealing with office politics and changing priorities and bad leadership and meetings and TPS repo…
If you are finding programming easy doesn't that just mean you aren't trying hard enough? There are tons of unsolved problems, tools that aren't optimal, and products that don't work as well as they should. If fixing those things were easy for you, you would be a billionaire.
Getting to the point where one can deliver value and find it easy, and setting the cruise control, is a reasonable thing to do. Frees time and mental attention for the rest of life.
I don't happen to be wired up that way, but there are times when I wish I was.
Re: After 14 years in the industry, I still find programming difficult
#16423 years of solid experience in programming. The hardest parts for me have been: - integrating with other systems, often APIs. The difficult part is the constantly changing API contracts, which break integrations in often unpredictable ways - Leaning new libraries or frameworks that often reinvent the wheel for no good reason - Understanding the deep layers of abstraction in some systems (be it a DSL, a transpiled la…
Re: After 14 years in the industry, I still find programming difficult
#165Earlier quoted context omitted.
Yeah, I mean software development. I don't find the semantic distinction between that and programming particularly interesting myself - why write code if you're not doing that do develop software?
Because you might have architects specifying exactly what needs to be programmed, so the software development part is mostly done.
Re: After 14 years in the industry, I still find programming difficult
#16623 years of solid experience in programming. The hardest parts for me have been: - integrating with other systems, often APIs. The difficult part is the constantly changing API contracts, which break integrations in often unpredictable ways - Leaning new libraries or frameworks that often reinvent the wheel for no good reason - Understanding the deep layers of abstraction in some systems (be it a DSL, a transpiled la…
Painfully aware that my soft skills need improving but I'm not sure where to even start. I've started prepping more before important meetings but I'm easily so lost in code that I forget meetings are even happening sometimes.
Re: After 14 years in the industry, I still find programming difficult
#167Earlier quoted context omitted.
I've always hated this saying, and I think the reason applies here too. If you take up running and it never gets easier, that means you're never managing your pace and you're always going full throttle. That's a straight shot towards injury if not chronic disability. Most aerobic benefits happen at zone 2, where your heart rate is just above 'easy effort'. When you start out, this might just be walking, so it makes s…
Lemond's statement is in reference to racing. The race isn't won in zone 2. Same with programming. Nothing wrong with a lot of zone 2 programming, in fact it's quite important to maintain balance like you describe, but the race isn't won with comfortable work.
Re: After 14 years in the industry, I still find programming difficult
#168Re: After 14 years in the industry, I still find programming difficult
#169Been programming over 30 years, since I was 8 years old and my dad’s coworker gave me his old BASIC programming books and I was hooked. I have always found programming easy, and still do. It is just fun, and I still love learning new languages and tools and paradigms. It is still my favorite hobby. However, WORK is hard. Dealing with office politics and changing priorities and bad leadership and meetings and TPS repo…
Same here, 30+ years experience, programming's always been easy for me. The hard part is suspending disbelief to ignore how bad nearly everything has gotten. Every language, every framework, every operating system, every hardware platform, every paradigm like the web/mobile/AI is so riddled with obvious mistakes and missed opportunities that it takes nearly everything I have each morning to start working. I've reache…
The luxury of thinking otherwise is a post-war economic boom phenomenon. We’re now reverting to what has always been: people screwing one another over scrambling to get their piece of the pie.
I used to think about living a well-balanced life — the middle class life — but that’s akin to thinking you can make a long career out of just being a dev for the rest of your life during ZIRP: naive.
All the market inefficiencies that allowed tech to boom have been snuffed out. All the market inefficiencies that allowed people to live simple, fulfilling lives are gone. You now have to actually play the game, or one day you’ll find you’re a replaceable commodity that’s past its warranty.
Rally together people that share your values and go grab your piece to build something that actually enlivens you. To do otherwise is just shirking responsibility.
Re: After 14 years in the industry, I still find programming difficult
#170Earlier quoted context omitted.
Yeah, I mean software development. I don't find the semantic distinction between that and programming particularly interesting myself - why write code if you're not doing that do develop software?
Because you might have architects specifying exactly what needs to be programmed, so the software development part is mostly done.