- Young people to innovate and grow

- Old people to stabilise and ensure sustainability

Fire one group and you get problems on the long run.

The hard part is to keep the balance between each group's influence. They don't have the same needs, desires, agendas, and flaws.

I'm now in my 50s. I tried management but prefer working as an IC. I think I'm good but I know most companies would never hire me. One thing I do now is try to look after all the youngest grads and new joiners. Its so cutthroat now it seems no one has time to help anyone else, so I like helping people get up and running and encouraging them to enjoy their work while being productive and getting their skills up. No one else seems to care.

It's a tale as old as time that developers, particularly junior developers, are convinced they could "slap together something in one weekend" that would replace expensive SAAS software and "just do the parts of it we actually use". Unfortunately, the same arguments against those devs regular-coding a bespoke replacement apply to them vibe-coding a bespoke replacement: management simply doesn't want to be responsible for it. I didn't understand it before I was in management either, but now that I'm in management I 100% get it.

The current crop of LLM-backed chatbots do have a bit of that “old, good internet” flavor. A mostly unspoiled frontier where things are changing rapidly, potential seems unbounded, the people molding the actual tech and discussing it are enthusiasts with a sort of sorcerer’s apprentice vibe. Not sure how long it can persist, since I’ve seen this story before and we all understand the incentive structures at play. Does anyone know how if there are precedents for PBCs or B-Corp type businesses to be held accountable for betraying their stated values? Or is it just window dressing with no legal clout? Can they change to a standard corporation on a whim and ditch the non-shareholder maximization goals?

Sorry, missed this post. I don't have any write ups to recommend I'm afraid, for me it was a lot of trial and error, but what really made the whole thing click for me was setting up a linux box and not being able to remember all the mad incantations and flags for everything I need to do on the semi-regular. So I started just putting them in a user-global mise.toml as tasks with nice descriptions to help me remember what they do, and gradually, over time, I'd think "it would be really helpful if this task also did x", so I'd add that. They're basically superpowered aliases with a vastly better user experience.

Then I realised how powerful it was that I could create tasks with dependencies (ie: when a task requires the user to have jq installed, you can add that to the mise.toml) which makes the tasks beautifully shareable across a team. The only tool they need to have installed is mise, and mise handles everything else for them.

> it is possible to put 500 to 1000 TW/year of AI satellites into deep space, meaningfully ascend the Kardashev scale and harness a non-trivial percentage of the Sun’s power

We currently make around 1 TW of photovoltaic cells per year, globally. The proposal here is to launch that much to space every 9 hours, complete with attached computers, continuously, from the moon.

edit: Also, this would capture a very trivial percentage of the Sun's power. A few trillionths per year.

I use mise for this as it then also gives you a handy `mise tasks` command so you can see what commands are available and what they do. Mise has been a real gamechanger for my ailing memory.

The value extortion plan writes itself. How long before someone pitches the idea that the models explicitly almost keep solving your problem to get you to keep spending? Would you even know?

You also get simplelogin for free, give that a try. Will probably fix your first issue