Having used Braze's services, I would not recommend taking advice from this company. Their API is pitiful and only exposes a limited subset of the service's functionality, and they don't even use token-based authentication (it's a UUID API key)
I think development is one of the coolest jobs out there. With dev skills, you can do everything from building websites to physics models to game development to data science... I'm not saying all you need is coding, but you can't do most of these things without code!
I'm not 100% sure I would be a software engineer, but I can't imagine myself on a career path that didn't involve writing tons of code.
I have a similar but different viewpoint. Software products can be distributed to a old rural minority in africa and to a rich man in the heart of a city atthe same time. For many applications they can be catered as well, mobile/desktop, zoom in for bad eyesight, etc. You just can't do that with, AFAIK, anything else.
Personally, I don’t like the terms ‘microservices’ or ‘nanoservices.’ What’s the value add in describing the relative size of the service? The _domain_ should drive what becomes its own service. Every service should handle the business logic within a particular domain. It’s definitely a goldilocks problem, though, in that there’s a too-small and too-large, and we’re looking for the just-right fit!
That's exactly it. But when you start doing 'microservices' you get the architecture astronauts who go and see into how many silly little services a monolith can be broken up. The end results are as predictable as the original monolith, both end up as an unmaintainable mess in a couple of years.
I predict the same will happen to the 'superstar', it just isn't old enough yet (and at least it was built with some badly needed domain knowledge).
what's the takeaway from this blog post? There's no such thing as a full stack engineer so don't bother learning about databasing and server concerns and devops; just focus on front-end? Are we just criticizing people for doing their jobs to the best of their ability?
A full-stack engineer is not always going to write the best front-end ever; there may be some kludgey stying and some non-semantic HTML (divs and spans!). As a non-DBA, queries may not have optimal execution paths. There may be questionable backend design decisions.
This is an obvious conclusion and does not really speak to the value that a developer brings to an organization. Development is a means to an end, and there are plenty of business cases that an experienced full stack developer can solve in a 'good enough' manner.
We run the risk of letting the perfect become the enemy of the good. Any mature developer should have one or two areas of deep expertise and have enough skill in other domains to get a job done.
There seems to be a lot of health tech in the Denver Metro area. I don't know if it's a 'hub,' but I've heard of several companies and startups in the space.
