Live data from Hacker News

Aging programmer

world.hey.com

311–320 of 375 posts

Re: Aging programmer

#311
post #151

“I have no idea about how effective pair programming is. My desire to discover it is zero.“ I stand with the OP. Maybe this is a young folks thing, but I don’t understand how anyone can pair program. It’s like going to the toilet with someone staring at you.

I think pair programming is almost always done wrong: it usually ends up being one person doing all the work and the other one watching.

I had a manager who loved coding at us. We’d get on a 3–5h zoom call and I’d watch him mumble and write code. It was exhaustingly boring. He called this pair programming.

Re: Aging programmer

#312

Earlier quoted context omitted.

I’m kind of in this boat. I’ve been doing this for 25 years now (jeez). Mentoring a dev with 6 to 8 years experience is a pain in the butt (yes. I know. Not all of you). While I’ve got a pretty good memory, a lot of the times I don’t have a direct or complete answer for their question. I’ll have a tingle of a memory that is similar to their question. So I’ll give them that as a starting point and tell them how I’d ap…

I'm working with a junior dev now and the phrase that I keep repeating is "slow the fuck down". He's completely frantic with the copy and paste. I'm watch him google something, click the first link, paste the code into his project, and when it doesn't work he's on to the next link, paste, repeat. He doesn't even back out the changes he made the first time that didn't work. I spent hours fixing his code and hand it ba…

This seems to be what modern software development has degenerated into. In the future, it'll be monkeys playing roulette with Github copilot until something compiles/executes.

Re: Aging programmer

#313
The idea that a programmer is “aging” at 40 is just nonsense that the tech industry made up to cut costs. Nobody would suggest that a 40 year old doctor or lawyer or civil engineer is “aging,” they’re widely acknowledged to be getting better until perhaps 50s or even early 60s. What might happen is that two decades of tech salaries make senior programmers not give much of a fuck anymore.

Re: Aging programmer

#314
post #312

Earlier quoted context omitted.

I'm working with a junior dev now and the phrase that I keep repeating is "slow the fuck down". He's completely frantic with the copy and paste. I'm watch him google something, click the first link, paste the code into his project, and when it doesn't work he's on to the next link, paste, repeat. He doesn't even back out the changes he made the first time that didn't work. I spent hours fixing his code and hand it ba…

This seems to be what modern software development has degenerated into. In the future, it'll be monkeys playing roulette with Github copilot until something compiles/executes.

No, it's not. They're just inexperienced and it will stop/become more thoughtful as they're gaining experience and learn how the pieces actually fit together.

The reality is that half of the tutorials and answers you can find won't work. Either because they're doing something entirely different or because they're for a tool/framework that's deprecated the functionality.

A beginner won't be able to tell this simply because none of the pieces are known to them.

When a person with more experience finds these tutorials they'll likely know within seconds if a given answer or tutorial is even remotely applicabe, which enables them to be much more thoughtful about what to do.

You'll potentially waste weeks on trivial tasks if you're hellbent on actually fully understanding something right at the start, and if the beginner does this the more experienced ppl will complain how inapt they're.

Honestly, you both just sound like toxic people in that regard and should not be allowed to work with total beginners. Which is fine, but the issue really isn't with the pupil that's just clueless. They need somebody to give them a tutorial and guide which is applicable and they'll learn how that piece works, now keep repeating that until they've got a basic understanding of the system and only then can they work on their own

Re: Aging programmer

#315

Earlier quoted context omitted.

I have to agree with parent comment. Leet code interviews, while sometimes obnoxious, are still good exercises. I have learned a lot of nuanced takes from a leet code interview with an interesting question.

OK, fair 'nuff. Right now, I'm working on a data parser for a backend API that fetches a JSON response, using the built-in NSURLSession stuff, turns it into a Swift Dictionary, then I sort through that Dictionary, and emit a bunch of Swift struct instances for use by the API consumer. The reason for this, is because the API that I wrote about seven years ago, is giving us performance problems. I wrote about that in t…

>But maybe I'm doing it all wrong, and I should stop working on this to practice leetcode.

Junior here and not as experienced as you are but I resonate with a lot of what you have written so far. I'm more of let my work and projects speak for itself. I also hate leetcode or code challenge kinda interviews. So far I haven't have to take any to get a job and I plan on never taking or doing any. If I see that an interview involves such I will reject it. I can accept a decent take home assignment or technical questions in areas that I will likely encounter on the job.

Re: Aging programmer

#316
post #94

I found I lost interest in vapid work. Programming is still fun, but it's a big challenge to find a job that is fulfilling. When I was younger, I'd work on whatever. Then everything started sounding like yet another get rich quick company, and is that what I was giving up my life for? Just to move little green pieces of paper around? The most appealing thing I'd seen recently was a company that wrote software to help…

What do you teach? Like computer science at a college? Or something else? How did you make the switch? Was thinking about somehow doing some casual teaching as a step back from a corporate programing career for a bit

