Live data from Hacker News

Ask HN: How did you become a software engineer?

news.ycombinator.com

31–40 of 83 posts

Re: Ask HN: How did you become a software engineer?

#31
I was a mediocre (bad) electrical engineer. Software just clicked. I personally believe EE is just harder. Maybe my brain is just better suited to programming and one is not harder than the other. I do know it took me 20 years to let go of the fact I’d never be a true EE. Ego is weird. Fortunately, even in EE, programming opportunities are aplenty and I was able to transition.

Re: Ask HN: How did you become a software engineer?

#32
A friend of mine in the neighborhood started playing around with RPG Maker 2000, and then sat us all down and taught us how to use it. Later, the older kid whose house we'd hang out at, his parents bought him Visual Studio 6 (C++), hoping that his constant time on the computer would make him a programmer (it didn't).

The RPG kid and I copied the compiler, though, and went to town.

I later went to college at the state school and studied Physics (out of interest) and Music (out of not wanting to stop playing). I've since stopped playing.

When graduation was near, I didn't do well on standardized tests for Physics graduate schools, and really I don't think my heart was in it. I didn't get accepted to any schools, so I went to the job fair, since my engineer/comp-sci roommates were doing that.

I interviewed with Microsoft and Bloomberg. Microsoft told me no in the last on-campus round. I didn't know that the traveling salesman did not have a polynomial solution (if P != NP ;))

Bloomberg said yes. I think that my over the top nerdiness and perhaps confidence helped. There's one thing I remember, though. They asked me my SAT scores and when I told them, they seemed deeply impressed. This makes me wonder if the rest of the interview was just a show.

Once I had a good paying job at a reputable firm in a big city... I guess that makes me a programmer. Once you're in, you're in.

Now it's ten years later and I'm working at Datadog, doing C++ stuff (Bloomberg is largely a C++ shop, and I have yet to pivot in any significant way). I like my job. I'd be coding for fun anyway, though. I still code for fun. No kids yet.

Thanks for asking. :)

Re: Ask HN: How did you become a software engineer?

#33
Through Linux initially.

In my early teens, I started tinkering with Slackware and then Debian. I eventually started following tutorials to add cron jobs to do things I needed. I started adding some logic around them.

I kept at it. Kept getting familiar with command line tools, bash scripting, logic, and so on.

I was going to go to Uni for Computer Engineering but changed to Computer Science because the code and logic part appealed more to me.

I went to University for a few years and I was freelancing. There was a strike at the university and other projects fell in my lap. I was making money in my field, so I just kept doing that.

Re: Ask HN: How did you become a software engineer?

#34
I got in to programming because of my other hobbies. I remember playing an NFL game on the Dreamcast. It wouldn't keep statistics from the past years, only the current year. I remember researching and learning about the LAMP stack and made my own statistics tracker for the game.

I've thought about volunteering in my local community with kids who are interested in computers. I think finding out about their other hobbies and finding a way to tie in programming with them would be a great way to get them interested and stay motivated.

Re: Ask HN: How did you become a software engineer?

#35
First got into programming with FIRST Robotics in high school. Did some game stuff as well at the very beginning but never really stuck with it all.

Went to uni for Aeronautical Engineering. Switched to CS for all the wrong reasons. I'm in the camp that if you're going to be doing what "most" software engineering is, you absolutely do not need a CS degree. You'd be better off with Electrical or Computer Engineering (if you're gonna get a degree at all). They open up way more doors than they close by not being CS (dumb example but: EE/CompE masters with a CS bachelors is a v tough thing to manage, much more doable the other way around).

First paid work was an internship I got through a career fair doing web-development which I absolutely hated.

I'm a vulnerability engineer currently. Not what I want to be doing long-term, but certainly a lot closer to it. Still making up for mistakes I made when I was 18 smh

Re: Ask HN: How did you become a software engineer?

#36
I suggest that you read "Mindstorms" by Seymour Papert (inventor of Logo). I think he gets to the heart of the (healthy) resonance between young minds and computers -- efficacy. This is a different relationship than those engendered by, for example, the casino-like air of social media apps and many (if not most) games.

My own observation is that, because modern computers are so small and so fast, you have to intentionally zoom in and slow things down to understand them. This requires special tools and special knowledge that takes patience and practice to acquire. For better or worse these actions aren't very granular: you're either using an app, or you're looking at text, and everything in-between has to fit between your ears. Plus, there are many competing "coordinate systems of thought" (language, but also tools, architecture, convention, idioms) so this is where a lot of people fall over.

Comparatively, we had it easy with the Apple IIe. The distance between running and editing was smaller; the mental model was (mostly) unitary - Basic, or in my case, Logo. The runtime model was beautifully simple, and physical, and easy to understand. It's not easy, but I think the best teachers do their best to recreate this simplicity.

Re: Ask HN: How did you become a software engineer?

#38
I've found that folks around here don't really like it, when I share my backstory. Not quite sure why. The only reason that I'm doing so now, is that I feel it would be inconsistent for me to avoid it. I do enough whining on other posts, so it would be jarring, if I didn't do so here.

> How did you first get into programming? Were any books, blogs, forums, or people particularly helpful for your growth? What is it about coding that got you hooked?

I had always been into electronics, ever since I was a wee bairn. I think my first electronics project was a HeathKit programmable calculator, in the mid-1970s. As my brother noted: "I liked to take things apart." He followed that with "and didn't always put them back together, successfully." BTW: He's also a self-taught engineer, working for a major, major corporation. He did well. Smart cookie.

> What is your experience with university? Did you get a degree, was it worth it, do you think it helped you find work, what did you love/hate about uni?

