HN user

bb0wn

35 karma

hi.

http://bobbyrussell.io/

Posts0
Comments22
View on HN
No posts found.
Jenkins 2.0 Beta 10 years ago

Very exciting -- a new major version of Jenkins has been a long time coming.

"Jenkins 2.0 is a drop-in replacement of the Jenkins 1.x series of releases and fully backward compatible. There is practically no reason not to upgrade once 2.0 is released."

Skeptical, but optimistic about this claim.

I hope that the Jenkins configuration format is something that can be manipulated more easily in the new version.

And this is one of the many reasons why I've not used paid IDEs. I feel bad for everyone over a barrel with JetBrains because they've dedicated so much of their time developing in their lovely IDEs (many of my co-workers use their products.)

This is not to say that a SaaS model is necessarily bad... it's just that, as a user, one is now beholden to the whims of a company for what is perhaps the most critical part of their work flow.

Just bought my first new car in November. I tried really hard to get a used car, but honestly, it just didn't make any sense -- the cost of financing was much higher, and the cost of the vehicle itself was nearly as much as a brand new model year (this was the case for both the '15 Toyota Corolla and '15 Honda Civic, and their '11 to '13 model year used counterparts.) This doesn't even touch on how difficult it was to find a decent used car in the first place.

I guess if you're comfortable with dropping $10k in cash for a decent used car, then you'd save money, but when/if you can finance a new car for very low interest rates, why tie up your liquid cash like that?

For those families, a new-car payment is a burden — but it’s one they can predict and live with. It sucks to “throw away” $300 or $400 every month, but it’s never a surprise and in exchange they have freedom from surprises.

How exactly is paying $300-$400 monthly for a new car "throw away" money? It's going towards the ownership of a useful piece of property. Maybe the author is talking about leasing? I don't know.

I haven't read the linked book, so I can't comment on which is a better introduction.

I will say that having read the Tannenbaum book, it is a very thorough, bottom-up survey, and you will certainly know quite a lot about computer networking after reading it.

The best thing about jQuery is that it abstracts away most of the browser-specific quirkiness for you. Using jQuery for that feature alone makes it worth using.

I'm not glad that others don't have it -- I'm just glad that it's non-trivial because it means that learning it is an accomplishment worthy of taking pride in. As far as it being a barrier to entry is concerned, I think that having to learn something that is not-so-simple to become a professional separates the wheat from the chaff in the same way that someone like a professional exam or certification would. I have worked with newbs in the past who don't know how to use their tools correctly, and they're usually a net negative re: productivity on a project.

There is no 'overcoming' of command-line bullshittery -- it's a barrier to entry and computer professionals should be glad that it's non-trivial to become productive with your environment -- the time that you put into becoming fluent in POSIX and all the requisite pays off 10x. It makes you that much more valuable to have put in the time to learn an interface that is powerful.

It's hard because there is a lot you can do with it, both in research and in the workplace. I am really biased against software people who are not good with their tools. I don't want to work with people that are counting on their fingers and toes trying to get stuff done -- I want to work with people who embrace the tools and take pride in using them well. Is playing the scales keyboard bullshittery, or the fundamental skill required of being able to play beautiful music?

Thanks for posting this Alex. I really love hearing the others' tales of code enlightenment, and with yours being very similar to my own story, it's especially nice.

Finally, but too little too late in my opinion.

I love python, but I would rather use Rails for web stuff at this point. So many 3rd party libraries are needed to do what Rails can do right out of the box.

I think you hit the nail right on the head here. It can be detrimental to try and learn vim (or emacs, for that matter) while trying to get stuff done, but it is necessary to immerse yourself, as it were.

For those who don't use vim, switch right now (unless you're at work.) If you want to be productive, you'll have to learn to love the home row.

As an aside, it might be worth it to learn a couple of emacs movement commands as well if you're using OS X, as you'll be able to navigate textboxes without leaving the home row as well!