1. 程式人生 > >Ask HN: How do I transition from full

Ask HN: How do I transition from full

I too started w/ web dev (PHP and HTML (so funny to think about those first days starting out)), but ended up moving to the backend (Apache Suite) for my current job, and took up lower level programming from there, so here's my 2 cents.

#1 - throw out the "systems engineer" title. It's ambiguous, can't really be achieved

, and I've seen guys out there who are actually Systems Engineers (in job title) who are so good that it's almost sickening - makes me want to quit. So first, get rid of the title.

#2 - Learn a low-level language. You seem to be already doing this (I'm a RUST guy myself). Here you'll probably see (if you haven't already), that there's a focus/efficiency that isn't necessary

for CRUD apps (e.g., passing references, using as little memory/cpu as possible, etc). But that's kind of what I like about lower languages, you get almost intimately close to the machine and understand on a completely different level that a web dev.

#3 - And this is something I'm still dealing with: switch your dev mind from higher-level web work, to lower level work. What do I mean? Well a lot of times in web dev, you're building at the application level (e.g., CRUD apps). However, I'm noticing for a lot of lower-level programming, you're building beneath

the application level. I'm working on a load balancer at the moment, which isn't really a part of the application, but kinda sits underneath it. The thing about lower-level dev work is that it's not really the show-boaty type of thing that a React can be (oh look at my shiny UI). And in my opinion, it doesn't get celebrated like it should have. I have SO much more respect for lower-level guys, after jumping into that world.

TLDR; systems engineer title is ambiguous, learn a solid low-level language and stick with it, reframe your thinking when it comes to designing/planning what you build