The only advice that I have is learn the crap out of the fundamentals - they are the only things that won't change. Then use that deep strength to make surfing the hype cycle less exhausting. Use that to "lean in" and embrace change.
Ask HN: Is back end dev generally easier than front end?
51–60 of 179 posts
Re: Ask HN: Is back end dev generally easier than front end?
#52A big issue I'm having learning back-end coming from front-end was to gauge if my implementations were correct at all. With front-end you usually get immediate feedback: CSS mistakes and infinite rendering loops are easy to spot. With back-end, poorly optimized code can run great in development and even beyond because stacks these days are very forgiving, up to a certain point where you have no idea why things are sl…
Test your backend with real data, not playsets. So use millions of records instead of 3-4.
If you're touching database, then learn SQL, and learn the tooling for your database. Learn how to read a query plan, use the optimiser and design indexes.
Re: Ask HN: Is back end dev generally easier than front end?
#53Re: Ask HN: Is back end dev generally easier than front end?
#54Backend code talks via APIs. Things need to be well-defined so that machines can communicate. Frontend code has that but has to talk UI, too. That's a much looser-defined interface relying on human nature and perception to work. Meaningful performance is based on that perception and never in the areas that were well-designed. Frontend security is something you can't just hide behind your DMZ. And the design much more…
Frontend not done right is often fuzzier and debatable, so it is simultaneously harder to do frontend optimally and easier to do frontend well-enough to get away with.
This is, perhaps, why pure front-end work tends to pay less well. Quite a lot of the time, good enough to get away with is, well, good enough to get away with.
Re: Ask HN: Is back end dev generally easier than front end?
#55No, Backend is not easier than Frontend. Both are equally hard, since you will always be pushed to get the most out of what is currently available in terms of technology & tooling, no matter of your niche. If not, your job will become worth less since you are going to be automated away at some point. A fallacy that I found many frontend-developers have is that they believe Backend is the same as Frontend, just that y…
In my experience (10+ years) backend is almost always faster when it comes to building apps. Not running your code on 300 different devices and OSs, or having to deal with 20 years of backwards compatibility is a big advantage. Plus the library churn as mentioned, I don’t know any ecosystem that comes close to JS (cue the Remix announcement from yesterday…)
At $currentJob, backend features (go + pgsql) are usually done in hours while the FE/app development (React) goes on for days / weeks. It’s a bit unnerving.
So, is backend easier? It depends, but it can certainly be a lot less stressful.
Re: Ask HN: Is back end dev generally easier than front end?
#56If you're concerned about employability, isn't it easier for you to get up to date on front-end which you do already rather than learn something completely new?
Re: Ask HN: Is back end dev generally easier than front end?
#57Just a bunch of examples I can think of offhand as to why back-end development isn't necessarily easier than front-end.
Re: Ask HN: Is back end dev generally easier than front end?
#58A big issue I'm having learning back-end coming from front-end was to gauge if my implementations were correct at all. With front-end you usually get immediate feedback: CSS mistakes and infinite rendering loops are easy to spot. With back-end, poorly optimized code can run great in development and even beyond because stacks these days are very forgiving, up to a certain point where you have no idea why things are sl…
Write automated tests for your code as you're writing it. Hitting the entire system is fine. If your code is properly factored then it should be easy to do. If not, then you get to learn how to factor your code. Test your backend with real data, not playsets. So use millions of records instead of 3-4. If you're touching database, then learn SQL, and learn the tooling for your database. Learn how to read a query plan,…
Re: Ask HN: Is back end dev generally easier than front end?
#59No, Backend is not easier than Frontend. Both are equally hard, since you will always be pushed to get the most out of what is currently available in terms of technology & tooling, no matter of your niche. If not, your job will become worth less since you are going to be automated away at some point. A fallacy that I found many frontend-developers have is that they believe Backend is the same as Frontend, just that y…
Data / API / DB design will take 10%-20% of your time at most (unless you’re a DBA), maybe as low as 1% on a large company where almost everything you touch was made by someone else. In my experience (10+ years) backend is almost always faster when it comes to building apps. Not running your code on 300 different devices and OSs, or having to deal with 20 years of backwards compatibility is a big advantage. Plus the…
But in reality, most backend-work is maintaining and extending existing backends and then things become much more difficult. And that's also why backend is different from frontend: it's easy to throw a frontend away and replace it with a new one - try to do that with a backend - usually much much harder.