After many years I'm still pasionate about programming, still do it in my spare time and enjoy my work. But, it really does need to be in a language and platform I enjoy. I also notice that if you have a job with a more niche language all your collegues will be passionate about the work too. This is why I personally do not care much about language comparisons. It might be that the language of my choice is only margin…
Same Stop: Life after 26 years as a programmer for Apple
141–150 of 438 posts
Re: Same Stop: Life after 26 years as a programmer for Apple
#142So I'm a software dev/architect again, working in esoteric and interesting spaces, and will continue to do so until I "retire" (meaning that I switch to full time on my open source projects).
Re: Same Stop: Life after 26 years as a programmer for Apple
#143Earlier quoted context omitted.
That's well said... I feel this way even about pure fun pursuits like video games. Yeah, I still like video games, but I also like time with my daughter and wife or getting outside and playing sports or a bunch of other things I didn't use to do that kind of crowd out a well I've gone to many, many times anyway.
I think video games (like movies, books, etc) are a different kind: they are about consuming, while programming (electronics, carpentry, etc) is about creating. Some games, like Sim City or Factorio, sort of blur the line though.
Re: Same Stop: Life after 26 years as a programmer for Apple
#144I once had a PM who told me coding was just a stepping stone to them in their career. I couldn’t understand, I thought they must not have been a “natural” like me. Fast forward a few years, after taking on more mentorship roles, then staff responsibilities, then slipping into project oversight roles… She was so right. Coding was a great stepping stone. Several years ago my father got promoted to some leadership role.…
Ah, the foundational myth of middle management.
Re: Same Stop: Life after 26 years as a programmer for Apple
#145Earlier quoted context omitted.
> Technical leadership is very expensive to find though, and once you find one you don’t let them go back to the production line. I have a friend at our company who is a gifted programmer. He was moved into a management position. He discovered that he hated working in a leadership position. He tried to get them to move him back to an individual contributor position. They refused. He said, move me back or I quit. It t…
I feel it's completely acceptable to wish to stay in an IC position, but to refuse outright to give advise or share the experience (it's hard to tell from your short paragraph) seems... odd? It's acceptable to want to stay in a specific role, but I am not certain I feel it's acceptable to eschew an increasing responsibility or mentoring role as you gain experience. That way lies the "genius programmer that works alon…
I think it depends on how much time they expected him to take out of his days. My girlfriend resigned from a job after becoming a go-to person for everything and everyone. It caused her to not have time for her own work, effectively being way underpaid, and being stressed all the time.
Re: Same Stop: Life after 26 years as a programmer for Apple
#146Earlier quoted context omitted.
I understand this point of view. Unfortunately, for those who entered computing out of a passion for it, it’s difficult to work for employers or managers where computing isn’t a passion. This leads to all sorts of practices that suck the joy out of programming (e.g., Leetcode, meetings, KPIs, PIPs, certain design decisions, etc.), reducing it to a corporate “monkey dance.” Maybe I have rose-colored glasses, or maybe…
I think you're getting vloser to the root issue. You can work with passionate people. You can work for a large corporate, for a huge paycheck and stock options. Pick one. I work for a small company, and I make a great living, but it's a fraction of a fang salary, and there is no stock to option. On the upside I'm responsible for my code base, I work on whatever I like, (which largely overlaps with customer needs sinc…
It is the corporate environments and the entanglement of Business BS that ruins software work for me.
Re: Same Stop: Life after 26 years as a programmer for Apple
#147>Are there younger engineers, new to the career, for whom programming is not merely a job but something they can imagine doing in their spare time? Yes, absolutely!
Re: Same Stop: Life after 26 years as a programmer for Apple
#148I once had a PM who told me coding was just a stepping stone to them in their career. I couldn’t understand, I thought they must not have been a “natural” like me. Fast forward a few years, after taking on more mentorship roles, then staff responsibilities, then slipping into project oversight roles… She was so right. Coding was a great stepping stone. Several years ago my father got promoted to some leadership role.…
or you're probably not that good programmer...?
Who can tell?
Re: Same Stop: Life after 26 years as a programmer for Apple
#149> But there is something becoming more familiar to me as I go back to the wild west of C programming (where very little happens behind the scenes I might point out - no garbage collection here!). I share this sentiment. I pursued computer science because of the romanticized notation of tracking every bit and byte and talking directly to the hardware. I know I'm not alone given the popularity of old-school fantasy con…
I don't know what's sadder: That this kind of programming is becoming a lost art, or that nobody seems to care. I got my first job out of college partially because in the interview when I was asked to implement some algorithm XYZ in "any language I choose" I went with X86 assembly and nailed it. Well-performing code was highly valued at that company. Knowing how to ensure your code fit into the cache and your memory accesses stayed on one page were considered critical programming skills.
Now, outside of a few rare embedded or game engine jobs, nobody seems to give a shit about any of this. It's just "glue these APIs and libraries together and ship the resulting crap as soon as it barely runs." Nobody cares about the size of the resulting executable. Nobody cares about or even knows their code's runtime heap footprint. Nobody cares or even measures how many cache misses they're encountering. I feel like an old grandpa even typing this stuff out.
The worst part is that end users are the ones that end up losing. It's their system resources that are ultimately being wasted.
Re: Same Stop: Life after 26 years as a programmer for Apple
#150>Are there younger engineers, new to the career, for whom programming is not merely a job but something they can imagine doing in their spare time? Yes, absolutely!
I've reached a age where I have to answer "define young". Early thirties is weird. All the people I respect and learn from are still older than me, but not old old.
It didn't occur to me that I was old until your comment. Thanks!