Why I learned to "make things"

[kyllo]

Yes. And this is in a company where many other people are programmers.

If you are in a corporate environment surrounded by people who don't know how to write code, or even barely know how to use Excel, it cannot be overstated how valuable a basic knowledge of even something like VBA, and a little SQL, can make you.

I started learning to program because I was tired of being faced with the same business problems and productivity drags over and over again. Like being asked to log into a legacy system, look up some performance numbers, copy/paste them into a spreadsheet and e-mail it to management. I've even seen people summing numbers together with a calculator and then typing the sum into an spreadsheet because they didn't know about formulas in Excel. That knowledge could free up at least an hour of that person's time per day, which really adds up over many years on the job.

Not everyone needs to actually be a hacker, but everyone who's even remotely curious about programming should learn some basic skills in order to automate tasks and make oneself more productive, if nothing else.

[lectrick]

When I visit "business type" offices, I am constantly shocked at the amount of wasted time that goes on that I see. The examples you cited are merely the tip of the iceberg. Part of the reason I'm a programmer, I think, is because I absolutely ABHOR wasted/duplicated effort. This "natural programmer laziness" has always pushed me to figure out the way to "automate out all the boring parts".

I think it's a huge market opportunity for a programmer to merely show some poor bastards how to NOT get by via emailing spreadsheets back and forth.

[kevinconroy]

This is great. I wish more business analysts had this mentality of "it's faster to learn it myself than wait for a developer." That's a quality to look for when hiring.

[breckenedge]

I come from a Business Analysis background, now a full-time programmer. I love your mentality, but it can be frightening for employers. Many do not share your opinion. Over the years, I have also become somewhat reluctant to write code when it isn't specifically in my job description.

For me, it's always been a balance of sustainability, maintainability, and competitive advantage: What happens when I leave the company? Who's going to fix my bugs and restart the server? And then there's the flip side: If we don't innovate, isn't that the same as giving an advantage to our competitor?

[diego]

I find it sad when someone talks about "learning to making things" as if he had discovered the moon. Humans have been "making things" since the dawn of times out of necessity. Going through life without the need to "make things" is a relatively recent phenomenon.

[jpdevereaux]

This scares me about modern culture (at least that of middle class America). In grade school, I really enjoyed making things. Simple things, like creatures out of paper clips. To me that was more enjoyable than watching pre-made shows, or playing pre-made games.

When I discovered computers, it became even more fun to make things - websites, animations, scripts to make chemistry homework automatic, etc. My classmates would spend the same amount of time discussing who was the best at throwing pig-skin balls in an arena, or how funny that last South Park episode was.

Now that was before every kid had an portable entertainment system on hand for 24 hours a day, with interfaces tailored for consumption, and operating systems discouraging fiddling. I can only imagine the maker culture is dwindling, especially in younger generations. Is there a way to fix this?

[sp332]

Making little things, temporary things, things for your own use, is still pretty common. Making serious things, or making things seriously, is a skill that has to be learned.

[drewmck]

Perhaps no one should ever blog about anything they do and learn from? Unless, of course, it's a rocket ship or a fusion reactor. /HN

[rana-khandkar]

""Before I could actually make things, I felt like an outsider – who was I to provide advice to these people who actually made things?""

This is so true specially when you are working with an amazing team.

[beambot]

Six or seven weeks after I started...

What exactly were you doing for 6-7 weeks? If you know MatLab & R as well as you claim, I'm hard-pressed to believe that all you accomplished was one git commit, one git clone, and some copying and pasting.

EDIT: My point being... he was already a "maker" -- just not using web technologies.

[kevinskii]

Nowhere did he say that was all he accomplished, and whether it was or not seems beside the point.

[ipince]

He says he's an analyst. Presumably he was looking at data.

[why-el]

A little meta, but this design makes it hard to comment on posts! I spent about a minute trying to find the comments section, which is a click away, as opposed to a simple scroll.

[jimmyhwang]

I would agree that the comment section is not naturally below the content like most websites. However, at least for me, I'm getting annoyed with loading a full website where the comments take up 80% of the entire page. I'm assuming the point of them "hiding" the comment section is a design choice to reduce loading comments that may not be what the reader wants to read.

Maybe a happy medium would be to have a more obvious "click button" that would allow for comments.

[larrys]

It's important to get in a word from the sponsors, 37 signals. Comments would distract from that because your eye would be drawn to them instead of the ads that appear.

[debacle]

Maybe that's the idea.