I find it oddly hard to switch fields. I guess I did web stuff for too long and filled my CV with it. Although i regularily do other stuff (embedded eng, systems eng) and find my existing skills applicable to a large extend employers seem to be put off by my history in web.
Thinking this thought further made me giggle. Imagine devs deciding it's the best option for managing some enterprise device, onboarding would be so funny. "Yeah and now you need to enter the address of our buttplug server [..]"
From reading the docs I see a pretty generic device fleet management framework. What makes this software specific to sex toys besides the intention of the authors and the name? Couldn't you just as well manage - i dunno - a fleet of corporate e-scooters with it?
Yeah, basically I share those doubts. Still I'm still considering rewriting might be worth it at this point still. The question why it came to be is probably mismanagement, changing business requirements, a very inconsistent and highly volatile "microservice" backend made across hundreds of developers across the globe. Corporate shenanigans you name them. So the software being in a weird environment is nothing I can change. I just want this piece, the stuff me and my team works with to still be able to produce new stuff and be as much of a pleasure to work with as possible.
Some notes that make me actually favor a rewrite:
* Despite of being a considerable large codebase not a single piece of software made it past the "just for presentation" purpose - no customers or production software involved. (Also parts of it are infact already cancelled by management and therefore obsolete)
* Team morale is very low as practically any task currently
means dealing with a ton of cruft
* We actually piled up a refactoring backlog, that grew so big it practically will touch everything. Like obsoleting an outdated store package that contains 70% of the business logic. Migrating to vue3 will pretty much touch every view as our class decorator syntax stuff won't be straightforward to migrate. Then theres not much left.
Well I'm not in charge, but I think my input has a high influence in the decision making. The company is a multi billion dollar international multi, so cost is not really the issue here. It's more an organizational problem. Therefore I also don't think moving to a specific framework or a new design pattern will help us by a lot. It's more transforming the current state to _any_ consistent pattern with a certain level of quality. And I'm trying to figure out whether the team would benefit from a radical or iterative approach.
My speculation is a Bit more differientiated. The majority of the hype Tech will bei trash while a few will stick. I.e. i think kotlin is an objectively improved Version of Java and will compete against new iterations of Java and might come Out as Superior.
Public Cloud computing by itself will Take over although i hate it too.
But yeah for some reason our industry has a completely ridiculous amount of entropy in Terms of technology which Others crafts doesnt. Maybe because it's still Young. Maybe we have a Set of trusted Tools in 50 years.
I don't see a real need to campaign against web3 being the unusable dumpsterfire it already is. There is no practical broader usecase actually being adopted by masses. Just a medially inflated niche of people speculating in shit. I think itll Show itself Out producing a few people that cashed out well
I think Main reason is that coops so do not fit Well in our profit maximizing Economy. We do produce profits but due to the Nature of our organization there is no incentive for Investors that seek high margins. ( In fact we dont allow external Capital in to remain in Control of our decisions). So linear growth it is.
I think a lot more growth than you Like is Made by exploitation of the workforce. Without doing that you have a Harder time prooving yourself in the Market.
Mh... As far as I understand this article is promoting the fact to factor in kubernetes or the cloud platform directly into the orchestrator system (i.e. k8s). I think this won't happen. I think k8s was successful because it allows to run unix-like applications with little adoption effort of the application itself.
Yeah it's funny... Now 10 years+ in the web dev business. I occasionally got drawn by the hype, dug myself considerably deep into express based frameworks, sails.js, koa.js, nest.js... But in the end i had to conclude, my first go-to framework django always came out superior in terms of developer productivity. It even eventually covered the bases where i still thought node was superior like async/websocket communication. Imho Django and similar batteries-included frameworks are as state-of-the-art as they've ever been.
It's a nice wrap up of why SQLite might be more powerful than one might think. And actually is suitable for more usecases than testing or client application storage. But imho the title is a clickbaity and not very accurate. The featureset of postgres has so much convenience that I do use in most web applications, like spatial queries and indexes (via postgis), trigram similarity, queryable JSON fields etc. Wouldn't wanna miss all that niceness.