Live data from Hacker News

The Best Programming Advice I Ever Got (2012)

russolsen.com

191–200 of 247 posts

Re: The Best Programming Advice I Ever Got (2012)

#191

Could not disagree more. The author most probably freed the company from its dysfunctional stagnation due to some political issue. It is thanks to his ignorance that he resolved an issue, something that had to be done. In general, staying out of other people code is a bad idea. It promotes lack of transparency and agenda proliferation. This is because the owners of the code start being a "monopoly", can work less har…

Sounds like you didn't read the article :)

I did and I know the author says "actually it is a terrible advise" but he also continues to soften his statement

Re: The Best Programming Advice I Ever Got (2012)

#192

Did anyone really read this till the end? If your conclusion is that the best programming advice the author ever got was to “stay the hell out of other people’s code” please try to read it again... that was exactly the opposite of what he meant. Best advice I ever got: always read things ten times before responding. > “Actually it was terrible advice, advice that I've gone out of my way to ignore in the years since.…

Yep, seeing so many people with reading comprehension problem here at HN is surprising.

Re: The Best Programming Advice I Ever Got (2012)

#193
post #63

There's definitely value in respecting boundaries. Sometimes you have to take a small local inefficiency in order to create a bigger global efficiency. That's life. In my experience, though, this is a much bigger problem in software because nobody really knows what they're doing. There's no industry standard way to do almost anything. You can argue about "use Foo!" or "don't use Foo, use Bar!" and there's no one Corr…

That's an interesting perspective. I think you're right that we don't have "correct" and standard answers because we don't assume total competency, but I think we don't assume total competency because software development (both the requirements and the practices) change fairly rapidly. I wouldn't be surprised if in 100 years, we're still trying to figure out standards, if the pace keeps up.

Two things about programming:

1. Nobody really knows how to do it.

2. If you have a system for doing it, you're doing the computer's job.

(Sadly I cannot find the source of this quote.)

Re: The Best Programming Advice I Ever Got (2012)

#195

I made same mistake, I saw how old system underperformed and that I could make it better, faster, more stable and bring higher profit. When I presented that my boss, next I know I’m in room with HR, my bosse’s boss and technical lead (who was practically executive director), to my surprise boss started conversation with “your actions concerning me...” they told me to give all the related code, documents and remove ev…

You're clearly leaving out some important detail, which makes me think this is 100% your fault and you were being stupid, even though you want to play the victim

Personal attacks will get you banned here, regardless of what details someone else left out. Please review https://news.ycombinator.com/newsguidelines.html and post civilly and substantively, or not at all.

Re: The Best Programming Advice I Ever Got (2012)

#196

Earlier quoted context omitted.

+1. The fact that HR's involved strongly suggests that OP was messing with something he had no business to touch.

I don't understand this, or the linked article. Can someone explain to me what possible reason there can be for responding with disciplinary action when someone proposes an improvement?

I look at documents and remove everything from my computer, and my guess is that op worked on it on his own time on his own machine. He was still working 4 years in that company, so he was not removed from project. Feels like action was uh, he got documents out of company.

Don't get any data out of company, I would never promote someone who got any documents out of company laptop to his own.

Re: The Best Programming Advice I Ever Got (2012)

#197

Earlier quoted context omitted.

"People will sabotage things simply because they want the useful idea to be theirs." Not just that, they will sabotage things if it makes them more profitable, which probably happens in thousands companies worldwide everyday. 1. Get a contract. 2. Sell some crappy software to the customer. 3. Wait for them to ask for more speed. 4. Complain it's their fault because their hardware is too old. 5. Offer to either instal…

The way capitalism is supposed to work is you quit this job and open a shop which does the same thing as the existing company but doesn't artificially reduce speed, using that as a competitive advantage. The end result is that the first company is required to either adopt your strategy or fail, either solution leading the consumer to a better result.

Which is why the no-compete was invented...

Re: The Best Programming Advice I Ever Got (2012)

#198
post #143

Earlier quoted context omitted.

>>There's definitely value in respecting boundaries. Sometimes you have to take a small local inefficiency.. I don't think anyone argues with that. It's just that sometimes some of the biggest impostors hide behind "boundaries". >>This will continue to be a problem for the next 100 years until we figure out the right way to make good software. A lot of people figured it out already.. but those are a minority and the…

> A lot of people figured it out already.. You'll have to expand on this for me, because I find this claim shocking. Who figured it out, and what did they figure out?

Software is not the first industry to deal with systems complexity or large teams management but (in my part of the world at least) it's the first to expect engineering-like results from non-engineering workers and managers. There are developers who have noticed the similarities between creating/assembling/testing components & modules in other industries and software and borrowed practices before software had a name for them. It's just that these people are dispersed in a sea of devs tuned to Microsoft Framework Factory or busy building castles on Javascript Frameworks Sands.

Re: The Best Programming Advice I Ever Got (2012)

#199
In 1999 my boss's boss loved Silverstream.* It stores code in the database! Anyone still using files for code is obsolete!

We had 12 beefy servers powering our site. So I rock up and realise we're not using any of Silverstream's features, and its just acting as a servlet container. Big boss had moved onto bigger and better bossing by now so wasn't around to stop me.

After a couple of weeks of investigation, we demonstrated that Caucho Resin is better in every way. Fraction of the cost, starts super fast and runs like lightning. Great. We happily switch over and all was well for almost a week.

A few days in the head of Ops barrels up and demands to know if this was all my fault.

"Ummm, yeah?"

"Great. What the fuck am I supposed to do with the other 11 servers??"

I think they'd had to fight for budget for enough hardware to run the site with Silverstream, and young me had just made them look incompetent. They forgave me eventually...

* I actually like Silverstream's core ideas. It was just a little ahead of its time, and stored code in the db. And was 12x too slow.

Re: The Best Programming Advice I Ever Got (2012)

#200
post #143

Earlier quoted context omitted.

> A lot of people figured it out already.. You'll have to expand on this for me, because I find this claim shocking. Who figured it out, and what did they figure out?

Software is not the first industry to deal with systems complexity or large teams management but (in my part of the world at least) it's the first to expect engineering-like results from non-engineering workers and managers. There are developers who have noticed the similarities between creating/assembling/testing components & modules in other industries and software and borrowed practices before software had a name…

What other industries should we learn from?

I know big construction projects often suffer from similar problems, and they don't seem to have figured it out.

Post reply on HN