Sometimes, yes. Other times, no. It depends who's leveraging the technology to write these things. Though even in the positive outcome cases, the volume alone is suffocating. My brain doesn't have time to commit all of it.
I've noticed early into AI adoption in the workplace that some colleagues took advantage of the technology by appearing to be hyper-proactive; New TODs weekly, fresh new refactoring ideas, novel ways to solve age-old problems with shiny new algorithms. Fast-forward to today, and this is occurring two-fold. Not only are they trying to appear more proactive, combining this with the fear of AI layoffs, they're creating solutions to problems before the problem has even been fully defined.
For example, I was tasked to look into a company-wide solution for a particular architectural problem. I thought delivering a sound solution would give me some kudos, alas, I wasn't fast enough. An intern had already figured it out and wrote a TOD. I find myself too tired to compete.
Large institutional landlords use Equifax data, TWN, and other 3rd party financial tracking systems to dynamically price renters across the board; new rentals, security deposit, renewals, etc. These are pricing strategies insurance companies use to their advantage, often partnering with landlords to ensure they're getting risk-reduced renters.
Here in Ontario at least, when you transfer ownership of a bike, you have to get it certified for safety. In my case, the bike was an '81 xs400 which required a fork seal replacement and new front tire (due to side wall damage). With parts and labour I paid approximately $500. Fair enough.
Now, if he had recommended a full carb clean and battery replacement, of course that would bring the total to over $1000. Those recommendations are optional though, and your bike can live without them (if you enjoy using the kickstarter constantly ;)
I'm currently enjoying Zero to Production in Rust. It assumes you already have some experience building production-ready systems, and applies rust-specific syntax and concepts to that. As a complete beginner with the language and having read "the book", I find this to be a good resource to apply the book's concepts to real-world scenarios.
Personally, I take it seriously and I think that we at least have the opportunity to make our concerns known here as well.
To boil down my job title would reduce me to a computer programmer. I'm fine with that and it's what I tell to people I meet. In the industry though, it's another story, because we have to play the game in order to succeed. The result of this is that everyone on my team is a senior software person, while I reside in North America, and them, all overseas. You can imagine the pay-gap.
So where does this put me as the more experienced person on the team, getting paid double the salary of those who share the same job title? As the organization expands and goes through its cost cutting phases, I imagine that spot is directly in the sights of, well a coat saving opportunity. Am I paranoid? Maybe.
I think the intention was to spark conversation loosely around SPAs vs SSR. It seems we're at yet another turning point and frankly, I'm enjoying the debate.
It's nice to read that someone else has had a positive experience with the zero2prod book. I'm working my way through it and my impression so far (even after reading the official "book") is that Rust is hard; I enjoy the challenges and the eventual realizations, but working my way through some of the chapters that involve implementations, traits, and macros makes me wonder: Would I actually be able to do this myself in a reasonable amount of time, in a professional setting?
It's actually quite simple even without using some of the advanced features: What I do is create a directory structure for each domain as I explore them. I.e.
As the scope of your work expands, you add another sub-directory or file where necessary. Once it starts to grow in size, you can start making insightful connections via [[keyword]].
Furthermore, you can pretty much take this knowledge base with you, wherever you go, by uploading the vault file to your google drive and accessing it locally via SMB. Automatic save/backup.
Confluence has been the bane of my attempts in finding any relevant docs. Which one is the source of truth? Which one was a draft written by an overly eager to make a first impression, new employee (who is no longer with the company)? Don't even get me started on saving meeting notes to confluence.
These days, I maintain my own knowledge base on Obsidian. If there's ever any confusion or request for more information within the company, I copy-pasta the relevant note from my obsidian bank to whomever person or whichever confluence page they deem the source of truth.
I've been considering htmx for some of our more complex forms with a lot of colocated information. One approach I have in mind is using a small frontend state management library like Alpine.js with the htmx alpine-morph plugin.
In short, if a required field in a different section, i.e. used for a "complex calculation" is changed by the user, then we'd pass that flag in part of the POST request to recalculate.
More code results in more bugs. You need to throw money at software developers to build something, anything really. Only then do you hire a 3rd party pen-testing company for a few days. That's the way it works in our shop anyway. It's unfortunate, but sometimes the expected velocity to achieve MVP glosses over best security practices.
I recently moved to a newly built condo in Toronto and there was a special resident onboarding email, which happened to include a promotional offer from Rogers, advertising a rock bottom deal on internet that I couldn't refuse. I later asked the Rogers representative on the phone how they managed to score the deal with the building developer, and he basically told me that they have an ongoing relationship. They basically have the deal made as soon as the project gets off the ground.
Admittedly I scrolled down to find the obligatory archive link to read this for free, but it's got me wondering now, how do the economist and other online publications make money if we can easily circumvent their paywall (assuming this is their main revenue driver)?
From my experience this is true because the team is so focused on getting the backend business logic sorted out, catering to new customer demands, that they develop new features overnight.
Then just assume the front-end will consume it and output a little, inconsequential DOM element here or there.