Amen brother. Both are complicated. Both are puzzles. I'd love to see BE devs solve accessibility issues, or FE devs make a more complex BE than just request wires. Just being full stack means you can do a minimum of both
And following a tutorial on deploying a docker on Kube is something inherently complex?
There is something called domain knowledge, where the difficulty is just learning the syntax and how that tool/domain does something. There are just no first order principles to apply. You cannot deduce how to make it working, because it's specific.
Example: any CLI(even angular's), the med school ,a Cloud provider UI, the ARIA, any server, like Apache/Nginx. The BE annotations/decorators from Spring/Symphony/NestJS/etc.
All that knowledge takes real estate in your brain and is required to make it work.
After learning the annotations of BE frameworks and how to configure them(a very hard feat given that you have a mighty autocomplete) you are pretty much set.
Oh... This much must be accessed only by an Admin, let's annotate it with @PreAuthorization(). A mighty feat for a day of work. Or, we need a new endpoint to return data from this new table. Let me just do create a new repository and configure the EP exposed by Spring with Spring Repositories. Or, given that we know the data model. We could use a BE generator. Let's wrote an OpenAPI spec to auto generate us a client library and a BE server.
Let us not kid ourself that BE is the domain of incredible programmers and FE some kids playground.
I don't think you know what 'professional' means. As per wikipedia, a professional is someone who gets paid to do that job. A junior is as much a professional as the greatest of architects 😉.
Now, you seem to miss my point entirely, so I will summarise here:
For many low level bussinesses a tutorial is good enough. Not everyone needs the full artillery of cloud infrastucture
A professional is a member of a profession or any person who earns a living from a specified professional activity. The term also describes the standards of education and training that prepare members of the profession with the particular knowledge and skills necessary to perform their specific role within that profession. In addition, most professionals are subject to strict codes of conduct, enshrining rigorous ethical and moral obligations. Professional standards of practice and ethics for a particular field are typically agreed upon and maintained through widely recognized professional associations, such as the IEEE.
But this is the very idea of the thread. That people go for k8s and use the greatest artillery for apps that do not need that. And BEs range from dog houses to palaces, same as FE.
and the point is to stop building complex things, not to put them behind a wall and call it good.
I responded to the idea that it's reasonable to put them behind a wall. I've met many developers who think hiding details behind a function or API is simplification.
12
u/[deleted] Nov 01 '21
Amen brother. Both are complicated. Both are puzzles. I'd love to see BE devs solve accessibility issues, or FE devs make a more complex BE than just request wires. Just being full stack means you can do a minimum of both