Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why senior developers fail to communicate their expertise

nair.sh

Post reply on HN
Print view View original

101–110 of 361 posts

Re: Why senior developers fail to communicate their expertise

#101

Post by bigfishrunning »

iJohnDoe wrote: post #12

FTA: “AI agents are the future of software development. We won’t need developers anymore to slow down the progress of a business.” Almost all business presidents, CEOs, and owners are thinking this. I guarantee you they are sick and tired of developers taking forever on every project. Now they can create the apps themselves. My comment isn't meant to debate every nitty-gritty detail about code quality, security, stab…

Now they *think* they can create the apps themselves. I say let every CEO and business administrator try; business will fail, everything will get shitty, and eventually somebody somewhere might learn something. Let 'em cook.

Re: Why senior developers fail to communicate their expertise

#102

Post by macintux »

nullorempty wrote: post #51

What I found is that my willingness to communicate and share my expertise is usually not in demand with more junior developers. In general, I find developers uninterested in finding a mentor. They don't look at your linked in profile, they don't look at you as a possible source of knowledge and expertise. So it's not like I have nothing to share after 30 years of experience in the industry, I just have nobody to shar…

I took a job in another state in large part because one of the interviewers was a highly skilled sysadmin that I wanted to learn from (I had basically backed myself into system administration as a career at my first job, a startup, so I didn't have a lot of people to lean on to learn my trade).

Of course, he turned in his notice shortly after I arrived, because he had found his successor. So, that didn't work out so well for me.

Re: Why senior developers fail to communicate their expertise

#103

Post by mpyne »

nine_k wrote: post #70
lnenad wrote: post #50

Earlier quoted context omitted.

Why can't innovation bring better stability?

Innovation is change, and change is the opposite of stability. Innovation can reduce pain though, if the current pain is strong enough. A stable stream of failures in production can be the kind of "stability" you want to disrupt.

Being able navigate change can provide stability in the long term though, at least as opposed to being resistant to change.

Re: Why senior developers fail to communicate their expertise

#104

Post by giancarlostoro »

hilariously wrote: post #99
vscode-rest wrote: post #79

Earlier quoted context omitted.

Is the DB on the same host as the web server?

It is more likely they did not leave enough overhead for the host operating system, which is a classic issue.

I don't really remember, to be fair this was nearly 10 years ago now. Upon some googling now, I do see a way to limit just how much Mongo sucks up for data + index. I am curious if it would have been a smoother experience, if this configuration was even available then.

Re: Why senior developers fail to communicate their expertise

#105

Post by agumonkey »

nullorempty wrote: post #51

What I found is that my willingness to communicate and share my expertise is usually not in demand with more junior developers. In general, I find developers uninterested in finding a mentor. They don't look at your linked in profile, they don't look at you as a possible source of knowledge and expertise. So it's not like I have nothing to share after 30 years of experience in the industry, I just have nobody to shar…

Are juniors you ran into psychologically obsessed by being self-reliant ? or too proud of their own ideas ?

I also believe that some of seniors experience is flesh-level resilience. I'm no smarter than when I joined the industry, I just got used to being in the trenches, how to handle my own psychology, how all the easy-looking things are not and how the horrible ones aren't either.. I could explain this in detail to any junior, but until they're on the minefield it won't mean much.

Re: Why senior developers fail to communicate their expertise

#106

Post by danhorner »

I tripped over the double-entendre of the teaser quote and then found it ironic that the author is a copy writer.

>> “AI agents are the future of software development. We won’t need developers anymore to slow down the progress of a business.”

> And so, to me, a copywriter, what’s happening here is that the same message is meaning two different things to two different audiences.

I couldn't tell whether to parse this as "We will be faster without those slow developers", or more cynically as "We don't need developers to slow us down; We can now be slow with ai agents". I suspect that with creeping complexity the latter reading will hold up better for large projects.

Re: Why senior developers fail to communicate their expertise

#109

Post by nine_k »

mpyne wrote: post #103
nine_k wrote: post #70

Earlier quoted context omitted.

Innovation is change, and change is the opposite of stability. Innovation can reduce pain though, if the current pain is strong enough. A stable stream of failures in production can be the kind of "stability" you want to disrupt.

Being able navigate change can provide stability in the long term though, at least as opposed to being resistant to change.

Yes, all stability in real life is metastability, it needs a constant effort to maintain. A worthy innovation can lower this effort, or lower the risk of a catastrophic failure.

A complete stability is death.

Post reply on HN