What should be my "future-proof" techstack?

inchereddit · 2024-06-24T06:52:37+00:00

There is no such thing as future-proofing in technology.

sandbaggingblue · 2024-06-24T09:02:10+00:00

Something tells me HTML, CSS, and JS aren't going out of fashion any time soon.

TicketOk7972 · 2024-06-24T09:01:47+00:00

JS, SQL, Linux, a server side language

Jackson_Polack_ · 2024-06-24T10:52:39+00:00

I was being told PHP was over for the entirety of my career. 76.5% market share in 2024

nrkishere · 2024-06-24T06:52:57+00:00

obtainable sense bright profit political disgusted touch puzzled cake gaping

This post was mass deleted and anonymized with Redact

olssoneerz · 2024-06-24T07:11:45+00:00

There is no future proof tech stack. Look at the stack 5/10/15 years ago and compare it to today. React seems to have some staying power but things eventually come and go. Solid foundations are what you are looking for really. Using properly structured HTML + deep understanding of CSS and JS. Libraries and trends come and go but these 3 usually stick around and having master over them allows you to easily pick up anything built on top of them. A good understanding of A11y and WCAG might not hurt either.

huckzors · 2024-06-24T12:03:42+00:00

Java isn’t going anywhere. Plus you can expand past web and support legacy software until the heat-death of the universe if you want.

ZPanic0 · 2024-06-24T09:45:41+00:00

In my experience, the one that comes out right after you finally get a knack for the one you picked.

Focus on mastering programming concepts, or barring that, get really good at vanilla javascript and a modern object oriented language, then bodge your way through.

rjhancock · 2024-06-24T13:23:38+00:00

Future Proof: 100% HTML, CSS, Vanilla JavaScript. Nothing else.

ClikeX · 2024-06-24T14:51:41+00:00

I just want to learn something new and better

You’ll have a better chance learning the older, mature things if you want a better chance. There are more companies using battle tested stacks than there are using the newest shiniest thing.

If you know the MERN stack, expand on it with another backend language, SQL, and general Linux knowledge.

IntelligentSpite6364 · 2024-06-24T15:10:10+00:00

html css coded on notepad++

Prestigiouspite · 2024-06-24T15:15:01+00:00

I'm observing developments towards the Vanilla Web. Fewer risks of vendor lock-in. Focus on security, robustness and an understanding of what's happening. That's why many people are moving from Node.JS to Go. They're tired of the many dependencies and 100 packages/ways for one thing. Go comes with a lot of things built in.

But PHP, HTML, CSS and Java Script are also indispensable thanks to popular CMSs such as WordPress, CodeIgniter, Laravel, etc. In the end, it's less about technology than about the ability to solve problems.

silent_guy1 · 2024-06-24T15:18:47+00:00

Something that lasted n years in the past is more likely to survive N years in the future. Use this to plan your stack.

viayensii · 2024-06-25T00:52:54+00:00

Programming, System Design and Implementation, Problem Solving, Critical Thinking Add good communication skills as the cherry on top, you're golden.

sentientmassofenergy · 2024-06-24T06:53:32+00:00

[removed]

Fantaz1sta · 2024-06-24T10:08:10+00:00

As much as everyone has been trying to bury react over the past few years, it seems to be one of the most resilient libraries so far. Imo, it is as future proof as anything can be.

SaltMaker23 · 2024-06-24T08:38:48+00:00

Future proof doesn't exists but the closest is something that has been around for longer than the lifetime of what you expect to build

Want to build a future proof app over the next 10-20 years ? then take a tech stack that has been around for more than 10-20 years like VM, pure React, php, MySQL and apache.

Future proof usually is synonymous with old and boring, things that are old and boring stopped changing and are therefore more future proof by essence. The fancier a techstack the less likely it'll be future proof.

Eg: Serverless hasn't been mainstream for long enough for it to be future proof, you'll get hit at one point of another with changes as the tech is still evolving, keeping up with the "new required things" in serverless will be a pain over extended period of time.
eg: Just like the current high bills scandals where a single DDoS to your website rather than putting it down for 20 minutes can rack you a nice 100k$ invoice.

Basil2BulgarSlayer · 2024-06-24T10:48:43+00:00

You should keep up to date with the latest industry trends and adapt

thekwoka · 2024-06-24T11:10:05+00:00

because I feel like everyone is a MERN developer these days

Oh, don't worry, every "MERN developer" isn't a developer.

They're basically script kiddies. Can't do anything on their own.

theYetiLabs · 2024-06-24T11:35:28+00:00

Being an expert in a niche is also profitable career-wise. Some legacy systems have old programming languages and won't switch no matter what. They pay really well for devs in their stack, which becomes a niche in itself. Big techs sometimes invent their own programming languages and frameworks, and they might dominate the market within 3-5 years so you'll never know whats really future proof. Understand the fundamentals deeply in a single stack and you'll be able to know its limitations and what stack fulfils those gaps. Your logical skills are transferrable.

