The conversation

raw_anon_1111HNSource author
Lessons learnedExperience excerpt · English

So the project I mentioned while I did write every single line of app code and IAC, made every …

So the project I mentioned while I did write every single line of app code and IAC, made every architectural decision, etc., I did come on an off the project over the course of a year and I couldn’t even remember some of the decisions I made. I also used Codex and asked questions about how the codebase worked to refresh my own memory. Why wouldn’t a junior developer do the same? I mentioned that I had Codex describe in detail how it debugged it. It walked through each query it did, the lines of code it looked at and the IAC. It jogged my memory about code I wrote a year ago and after being on other projects

Original discussionI'm Coding by Hand357 source comments · at import
2

What was this responding to?

Parent context · original excerpt

GR
grebcHN

It’s always the journey that matters. If you’re experienced as you are, you’re not learning the same way a junior assigned this might learn from it.

Full original

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 2

Direct replies available in this import. Original-language excerpts.

GR
grebcHN

If you’re 50+ as you intimated in your first post then you have a wealth of knowledge that juniors don’t. Just because it worked this time doesn’t mean it always will. If you need further explanation of why you might want to spend more time resolving a bug to learn about the systems you’re tasked with maintaining then I’m at a loss sorry.

Full original
T4
t43562HN

It's what managers or team leads experience. They have a team that work on the code and even if they used to know what was going on they end up doing everything second hand and they don't realise when the project is going wrong technically because they aren't spending the time to build knowledge and it all looks reasonable from 5000 feet. They start to make questionable decisions based on how they think things are. I have done this. Getting back into development allowed me to see what was going wrong, why changes were difficult and what we needed to do to test properly. Hurray, you're an AI manager now but be careful how much you decide to not look "in the box" especially if you're trying to come up with release dates and so on.

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.