Readit NewsMy only complaint is the chart-data data structures. Each chart type takes a different structure and axis data structure. They bolted on a data table feature (columns and rows), but it's not as documented and last I tried, incomplete.
Where I disagree with the article is on refactoring. It's identically hard both ways. Migrating to new business rules while simultaneously running the old and new system is the hard part. I don't find static typing helps or hurts me in particular. Compiler warnings are useful, but my unit tests catch the dynamic parts as well. Either way a lot breaks and often needs temporary scaffolding between the versions.
The market has been trending towards specialists for a long time. AI may help employees in the short term be more effective generalists, and so be able to compete with specialists. AI may help specialists be even more effective in their niche, while also serve wider needs, and so compete better with employees.
Something I do see happening is companies are doing a lot of low hanging fruit themselves in my space (I do revenue and business analytics). Today, they will get 80% of my specialty done themselves. That is enough for most companies. But that last 20% for those who want it, still requires a specialist like me who knows the domain entirely.
It sounds like a similar use case to yours.
While the server can use the URLs to update the links in the new HTML, if other links outside that content should also reflect the changes params, you need to manually update them.
In my progressive enhancement library I call this 'sync-params' https://github.com/roryl/zsx?tab=readme-ov-file#synchronize-...
But now I struggle with my own motivation having no one to share the burden. Co-working and colleagues doesn't really improve the loneliness much.
I don't have an answer though. I'll probably go back to a team some day.