Re: Aging programmer

#317
post #306

I'm 60. I've been writing software since 1983. For 25 years, in between, I was a manager. At one point, I progressed in my career, until I only managed, and did no coding (for money). So I coded on the side. That's a big reason for all the open-source stuff that I have in my portfolio[0]. When I was told that the software industry has no use for old coders, I took my toys and went home. I was kind of butthurt. But th…

Hey Chris, I'm younger than you by a bit, have been coding since 1982. Some similar background (low level stuff, embedded, designed some boards). I'm now a manager (for a few years) and it's hard for me to find time to code which kind of maybe sucks. Am unsure ;) I still do a little. Given I have a family and other interests I just can't imagine myself writing software on my "free" time (which isn't that much given m…

Well, one of the reasons that this WFM, and YMMV, is that I’m, personally, a fairly OCD-type person. I’m a couple of fries short of a happy meal, so to speak.

Coding and architecture are my hobby, as well as my vocation. It’s a real pleasure for me to work on a software problem.

I have friends that own boats, travel, ride motorcycles, exercise, play golf, fish, hunt, take photographs, sculpture, paint art, cosplay, build drones, play music, build hot rods, etc.

I use that energy to write code. That’s also one reason that it has been so painful, having employers treat my work badly. I tend to take that stuff personally.

Also, I am a long-term member of an extracurricular volunteer organization, and this has given me a ready-made target demographic for my work. I don’t need to hunt around, looking for problems to solve. The downside, is that there’s no money to be made, Serving this demographic, and they can be a real high-maintenance crew. Rather demanding, and they tend not to play well with others.

I currently work on software more intensely, than I ever did, when I was getting paid. I’m probably devoting 4-12 hours per day, seven days a week, to it. I take breaks (naps, even), whenever I feel like it, and have a fairly full dance card, socially (see “extracurricular,” above). I don’t drink or use any “recreational” substances (not a teetotaler —I don’t really care what other people do), so I don’t have a lot of mental “down time.”

I have a family, and act as a bit of a caregiver, so working from home is important. I also no longer travel, all the time, like I used to. If I go anywhere, these days, it’s because I want to; not because I have to.

Like I said, I’m fully aware that many folks would not enjoy my lifestyle. That’s fine. I won’t judge others, for theirs, and appreciate it, when the favor is returned.

I am “the real deal,” though. My productivity is fairly high, but I have worked with folks that make me look like a lazy slob, and I’m no longer interested in playing ego games, or competing with others. I’m enthusiastic, open, friendly, and enjoy working in a team. I was a good manager, but hated it, and am glad to see the back of that.

I have been disappointed in the way that I’ve been treated by folks in today’s industry (I fairly quickly learned to avoid things like meetups), and, to be perfectly honest, there’s more than a little “screw you” in my energy.

But it WFM. YMMV.

Re: Aging programmer

#318

Earlier quoted context omitted.

I know quite a few engineers who simply no longer need to work ever again, and are working just for "funemployment".

Funemployment is when you are not working though

I guess there’s both fUnemployment and Fun-employment

Re: Aging programmer

#319

Earlier quoted context omitted.

I have to agree with parent comment. Leet code interviews, while sometimes obnoxious, are still good exercises. I have learned a lot of nuanced takes from a leet code interview with an interesting question.

OK, fair 'nuff. Right now, I'm working on a data parser for a backend API that fetches a JSON response, using the built-in NSURLSession stuff, turns it into a Swift Dictionary, then I sort through that Dictionary, and emit a bunch of Swift struct instances for use by the API consumer. The reason for this, is because the API that I wrote about seven years ago, is giving us performance problems. I wrote about that in t…

> but it takes years to get the advanced stuff down.

Obligatory ask, bullet list of "the advanced stuff", please?

Re: Aging programmer

#320

Earlier quoted context omitted.

OK, fair 'nuff. Right now, I'm working on a data parser for a backend API that fetches a JSON response, using the built-in NSURLSession stuff, turns it into a Swift Dictionary, then I sort through that Dictionary, and emit a bunch of Swift struct instances for use by the API consumer. The reason for this, is because the API that I wrote about seven years ago, is giving us performance problems. I wrote about that in t…

> but it takes years to get the advanced stuff down. Obligatory ask, bullet list of "the advanced stuff", please?

I’m not really up to doing that kind of write-up. However, I did write this series[0]. Some of it might be a bit “dated,” but it probably has what you want.

There’s an excellent book[1], called “Advanced Swift,” by Olle Begemann, and Chris Eidhoff, that gives a far better breakdown of the more intricate parts of Swift than a simple bullet list.

Like many languages, Swift is a deep rabbithole. Heck, you can get lost, just in the way it handles strings[2].

[0] https://littlegreenviper.com/series/swiftwater/

[1] https://www.objc.io/books/advanced-swift/

[2] https://flight.school/books/strings/

Post reply on HN