Live data from Hacker News

The Biggest Difference Between Coding Today and When I Started in the 80s

thecodist.com

111–117 of 117 posts

Re: The Biggest Difference Between Coding Today and When I Started in the 80s

#111
post #4

There are so many options these days, and evaluation often requires all the work of using the package only to find out that it's incompatible or broken or unusable for some other reason. So it's often more efficient to write your own version anyway. At least then you'll know the jerk who made it.

I agree, and posts like this [1] leave me floored. How does anyone have time to evaluate all of these individual components. My CS education taught me to build components for myself but not to necessarily do a complete evaluation of 3rd party components in a short time. " We use Heroku for hosting, and run automated tests on CircleCI. Slack bots report what’s being deployed. There are a lot of external services we re…

Yeah, I find that kind of intimidating too. But don't forget that this is an entire company's worth of infrastructure that they're calling out. Also some of those in the middle of your quote are like saying "and we use Comcast for our ISP, and Microsoft Office 365 to create our documents, Google Drive to manage them, and Atom for editing source code..."

Re: The Biggest Difference Between Coding Today and When I Started in the 80s

#112

I don't wish back those days. I get that it's interesting to work to the bottom of things yourself, sure. But I've run into several problems that I couldn't have hurdled on my own, in any amount of time, without the help of the internet. - dll broken from MS. This happened to me. I did a lot of sleuthing, taking things apart, and it just didn't make sense. It was for a DB adapter, so the official documents would have…

> Sort algorithm broken in Swift I really want to believe you, but I can't find any information on this, what are you referring to?

http://stackoverflow.com/questions/33444460/swift-2-1-error-...

Re: The Biggest Difference Between Coding Today and When I Started in the 80s

#114

Earlier quoted context omitted.

>I sometimes feel like doing an Ask HN about "how do you find a coding job where you actually code most of the day when you are 20 years into your career" Find a company who requires any non-approved outside code, no matter how well known and even if using an already approved license, to go through a multi-month approval process that is almost always longer than the current project's allotted timeline. As it is, if I…

I don't want to seem sarcastic, since this is a genuine question: What are the positive aspects that would induce you to work or stay in such an environment?

Approval process is outside the dev shop's control. Overall this is one of the least stressful positions I've been in, has the best pay so far, I enjoy working with my team, and has a short commute.

Re: The Biggest Difference Between Coding Today and When I Started in the 80s

#115

Earlier quoted context omitted.

I don't want to seem sarcastic, since this is a genuine question: What are the positive aspects that would induce you to work or stay in such an environment?

You can code all day and stay in your corner without any external hassle. That process being enforced will ensure that most code is buggy and development is totally unproductive. That will usually create an environment where noone expect anything from developers and you have zero accountability. if it all goes well, you can toy around all day and not have to ship anything, still getting a paycheck, and not risking th…

>That process being enforced will ensure that most code is buggy and development is totally unproductive.

I don't think I'm following you. The procurement process is quite different than our coding process which involves team reviews and the like. Yes, productivity isn't as high as it could be because we sometimes have to develop something in house instead of using open source code, but we still have code review, unit testing, and similar required.

Re: The Biggest Difference Between Coding Today and When I Started in the 80s

#116
post #14

I miss that too (90's for me). Honestly I don't enjoy programming much anymore for this reason. I remember when it was normal for people to write their own data structures for their programs -- and while not "practical," there's a certain joy you get debugging your own sorting implementation that you don't get, say, copying and pasting frameworks' error messages into Google. One problem with today's coding environmen…

Seriously? I see SOOO many people making AMAZING things gluing stuff together. Maybe they're gluing together three.js with WebVR. Maybe they're gluing together the JS Magic Leap support with a Kintec and an arduino. I see artists making art throwing together Unity with a few plugins for networking etc. Sound way WAY more fun than me writing 10 moveto rand(320), rand(240) 20 lineto rand(300), rand(240) 30 goto 10 If y…

> Seriously?

Yes, seriously. Artists are great. I'm not an artist. Unity bores me; it sounds more fun to homebrew an engine and build on top of that.

Re: The Biggest Difference Between Coding Today and When I Started in the 80s

#117
post #86

Earlier quoted context omitted.

Haha- I couldn't be happier to be rid of it. I used GWT for a couple of projects. It's a good useful thing but it was like being back in the 80s (or mayber early 90s)

Google Web Toolkit was great for putting your java in your javascript. Those were the days. I didn't really know Java or JS that well but I could write stuff! We actually used it for projects at Google. Plus anything interesting in java was always not implemented in GWT.

What, is that project gone? I used it recently. I'm too lazy to learn javascript
Post reply on HN