Dividing front end from back end is an antipattern

Re:Dividing front end from back end is an antipattern by dakiol on Saturday July 25, 2020 @03:34AM (#23947452)

I don't call myself a "full stack" engineer. I call myself a software engineer (or software developer); this pretty much means: I am a problem solver. Do I have to design a relational data model? Sure, there I go. Do I have to keep the state of a client side app in sync with our server's database while client is offline? Ok, let's do it. Do I have to design an api that exposes resources to the public? I can do it.

If I don't know how to do something, I go and learn what's the best way to do it (by reading documentation, books, or just be asking more experienced devs). That's all.

If a company I want to work for is looking for "JavaScript" devs only (or "Python" devs only), that's a red flag... But if I really want to work for them, I would just apply because if you are a decent software engineer/developer then it does not matter if the job involves JS or Python or PHP. You can learn without too much trouble.

[ Parent | on HN ]

Re:Dividing front end from back end is an antipattern by Aeolun on Saturday July 25, 2020 @08:10AM (#23948590)

Most importantly, I think I know how to build things so that I can fix whatever I do wrong later, without having to tear the whole thing down.

[ Parent | on HN ]

Re:Dividing front end from back end is an antipattern by randomdata on Saturday July 25, 2020 @10:53AM (#23949613)

I share this mindset, but I don't love pigeonholing myself to software. If the problem is better solved with a mechanical machine, I'll build that instead. If the problem is best solved by baking bread, I'll do that. Software has its place, but is not the best solution to all problems.

[ Parent | on HN ]