HNHacker News
TopNewBestAskShowJobs

drylight

103 karma · joined August 7, 2010

submissionscomments
drylight··on Bram Moolenaar has died
As an old-time Amiga user, I was pleased to read that Vim first appeared on the Amiga.
drylight··on Sam Altman says era of remote work is over
Interesting that he may have had some positive things to say in a 2017 blog post, but has now been deleted? https://blog.samaltman.com/how-to-be-successful-in-a-job-rem...

ChatGPT told me about said blog post.

drylight··on Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API
You should believe them and others on here. Atom is slow. No way around it.

If you or others say that it's fine, then you're suffering from Stockholm syndrome, having been taken in to the cult of Atom.

drylight··on HealthCare.gov Sends Personal Data to Dozens of Tracking Websites
Give $563M to Accenture and you get some really shoddy work http://www.healthcaredive.com/news/accenture-snags-new-5-yea...
drylight··on You only get 1,000 lines of code a week
That's a lot of "copy and paste 'programming'".
drylight··on Apple seeks to trademark “startup” in Australia
Please don't say Linux.
drylight··on Why is YAGNI a good rule?
You're correct when you say about YAGNI not necessarily leading to "elegant, short, and easy to maintain code". That is, in the end, up to the developer's skill.
drylight··on Why is YAGNI a good rule?
Design Patterns are one of the biggest culprits in large, over-engineered patterns. http://37signals.com/svn/posts/3341-pattern-vision
drylight··on Why is YAGNI a good rule?
YAGNI is not about being lazy, it's about being smart about the code being written, about the craft.

Over-engineering, architecture astronauts, hurt a system a lot more than someone following YAGNI. Making systems that are a big mess of hard to understand and modify code (even worse). I've seen this happen again and again.

Architects sitting in ivory towers pump out Word documents which result in overly complicated systems. Large, slow, waste people's time and money. The whole idea of "oh, in 10 years we may want to handle this and that" adds unecessary code which then needs to be tested and creates many more points of failure. And did I mention slow? These hairy-balled monstrosities are terribly sow.

If over-engirneers got paid by the line of code, they'd be millionaires. If they got paid for writing elegant, short and easy to maintain code, then they wouldn't have two pennies to rub together -- the YAGNI developer would be sitting in his yacht.

You Ain't Gonna Need It!

drylight··on Dapper.NET - "micro-ORM" that poweres StackOverflow goes opensource
If you hang out on github, and do your social coding over there (or simply prefer git over Mercurial), here is a github fork of the repository: https://github.com/dbarros/dapper-dot-net
drylight··on Ruby is beautiful (but I'm moving to Python)
A Java developer complaining about Ruby's supposed verbosity? What's the world coming to?! When one looks at Java code, 90% of it is just syntactic sugar, which doesn't add much to the actual working code. One has to filter through large amounts of white noise to get to the crux of the code. Not so with Ruby (and many other languages).
drylight··on Why Pixar uses Microsoft's Azure
If a job posting to work at a Pixar server farm is anything to go by, they actually use Linux for their films.
drylight··on Bill Gates: In Five Years The Best Education Will Come From The Web
I wouldn't count on any predictions made by Gates. He said that the spam problem would be solved. And that was meant to happen some 5 years ago.