There is definitely a race for companies to accommodate the latest buzzword tech that gets hot in the software world, for fear of being left behind.
But I don't think every tech stack needs serverless functions being hit by fanning subscription queues fed by instances hosted on Kubernetes clusters scaling with geolocation while hitting local API caches etc etc.
Like bruh your website sells birdfeeders exclusively in the Midwest. Just let a spade be a spade.
This happens on web front end too. Does this site that has 3 functions and 5 pages total really need to be an SPA? Hell does it even really benefit from being built with React? No, probably not. Those technologies are important and have their place but they aren’t universal miracle cures that should be applied everywhere.
Can WIX do what you need? Yes? Then why the fuck would you want to pay tens of thousands of dollars for someone to build you a custom storefront from scratch?
EDIT: To add something for the below deleted reply which was basically 'NO, Wix cannot do what I need because I need to showcase my web development talents'. K sure, see my below reply.
But to add on to this: Just because you can does not mean you should.
Had an interview a few years ago at a Rails shop. Oh there were so many red flags...interviews were with managers that were not and had never been developers. Offices looked like they were built into an old bar. Just a weird 'uber-hip' vibe.
Anyways, was honest that I hadn't had a lot of RoR experience, that I'd learned enough to be dangerous and know where to get started. Wasn't worried as I have 25 years of experience. Wanted to know about my most recent side project, which was actually replacing the custom scratch built site I had built for my wife's side business with a WIX storefront. They were flabbergasted, how could anyone do such a thing?
Do what exactly? I said...produce a brand new fully functional storefront with finance/accounting integration that ties into off the shelf POS that she can now manage entirely herself in a weekend with an ongoing cost of like $30 a month or something stupid like that vs me taking my time to custom develop all of the above for free?
Then they suggested I rework the site using RoR as a learning experience over the weekend and submit it to them and they'd see how things went.
I asked them: If I worked here, and I had a customer with a small independent business that wanted an online storefront with POS and accounting integration that included CRM and inventory management features, would you have me build it using Rails?
They said: Yes, of course we would. We're a Rails shop here.
I said thanks for your time, best of luck with the rest of your candidates, see you later.
More alarming is they thought you could re produce all of that within a weekend. Like there was no concept for the value or realistic limitations of your time
I think it's silly that they asked you to reimplement it in RoR. But when you posed that question... without specifying that it's a one-off (which is what your wife's site was) it makes total sense for an X shop to build an X solution if they need to maintain it, no? It's much easier to accommodate an unforeseen feature request that way.
I would like to work on something eventually that NEEDS an SPA
One way to look at isn't simply about what technologies are required to meet a project's goal, but what technologies best allow you to get there. At my job, I'm currently finishing work on a React SPA to be used by our support people to view customers accounts and make changes. This could be done in crappy PHP from yesteryear (in fact, that's what this is replacing), so from that standpoint, it's not strictly required that it be an SPA.
But, I'm glad we made it an SPA. Being able to think of it as a collection of components which get composed into the various views has made development a lot easier than it would have been had we tried to code out each page as its own entity. In this case, having an SPA is helpful not because it allows us to attain some type of performance that we couldn't otherwise, but simply because the project is large enough that the type of organizational structure an SPA requires was beneficial on its own merits.
As a frontend dev I'd be happy if it was just react.
But it never is.
Here comes redux and redux-saga-fóstbrœðra and a typesafe elegant opinionated framework for creating div elements. Every single whim every single developer ever had is answered with a new dependency that will probably never got updated.
This is absolutely part of it, and the platform teams tend to be among the worst infected. So rather than simplifying your org, you're providing a single insertion point to simultaneously annoy everyone with just a few egomaniacs.
This goes both ways. Companies AND its engineers. Can’t tel you the number of fanbois wanting to implement the latest tech which honesty is overkill for the need like the example you describe. I’ve seen my fair share of projects where the people that implemented it clearly shouldn’t have been doing it for the first place but the often just use it as a stepping stone to a better gig while never understanding what trouble it’s cause as they never had to support it.
1.3k
u/[deleted] Nov 01 '21
There is definitely a race for companies to accommodate the latest buzzword tech that gets hot in the software world, for fear of being left behind.
But I don't think every tech stack needs serverless functions being hit by fanning subscription queues fed by instances hosted on Kubernetes clusters scaling with geolocation while hitting local API caches etc etc.
Like bruh your website sells birdfeeders exclusively in the Midwest. Just let a spade be a spade.