News for hackers. Stuff that matters.
Re:The Little Printf by andars on Monday October 12, 2015 @03:54PM (#10376634)
Wow. I'm a college student, but I still feel like a kid. This seems to pretty much sum up every reason I decided not to study computer science and make a career as a developer. I love computing, but I have just gotten tired of the billions of js frameworks and wars about how everything anyone tries to do is wrong. Little printf strikes too close to home. This is a fantastic piece of writing.
Re:The Little Printf by 0942v8653 on Monday October 12, 2015 @04:36PM (#10376827)
> the billions of js frameworks and wars about how everything anyone tries to do is wrong

IMO...

This isn't universal. HN is one of the places where it is the worst. I probably wouldn't be fighting with Go right now if it weren't for HN; I'd probably be using Java. Staying up to date isn't really as important as it appears. There are people having successful careers with COBOL right now, and while that may not be where you want to go, switching between JS frameworks does not sound any better. And you can basically ignore the JS frameworks. They don't matter.

Because of HN I switched from TextMate to Sublime Text to Emacs to Vim. What did I get out of it? Not a thing. Maybe I can type a little faster when I am in vim. But mostly I just get annoyed when the rest of the OS doesn't support the shortcuts that I am now used to. I switched from Mac to Linux to Mac. I got nothing out of it, except that now I get more annoyed when I can't do something on my Mac that I was able to do on Linux. Don't do what I did.

I think it's completely possible to be a developer without all this, as long as you can recognize when you are wasting your time.

Re:The Little Printf by cicero on Monday October 12, 2015 @05:04PM (#10376952)
One of the most cheerful people I met was a guy on the commuter train about ten years ago poring over a greenbar fanfold[1] listing of COBOL code used in a gas station point-of-sale backend. I asked him about it, and he enthusiastically told me about what he was working on and how a problem had developed over night that he was going in to work on. It made me realize that software development doesn't have to be bleeding-edge to be interesting. Indeed, I thought the stability of an established COBOL ecosystem might be refreshing.

1: https://en.wikipedia.org/wiki/Continuous_stationery

Re:The Little Printf by opsforgotmypass on Monday October 12, 2015 @05:51PM (#10377157)
> Don't do what I did.

I try. I don't think going from a GUI editor to Emacs was a complete waste of my time and I still like it a lot BUT whenever you make that kind of switch you gotta stay out of the "this is the best thing ever" mentality. Instead of seeing $EDITOR as the Holy Grail that cannot be eclipsed by anything (which is false) I see it as my favorite tool in a toolbox. I like it but I also recognize it's just one of many tools and it's not always the one I should use and getting frustrated at the differences is pointless.

That last bit took a while for me to realize. I think what helped was seeing other people code without my favorite editor with an IDE or something. Watching Notch coding an FPS using an IDE caused quite a few of us in the HN thread that followed to just kinda take a step back.

I'm still relatively new to programming so hey thanks for the advice.

Re:The Little Printf by davidw on Monday October 12, 2015 @06:41PM (#10377320)
I started using Emacs 20 years ago and have happily stuck with it.
Re:The Little Printf by vezzy-fnord on Monday October 12, 2015 @06:31PM (#10377298)
What separates good programmers from great programmers is that the latter know what not to learn.

If you look at most of the great computer scientists and system architects, they all have very unconventional and personalized setups which are completely far off the grain.

Re:The Little Printf by vacri on Monday October 12, 2015 @06:48PM (#10377348)
I think you're painting too bleak a picture. A balance is needed between chasing the shiny and ignoring the world's movements.

Whether you're a developer, a medical practitioner, a lawyer, an accountant, in real estate, a mechanic, a civil engineer, a teacher, a politician, whatever you have... to be a good professional, you need to keep up-to-date. This doesn't mean latching onto the bleeding edge, but it does mean learning things and occasionally trying new tools or methods.

Re:The Little Printf by andars on Monday October 12, 2015 @05:20PM (#10377019)
"Don't do what I did"

Unfortunately, you're a few years too late... I switched from TextWrangler to vim to TextMate to atom to emacs to vim. Totally pointless and stupid (of me) in retrospect. Same thing again with web. I'm finally learning to ignore the shiny but it seems like everyone I see/meet (both online and in person) are only interested in the backwards-incompatible new release of Express 17.0 for NodeJS, now with ES7 features.

Thanks for your response. Looking back and moving forward, I guess.

Re:The Little Printf by kbenson on Monday October 12, 2015 @09:24PM (#10377900)
Emacs to vim boggles my mind. I mean, I've been a vim die-hard for decades now, but I'm not sure there's a compelling reason to switch from emacs to vim or vice-versa. To my mind they are pretty much equivalent feature wise.
Re:The Little Printf by TeMPOraL on Monday October 12, 2015 @10:39PM (#10378271)
I was considering this actually, but opted for eventually learning evil-mode at some point instead. Vim has superior approach to keybindings, but Emacs has the power of Lisp. Evil-mode feels like best of both worlds to me.
Re:The Little Printf by edwintorok on Tuesday October 13, 2015 @05:00PM (#10383446)
I've mostly switched from Vim to Emacs by using spacemacs: https://github.com/syl20bnr/spacemacs/blob/master/doc/DOCUME...

I like the keybinding conventions (all starting with SPC, hence the name).

Re:The Little Printf by juanuys on Friday October 16, 2015 @06:58PM (#10402532)
Spacamacs is definitely the sweet spot.
Re:The Little Printf by 0942v8653 on Monday October 12, 2015 @09:54PM (#10378042)
When I switched from emacs to vim, I was looking for something that

1. starts up fast - I used emacsclient but that got to be sort of a headache, and still did not start up as instantly as Vim does

2. Better keybindings - I would have used evil-mode but I felt at the time that it would be better to use actual vim.

3. Runs in a terminal window - Absolute necessity, so my only real choices were emacs and vim. I liked the workflow I had with `emacs *.py` or whatever I was doing but I thought at the time that vim would better support it.

A friend actually pushed me into using vim, which is funny because he uses the arrow keys with it... I got used to vim way quicker than I expected to, mostly because it was the only editor I installed at all (I switched from emacs to vim at the same time I switched from mac to linux)

Of course i do not recommend you switch between them but those were my reasons at the time.

Re:The Little Printf by wtracy on Monday October 12, 2015 @11:24PM (#10378405)
The Emacs key combinations overlap with the standard Windows shortcuts in ways that make it hard (for me) to switch back and forth between Emacs and Office. Vi key combinations seem to occupy a completely different part of my brain.
Re:The Little Printf by andars on Monday October 12, 2015 @10:06PM (#10378097)
I should note that each phase was pretty short lived, as in I barely scratched the surface of emacs.
Re:The Little Printf by nostrademons on Monday October 12, 2015 @04:09PM (#10376694)
You can ignore all that and still make a career as a developer.

I started out as a physics major, largely because I didn't want to lock myself into a practical career at the beginning of college. Spent most of my college career avoiding my physics homework by learning lambda calculus, and Haskell, and compiler design, and all of the impractical side of computing. When it came to get a job, I dusted off my Java and got a job in a financial software startup. Left it after two years after discovering that I hated finance but actually liked both software and startups. I've made more tech switches than I can count since, but it's always "Well, what do I need to know to get a job that will pay me and give me interesting challenges?" rather than "What do I need to know?"

You can choose to avoid all the language/framework/editor wars about which is better. None of them are better; it's just some are better for certain circumstances.

Re:The Little Printf by andars on Monday October 12, 2015 @05:08PM (#10376969)
The first part of your experience sounds very similar :). Thanks for sharing it.
Re:The Little Printf by thothamon on Monday October 12, 2015 @04:48PM (#10376877)
The real value of an engineer is 10 or 20 percent in what frameworks they know, but 80 or 90 percent in what they can learn. That's especially true in today's embarrassment of riches world in which no one could possibly learn everything.

It's really a great time to be in software, despite the problems. The world runs on software and this will only be more true in the future.

You don't have to hit one of the pitfalls in the story. After all, printf himself ended up as a happy programmer with a human face. If you love programming and you can stay focused on doing what you love, then no matter what else happens, you win. And if you don't enjoy what you're doing, then you lose, no matter what kind of paycheck you take home.

Re:The Little Printf by MichaelGG on Monday October 12, 2015 @05:38PM (#10377098)
Exactly. Some of the best folks I've hired or worked with had no experience with the framework/language we ended up using. Knowing fundamentals is far more important.

This is also why managers that pick languages based on "hireability" are wrong for the most part. In any non trivial system, learning the domain and existing codebase will dominate the time to learn a new language. It's a nice bonus to have experience with a certain piece of tech, and for baby apps that might be the most important thing. But not for real systems.

Re:The Little Printf by wwweston on Monday October 12, 2015 @07:14PM (#10377430)
> Some of the best folks I've hired or worked with had no experience with the framework/language we ended up using. Knowing fundamentals is far more important.

This is what we want to be true.

It's not how 90+% of job listings are written, and I'm not sure it's how we hire.

Even if we addressed that problem, it'd still only be true at a close approximation: once a framework/lib/language becomes leaky enough, or has enough of a mismatch between its natural invocation and the problem domain, or carries enough of a culture of The Right Way To Do It™, then it's true that experience with the tool matters... as long as the org is more invested in the tool than a solution that doesn't have those problems, knowing the tool's foibles and practices remains important.

Re:The Little Printf by nostrademons on Monday October 12, 2015 @07:43PM (#10377534)
Companies have a wide variety of hiring practices. By making yourself bad at one hiring procedure but good at another, you'll select for the companies that are selecting for developers like you.

Getting a job is not a numbers game unless you just want any old job and really hate jobsearching. I've found that making myself unappealing to the organizations that I wouldn't actually want to work for has paid off significantly in both financial and job satisfaction terms.

Re:The Little Printf by deciplex on Tuesday October 13, 2015 @01:30AM (#10378694)
> This is also why managers that pick languages based on "hireability" are wrong for the most part.

This is 80% of what's out there though, FWIW.

Re:The Little Printf by qudat on Monday October 12, 2015 @06:08PM (#10377219)
Software development is all about solving problems and developers think they are good at it ... so much so that we try to problem solve the solutions (recursive framework hell). I think what this parable is trying to illustrate is that developers ought to focus on problems "with a human face," ones that don't revolve around solving problems that are caused by software development.

JS has a very particular ecosystem and it certainly doesn't describe every other ecosystem in existence today. Basically what I'm saying is if you love solving human problems, software development is an intellectually stimulating and satisfying fields to get into.

Re:The Little Printf by seansmccullough on Monday October 12, 2015 @08:13PM (#10377687)
I think the Javascript framework of the month fad is a complete waste of time.