I think it depends on what kind of technical writing.
Are you interested in creating technical content for the outside world or content for internal consumption only. Do these individuals have strength in regular comms but trying to balance a technical voice - or more broadly need work in logic and rhetoric and writing in general?
I hear you. But nothing goes directly into main. The working branch is not sacrosanct you know what I mean? I'd rather clean up anything that leaks in before merging and a good .gitignore can protect against most noise.
This story is gross and not entirely surprising. It is unclear to me why anyone would stick around inside the other Musk co. @twitter that wasn't bound by H1B handcuffs.
The upside in that company is really not there...at least at SpaceX you get to build the future.
I used to use CLion at my previous gig - before moving to eclipse and finally doing everything all day long in VS Code. I wonder if the performance issues of CLion have been addressed or if its still a performance dog.
This disease is just absolutely devastating; I remember reading over the past couple years how the connection between protein buildup and alzheimers was being questioned more in the research. When a momentous breakthrough is a 25% delay in symptoms - you know things are bad.
I think the articles related to staff cuts should often call out what the company size was 12/24 months prior. It's never good for folks to lose their jobs, but companies, especially tech focused ones - grew unbounded during the last couple years.
price predictability is super important in this space. usage based metrics are straight forward to understand around AWS. Burn more machines...cost more $. that equation is easy to understand and predict for. systems where the utilization of the service are not obvious, predictable, understood as a metric upfront are really annoying. we can understand what it costs to run a machine and we have history running services on X number of boxes....the same cannot be said for...how many keys or words I type a day for example.
I love the Iron Man reference. Everyone is always chasing the shiny new thing. Since my company build devtools the shiny thing is the thing that usually gets rusty - which is kind of the whole point I guess.
100% - documentation will always go stale. the source of truth is the code however, and making sure the code is kept shiny is the primary task of engineering. documentation is non-load-baring - you can tear it all down and the project will still work correctly. Legacy tooling can literally cause breakages and security concerns.
there are bots that can resolve this one angle of the problem. they have drawbacks that are great opportunities to improve upon - dependabot loves spamming projects with update notifications and doesn't understand what its actually doing - it is kind of a semi-smart regex parser. valuable but we can do better.
I joined MSFT in 2002 as the .com bubble burst. Microsoft was one of the few companies still hiring and building that year and it was a great place to cut your teeth and learn how to build software at scale.
Congrats to the artemis team, but honestly this project is a testamount to the ridiculous inefficiencies in the government procurement process. Cost+ pricing and siting rules for manufacturing across constituent states led to a bloated antique project.
the only way you are likely to expedite processing of any bans/robo-blocks is to know someone on the inside of these companies who can try to expedite a review on your account status. that itself is a non-trivial lift.
It doesn't take much to trigger very bad things from escalating. Luckily comms are much more reliable now than when Arch Duke Ferdinand was assassinated. Also - no one wants to blow up the planet which is what a direct NATO/Russia confrontation would look like.
Years ago I started using only ubiquity hardware and have never looked back. Never had a problem with the H/W they pump out. Only downside is sometimes its backordered because everyone else wants it as well.
Amazing to see the progress Descript has made in the space. I remember playing with the original beta project years ago. Making an intuitive process for video editing without premiere/avid complexity is really super cool.
the number of projects that require the scaling factor of something like this is very small. git with lfs scales very well for most repositories. That said the actual flow of git is pretty raw. There are other pretty solid projects out there that support undo commands into git.
Stacked PRs are a blessing and a curse - still not convinced they are the correct way to build software as a team.