High school dropout with a GED (that I actually did well at, and graduated before I would have, anyway). It's a long story, but I managed to make a pretty good hash of things, before I was 18.

I started picking up the pieces, and attended a somewhat sketchy certificate mill (since dissolved). Got a student loan, and it was the best investment of my life, so yes, it was worth it. How I picked that particular school, is a story, unto itself (which I won't share). It was a two-year, full-time (M-F, 8-4, no summer off), EET program (generalist electronic technician). I wrote my first software, at that school (if you don't count the HeathKit calculator). It was Machine Code, on an STD-Bus-based MC6800 CPU card. Pretty "raw," but you really learned how things worked.

I enjoyed the characters I attended school with. Many were Vietnam vets, attending on the GI Bill (the "sketchiness" of the school was because a lot of these outfits popped up, in the late '70s, and early '80s, to milk the GI Bill, but this one actually taught you proper). They were a rough lot, but taught me a great deal about working through life's problems (and I had a lot, back then). This was downtown Baltimore, in 1981-3. A significant number of my schoolmates were black. We also had a couple of State cops, attending (also Vietnam vets, but their tuition was paid by the State).

Interesting environment. I enjoyed the classmates, as much as I did the class.

During my career, I have attended over 30 seminars and bootcamps. Did a bunch of Apple DU classes (dating myself -no one else will). I took calculus, at college, then promptly forgot it all, as I never used it. I was just told that "I needed to know it."

> How did you get your first paid work (family & friends, internship, freelance, full-time)?

The school had deals with local companies, for interviewing candidates as electronic techs. I interviewed at a local defense contractor that did microwave and RF work for various defense orgs (not just the US. They also did NATO and Israel).

I started as a bench tech, but had a habit of hauling over all the HPIB test equipment, and automating my analysis. This caught the attention of the Test Engineering team, and I was fairly rapidly promoted to a Test Engineer. In another post[0], I discuss the genesis of my very first project.

The rest is history.

> What do you do now and what do you love/hate about your job?

Thanks to the ageism in tech, I was forced into early retirement, and I write software pro bono for nonprofits. They seem happy with the work I do.

I love my job. I work very long hours at a standing desk, at home. Working is my favorite pastime. Since no one is interested in paying me for it, I do it for free.

[0] https://news.ycombinator.com/item?id=28454887

Re: Ask HN: How did you become a software engineer?

#39
I taught myself to code on TRS-80 Mod 1 at my high school. I had seen a friend write a three line basic program that moved a dot onscreen, and about six months later told my math teacher I wanted to try drawing a circle using the formula we had just learned. I sat down with the Basic manual and did it. A few months later my folks got an Apple II and there was no looking back, I was coding nonstop.

I got my first paying job six months later; walked into a store to buy a book on assembly language, and saw a sign that said “Basic programmers wanted”; I applied, and they hired me for the summer. I kept getting summer jobs writing commercial software. I learned Pascal my first semester in college, taught myself C on their mainframe the following year. Took a year off school to travel and got hired to write some game software, and never went back.

Over the last forty years, I focused first on Apple II, Mac, MSDOS, and Windows apps; then Web development. The last 20 years I’ve focused on embedded development. I’ve worked as a freelancer / consultant much of my career, but also was Dir of Software Engineering at a several startups along the way.

Be sure to talk to them about the embedded industry, which doesn’t get much attention on HN. It’s a huge part of the industry that most people don’t know about. We’re the guys who write the software that makes rockets, robots, respirators, and routers do what they do; most things powered by electricity these days have a got a little processor in them, and someone has to write the software that makes those things work. Practically every form of transportation, medical, communications, and consumer electronics device is either an embedded device or has embedded devices inside it.

Creating good embedded devices is extremely challenging; you often have very limited RAM and Flash, and yet have to create sophisticated, multithreaded software that might communicate with the Cloud via wireless protocols, but have to run for a year on a single battery without failure. In other cases you might be building an embedded device based on Linux, requiring custom drivers and complex applications. In others, you have to create software reliable enough that it can be used in safety critical devices without injuring or killing people, and that is able to withstand hacking attempts to turn your IoT devices into a botnet.

What’s interesting is that I originally didn’t think I wanted to be a professional software engineer, even well after I started coding at paying gigs; it sounded boring. But looking back, as a kid, all my heroes were great inventors, but I was inept as an inventor of physical things. Programming allows me to constantly invent and develop new things, and with embedded, those things also consist of mechanical and electrical components that other engineers create. I love it, and it pays great.

Finally, your students might be interested in this: according to the 2017 Stack Overflow annual developer survey (https://insights.stackoverflow.com/survey/2017), while CS/SE are the most popular degrees among professional developers, most professional developers don't have a CS/SE degree. Of the professional developers surveyed:

* About 23% had no bachelor's degree

* About 42% earned a bachelor's degree in computer science or software engineering undergrad

* About 8% earned a bachelor's degree in electrical engineering or computer engineering undergrad

* About 7% earned a bachelor's degree in computer programming or web development undergrad

* About 20% earned a bachelor's degree in a non-programming-centric degree program (other engineering, natural sciences, math, humanities, system admin, etc) undergrad

Re: Ask HN: How did you become a software engineer?

#40

A friend of mine in the neighborhood started playing around with RPG Maker 2000, and then sat us all down and taught us how to use it. Later, the older kid whose house we'd hang out at, his parents bought him Visual Studio 6 (C++), hoping that his constant time on the computer would make him a programmer (it didn't). The RPG kid and I copied the compiler, though, and went to town. I later went to college at the state…

> his parents bought him Visual Studio 6 (C++),

Wow, ritzy! We always pirated it :) Many, many hours spent in that copy of VS6, definitely a major influence on me growing up.

Post reply on HN