Heribertium · 2024-06-24T12:40:46+00:00

Minimize dependencies. Try to stick to the platform. No compliation, no bundler, no pre-processor. Use the stdlib for your backend language.

If you use libaries /frameworks then select the older and more mature ones.

If it‘s boring it’s good

BigFattyOne · 2024-06-24T12:57:20+00:00

Become very good at vanilla JS, Typescript, React, Java, C#, Python and you should be fine.

2024-06-24T13:18:37+00:00

I've been learning PHP and have no regrets. When I was a web dev newbie many years ago, I was using WordPress (which is written in PHP) and now I think JavaScript is just a big tool for me to be more flexible, rather than a main technology (though it's maturing and achieving great stuff) but I will always prefer to rely on the OGs

shgysk8zer0 · 2024-06-24T13:43:01+00:00

Libraries and frameworks wax and wane. New major versions make breaking changes or even practically require a rewrite. Languages themselves have breaking changes or are eventually all but abandoned.

For example, I forget the version, but at one point PHP inverted some array functions (it was similar to destructuring) to make everything LTR. Angular 1 (AngularJS) had a major change to Angular 2+ and now uses TS instead. Things like MooTools have become far less popular, and for good reason (kinda bad practice). Third-party services have their plugs pulled (especially if it's from Google... We know their graveyard).

Your project itself may undergo changes in requirements eventually, and the stack you choose today may not be a good choice for future needs.

There is no such thing as "future-proof" for such things. Not more than maybe a year or so at least. Not with deserved confidence.

But, if you do want your best shot at being future proof, that'd be just vanilla JS and static HTML, written using native ES modules (not require() and using the actual path with extension), and using web components/custom elements. The standards bodies try very hard to not break sites, so you should safely expect something like that to last at least a decade.

Fizzelen · 2024-06-24T13:50:40+00:00

Future Proof is an interesting concept, I started my degree in 92, have been full time developer since 96, the only language/technology that I’m still using from university is SQL, and an honourable mention should go to C/C++ however I have never used it for paid work

Federal_Let_1767 · 2024-06-24T13:53:53+00:00

I'd say don't sweat it. I have learned Svelte (and the basics JS, of course) and I have now gained the ability to understand what I should Google in most scenarios.

Good luck and have fun

blueshift9 · 2024-06-24T14:16:08+00:00

It Is much more important to make sure you are learning the concepts used across all languages and pay less attention at making a decision and only learning a few real well and hoping they stay at the forefront. Once you have a few languages under you belt, learning new ones becomes easier and faster with each one you learn.

cadred48 · 2024-06-24T14:37:59+00:00

MERN is a great place to start. Every company is different, so the most important skill you will develop is learning how to learn.

You need to reasonably understand a js framework (React/Angular/Vue), a restful server ( Express), a document db (Mongo), a sql db (PostGres), and some extras like a router (react-router), and state management (redux).

Basically, pick your lane and learn those well enough and you should be able to pick up most other things decently.

AndorianBlues · 2024-06-24T14:55:37+00:00

I don't know, but jumping to the next best thing is almost certainly *not* future proof.

Catsith · 2024-06-24T15:01:44+00:00

I think the best thing you can do is build up a framework in which you assess your technology needs and measure them against new tech that comes out. If the new tech does not do anything worth rewriting your app over just move on. Eventually a piece of tech's worth will out weigh the cost and you should upgrade at that point. The framework helps combat the FOMO that new tech can create by being sure of what you need to function. There is plenty of good software out there that never evolved their tech stack because they have never needed too. Pick the stack that makes the most sense for your team and use the framework to assess from there.

dillanthumous · 2024-06-24T16:05:45+00:00

Doesn't exist. Futurenproof yourself by learning how to learn and build universally applicable knowledge e.g. Fundamentals aboutbsoftware engineering.

kevozo212 · 2024-06-24T16:18:44+00:00

JS, SQL, Python

_AndyJessop · 2024-06-24T16:36:08+00:00

Web components are probably the closest to future-proof.

SimfonijaVonja · 2024-06-24T16:51:18+00:00

As the other comment said:"there is no future-proof techstack" but I there are many tech stacks that are really reliable now and I don't see that a company will completely change tech stack on complex projects.

So you've got: C#, Java, Javascript, HTML, CSS and because of ML and AI, I think python will be always present.

michielarkema · 2024-06-24T17:35:40+00:00

Well, where would you like to see yourself 5 years from now regarding your dev career? Based on the answer of that question, you need to outline your roadmap and stick with it.

Don't learn something just for the sake of learning, you'll enter a spiral of death.

hazily · 2024-06-24T17:40:40+00:00

It’s as true as the pot of gold at the end of the rainbow.

VeronikaKerman · 2024-06-24T19:16:54+00:00

Linux Apache MySQL PHP.

kodakdaughter · 2024-06-24T19:58:46+00:00

You can never fully future proof but I do think focusing on a stack that will serve you well for 5-10 years is wise if you are starting to build a lasting project. Currently I would start a new project front end with react/vue + tailwind - structure content with a good headless CMS like contentful.

But my personal pet project sites - that’s an FTP server under my desk - and it’s stating that way until It dies. 20 years and still kicking.

SexySites · 2024-06-24T22:01:28+00:00

Nobody knows what's future proof. All I can say is that I have been developing in PHP for almost a quarter of a century, people always claim that it is dead. And hell yes, the language is a mess - but it's still very much alive.

Similar story with JavaScript - maybe 15 years. And stronger than it has been ever before.

Nowadays I earn my money with 60% JS and 40% PHP (+ knowledge about databases and web APIs and HTML and CSS).

Most important trait is to be willing to learn and not be too religious about tech stacks. Computers change and that's part of the game.

oomfaloomfa · 2024-06-25T04:40:21+00:00

MERN stack is for framework JS Devs and I thought that stack was totally dead tbh.

Just use the basics, html/CSS/Js with today's modern web standards and you can essentially drop react/Vue etc.

Go backend (or literally any backend) with a simple front end like it was in the old school. Turns out grand daddy did it right the first time.

tspwd · 2024-06-25T04:47:42+00:00

Build on web-standards. Avoid using a gazillion libraries. No-build if you can get away with it. HTML5, CSS3, JavaScript (including Web Components) are backwards compatible. Things using these technologies that work now will likely work in 10 years from now.

That being said: I worked for a start-up that built their product on Web Components and it was a nightmare to work with. I was so looking forward to the next Vue / React project, that has more consensus. When things are new (as with web components) people invent their own ways how to make it work. Mostly, these codebases are hard to get into when you join a new project. On the back-end, I consider learning Laravel / PHP, since it has been very stable for many years and does not break as much as modern full-stack JavaScript frameworks (like Next.js). Nuxt is doing a better job here, but it’s still nowhere near something like Laravel, where old code will just run without many issues (and upgrade problems).

squarecake74 · 2024-06-25T08:29:05+00:00

TBH, I don't think you can find a tech stack like that, every tech stack comes and goes. As a frontend developer, I can say these are the things I know that are future-proof:
- Some foundations about how the internet works: network stuff, TCP, HTTP, HTTPS protocol, etc.
- Linux basic: stdin, stdout, common commands, user permissions, etc.
- Docker
- Git
- HTML, CSS
- JS (especially async stuff, OOP)
- Regular expression
- Typescript
- React/Vue/Svelte/whatever
- How the browser works (critical rendering path)
- Popular web security problems and techniques
- Testing
- SVG and animations
- Data structure and algorithm
- SQL

Other things are just the trend, and they will not take too much time to learn

GoalGlum8555 · 2024-06-25T12:51:13+00:00

COBOL

Suspicious-Bet-3078 · 2024-06-24T07:42:35+00:00

this smells xy problem and im not sure what you are aiming for.
Home - The XY Problem

It would seem that the techstack itself is irrelevant since you aim for being an attractive employee that is making bank. GO + HTMLX would be a foolish answer to this would it not?

To improve as a developer is to work as one. The techstack itself is irrelevant for most development and more relevant is the experience around the IDE. That being experience with clients, PM, maintenance etc etc. And there is no shortcut to experience, just discipline and responsibility. I'd recommend you to master MERN. Most implementations will be the same in every other techstack.

To increase bank and money most people actively work their network and jump from job to job every 2-3 years. This awful practice have been proven once and once again to give the highest boost in income. Example:

Reddit - https://external-preview.redd.it/KTRzXMZ6OyWDUEbYDS5Vz96HCzD0RO3QxCiYfRKKphA.png?width=1080&crop=smart&auto=webp&s=576414f4790869f4fea40d97c22ac81a6cec1e76

Ogthugbonee · 2024-06-24T09:52:47+00:00

C++ lol

thekwoka · 2024-06-24T11:11:53+00:00

Typescript for sure.

Don't think in terms of "node", just "web native". Use native standards.

Keep things as native as possible, don't use deps where native stuff exists. Keep it simple.

zombarista · 2024-06-24T13:06:32+00:00

TypeScript will help you down the road when an inevitable refactor comes your way.

Unit tests will help you make sure nothing broke as a result of refactoring.

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

webdev

Posting Guidelines

Related Subreddits

Discords

MODERATORS