Step by Step Guide to Becoming a Modern Back End Developer in 2025
Posted3 months agoActive3 months ago
Techstory
supportivepositive
Debate
10/100
Backend DevelopmentSoftware EngineeringCareer Development
Key topics
Backend Development
Software Engineering
Career Development
A step-by-step guide to becoming a modern back-end developer in 2025 was shared, with commenters generally appreciating the resource and discussing its relevance.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
10h
Peak period
1
8-10h
Avg / period
1
Key moments
- 01Story posted
Sep 24, 2025 at 11:13 AM EDT
3 months ago
Step 01 - 02First comment
Sep 24, 2025 at 8:51 PM EDT
10h after posting
Step 02 - 03Peak activity
1 comments in 8-10h
Hottest window of the conversation
Step 03 - 04Latest activity
Sep 25, 2025 at 10:28 AM EDT
3 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45361522Type: storyLast synced: 11/17/2025, 1:11:39 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
Step 2 - Network the hell out there
Step 3 - Use your network to get a job that sort of does BE stuffs
Step 4 - Stick for 2 years
Step 5 - Modify your CV and say your have 2 years of BE experience
Step 6 - Find a real BE job, profit
Getting a programming job >> doing your own project >> all those education out there. Don't bother to learn everything. Instead, learn the minimum amount to get a neighbouring position.
- TCP/IP
- DNS
- TLS
- URL
- And a lot of RFCs
Sysadmin
- Unix
- Webserver (Nginx, Caddy,...)
- Services (Daemons) and logs
Programming
<Any popular language>
Basically there's only three ways to have dynamic content. Either your program is an HTTP server (Java, Node.js,...), it's a script or a program that a server execute (PHP, CGI perl), or it's a program that talks to a web server using FastCGI (and variants).
Databases
HTTP is stateless, so anything useful should be persisted somehow. Go with SQL (MySql, Postgres,...) and then add whatever you fancy.
---
So basically the same thing you needed circa 2010 and earlier. Anything new is something old with a new interface.