529 karma · joined May 31, 2022
Comments are vital, but I prefer everything be refactored to make the code the comments, which only happens if you get naming right, the language, libraries and the frameworks don't fight you. Which is a lot of ifs. Even then you need the comments to label parts of code that are exceptions to normal practice, or to fix particularly subtle bugs so that you prevent regressions from happening. (If you want tests to do that, it doesn't obviate the need for comments - you probably want the comments in the code and the test, because you don't want it to be standard practice when you are editing code to discover a new all the failing test cases when you make a change)
Now if the first developer deletes their account or repo everything dies.
I don't think downloading everything is a better solution.
I think Cargo is doing better, but I've yet to get a shared directory working for every build on a system. I shouldn't have to spend 2G per Rust project.
The wrong hands have the money to seek alternatives. All this policy does is keep it out of the hands of the public, and ensure that whatever open alternatives start up won't be OpenAI's.
There are drugs that say otherwise. As a side effect of medication, I've had to increase my calorie intake to maintain my weight.
Not to mention the relative bio-availability of foods differs even when their calories don't. Fats and Proteins need more processing per calorie than Carbohydrates.
I'm also fairly certain there are limits to the human bodies ability to absorb calories. i.e. you could saturate your diet by eating way too many calories, but your eventual weight gain would be at the limit of your body's ability to store fat.
I can't tell if you're on the conservatives side or OpenAI's.
Are conservatives being censored because OpenAI are allowing "woke" training data to be represented, or are conservatives asking OpenAI to censor the "woke" political views?
It's a bad signal that Microsoft can't think of any development worth doing.
I'd also use the meeting to signal any feelings you have about the direction of the team/company, as well as ensuring that your view of where the work is meant to go is valid. Keeping everybody with an aligned idea of goals is important when you're collaborating.
If you feel the need for a deep dive, I'd suggest picking a single topic before hand to ensure that the 30 minutes is used effectively, but I would say that if they're a manager that getting technical is probably not the goal here. As a manager, you want to know about risks and opportunities to make future decisions. I'd aim it at that level.
I wouldn't worry about blowing your own trumpet - you're going to be your only advocate here and you'll be competing with others that do.
I'd suggest just using the documentation. Manuals get used for doing testing and implementation. Using the documentation is like testing for it, and finding those problems right away is the best way I've found to ensuring that the documentation is correct and up to date.
I'm skeptical that these companies were so bloated that they needed to lose large percentages of their headcount.