Normally I hate timesheets, but there is some satisfaction in putting "Company meeting: 4 hours" into a timesheet and knowing the managers will have a mild heart attack when those 4 hours are multiplied for every person across the company when they look at the end of the month report.
You would terminate someone for...having an opinion? They didn't mention the company they worked for (if indeed it is their company and not some made-up example).
Little secret: outside of self-proclaimed "leaders" in the Linkedin bubble, most normal people think like the writer, if not put so eloquently. They have jobs to do, and know how to do them, and do not appreciate being dragged into a 4 hour meeting to listen to bullshit. Of course they'll do it if they are told to. But if you are a "leader" you would be conscious of their time and not waste it on self-congratulatory claptrap.
I think (or rather, hope) that this is a symptom of the low interest-rate era, and companies may be less willing to waste money and development cycles on chasing the latest shiny.
Russia does not have a "justice system" in the way that we would understand it in the West. Instead it has (and indeed, always had) a system of patronage and bribery, where your status within the system determines your sentence. If you are an oligarch, or the son of an oligarch, you will walk free, unless you cross Putin. If you are a nobody, you pay off the right people or you go to prison or end up freezing to death in a foxhole in the Donbass (Wagner recruits directly from prison, just as Stalin emptied the gulags for his cannon-fodder in WWII).
That's just how Russia is and always has been, and unfortunately, very likely always will be.
Is Denis guilty? Perhaps, but he will not have had a fair trial by any Western standard, and so we have to presume innocence.
I contribute what amounts to a few euros a month to a few open source projects. I do these because these projects have significantly helped my career and added to my personal enjoyment. Perhaps not much in the grand scheme of things, but I feel I owe at least that much, especially if I'm not able to help in other ways (PRs for example).
However, when I've asked employers to do the same - just throw what to them is would be tax-deductible chump change at some projects that have helped them make fortunes - there's lot of muttering and foot-dragging. More trouble than it's worth to do the paperwork, apparently.
So we end up in a ludicrous situation where essential software, used by companies with revenues in the billions, depend on a single, relatively impoverished and stressed out developer toiling in obscurity. Google or Facebook or Microsoft could, for what amounts to a rounding error, have just put him on an annual salary or grant.
And yet the movie industry - which has over half a century's head start over gaming - still has its fair share of studio excess, cost overruns and expensive flops.
There are consultancies whose entire expertise and premise are advising on AWS billing to companies who already know AWS, so the idea that a newbie should be aware of whatever magical incantation to limit their spend is ludicrous.
It's not really about "innovation", it's about fooling investors, customers and employees/gig workers for as long as possible until economic, technological or legal reality catches up with you. See: WeWork, Uber, etc.
> That Star Trek trope of "everything in the Universe is just like us with different faces" really needs to be put to rest.
Budget constraints aside, Star Trek aliens were used as a prop to explore extremes of terrestrial human behaviour and culture from an outside perspective - take a human and remove emotions and have them governed purely by logic, you get a Vulcan. Take a human and exaggerate their tendencies towards violence and honour, you have a Klingon, and so on.
Even in the original series there were truly alien aliens - for example the Squire of Gothos was a being of pure energy who just assumed human form, Devil in the Dark had a silicon-based creature, and the Tholians were an intelligent crystalline species who could only exist in high temperatures.
There's reasons beyond just legality. If you are in a company which has a culture of firing people at any moment for no (obvious)reason, you're going to see high turnover and low morale as nobody wants to work with an axe over their heads, particularly in an industry where it's hard to replace people.
After playing for some hours with the new Turbo on a side project (with Django as backend), it mostly works fine.
One thing that is kind of broken out of the box is form submissions: so a common pattern with server side rendering is to re-render the form with validation errors, but otherwise redirect to wherever.
The workaround here I think is to use turbo-streams and just re-render the invalid form HTML snippet rather than the whole page. While this is probably ok for most cases, I have some forms (3rd party library stuff) where this is going to be more work than I'd like, and due to a bug in the beta release you can't override the default form submission behavior - Turbo throws an error if a form POST returns anything other than a redirect. So it's probably not quite ready for production yet.
I've used Turbolinks/Stimulus with Django. I can't speak to the new hotwire stuff, other than the relatviely minor Stimulus2 changes.
Honestly it's pretty straightforward and the API is tiny. It's great for that grey area between serving server-loaded static pages and full-blown SPA - for example CRUD apps (and lots of things are pretty much CRUD apps). Turbolinks gives you a "poor man's SPA" for little effort (albeit with some gotchas) and Stimulus is fine, although it gets tedious for when you have to work with a lot of DOM elements e.g. "when I click the Subscribe button, change it to an Unsubscribe button". Maybe a less imperative framework like AlpineJS might be simpler.
I use Turbolinks for some Django projects, so took a look at how much work it would be to port these over to Hotwire/Turbo. Very little in the way of docs to go on right now and what little there is in the way of examples is buried in Rails gems. Should be mostly straightforward, with a thin Django middleware to check headers and the like. I guess The Turbo Stream stuff could be adapted to Django channels quite easily. I'll wait and see how and when they improve the documentation, especially on the Rails-agnostic front.
So far, this looks very much tied to some Rails gems : documentation for installing outside of Rails is pretty much non-existent, I guess to be expected for a beta. My issue with Turbolinks/Stimulus is really that it's developed pretty much behind closed doors at Basecamp and we maybe get a shiny new release every few years, instead of being developed as a more open source project with incremental improvements and input from a wider group of contributors with diverse needs and insights than one small team at one company.