I would have less of an issue if the inclusion in major indexes was delayed 6-12months but we are looking at inclusion within like 5 days for some of these indexes.

365day lockup isn’t a universal standard. For example for SpaceX 20% of insider shares can be sold in the first few days. 100% within the first 3 months.

Without a public S-1 filing we don’t know what the lockup for Anthropic will be

Part of being a good manager is knowing when to step in and have a private conversation with people before things get too bad. If the bad behavior continues then you follow the process of formal write up’s and eventually termination.

Collective punishment is the sign of a manager who doesn’t know what they are doing and will kill a team.

I can spin up a dedicated server within 24-48hours or a VM within minutes on OVH. Also there have been plenty of white papers written about how much more expensive AWS is when compared to Hetzner or OVH.

The big cloud providers are quite expensive and come with a lot of geopolitical risk/baggage. European governments have safer alternatives within their own borders.

Edit: it’s Lidl who launched a cloud service not Aldi

Having your government infrastructure run in country and managed by your citizens seems like a good idea just in general. It helps to develop local skills and the people living in country have a better feel for the needs of the local people.

I am an American but this just seems like a good idea even if the current geopolitical situation was better.

https://newsroom.cisco.com/c/r/newsroom/en/us/a/y2026/m05/ci...

The waterfall process I experienced went like this:

- Product folks created requirements

- architects produced detailed specs

- project managers created tickets based on specs

- lengthy estimation ensued.

- Then finally developers proceeded with implementation.

- QA tested it.

Each step above involved lengthy review with like 5-10people. If the devs found an issue with the spec or god forbid the requirement it triggered a massive cascade of work for everyone above. Things needed to be reviewed again, customers may need to get contacted, …etc.

I think we can learn from that and optimize for change. Specs as living documents close to the code should be less cumbersome. But, just like anything else large corporations will probably fumble this like they did with “agile” (SAFe I am looking at you).

This is a long way to say specs aren’t bad. Specs that are difficult to change are though.

To have it silently just start adding marketing copy to git commit messages is pretty bad. To have that added text not be visible to the user in the UI so they can remove it before commit is just much worse.

This kind of thing being released speaks to a greater disfunction over there. Not a good look at all and I am not a Microsoft or AI hater. But my commit messages are not where you move fast and break things

A buddy of mine runs his whole CICD setup off an old gaming desktop. They use tailscale to connect to their hosted infrastructure and set it up as a GitHub action runner.

For a solo dev this might be the way to go.

I have been in situations where I was told “don’t worry about cost just get it done”. Then a few years later the business constraints shift and now we need to “worry about the cost”. It ignores that decisions made under a different set of constraints were correct, or at least reasonable, at the time but things change.

One of my pet peeves is when people say “do it right the first time” but the definition of “right” often changes over time. If the only major flaw of this design was that it was expensive; then I am much more skeptical that it was wrong given the original set of conditions that they were operating under.

If this requirement was in place they would be a bit more careful about terminating accounts because the cost equation would incentivize it. Maybe they would be more careful in their automation or require more than one level of human review before cutting off access.

These companies are gatekeepers for their platform. It isn’t crazy to require them to act more responsibly.

Apple’s real differentiator is their silicon. M series chips are just incredibly good and you get a full workday out of them on battery.

The M1 Pro I still have at work is easily the best laptop I have ever used. For side projects I use an M4 air with maxed out RAM and it has no issues with anything I have thrown at it.

I have fixed this by forcing the issue and we get together as a team, set a standard and document it. If we can use tools to enforce it automatically we do that. If not you get a comment with a link to the style guide and told to fix it.

Style is subjective but consistency is not. Having a formal style guide which is automatically enforced helps with onboarding and code review as well.

Maybe that love, or at least liking something, comes from inherent talent to some degree but all the talent in the world won’t help you if you don’t put in the time.

I think you might have a bad one. See if support will do anything for you this is not normal.