Philosophy Of Life retweeted
Saiu o vídeo da 2ª GM. Que criatividade! Sigam a página que vale a pena.
The History of World War II in Minecraft: Every Month
0:00 The Road to War
3:11 Blitzkrieg in the West
4:47 A World at War
7:25 The Tide Turns
9:27 The Long Road Back
10:05 Closing In
11:58 The Fall of the Axis
16:39 A Divided World
4
97
1,849
58,099
Philosophy Of Life retweeted
the guy that made this account is simply genius:
The History of World War II in Minecraft: Every Month
0:00 The Road to War
3:11 Blitzkrieg in the West
4:47 A World at War
7:25 The Tide Turns
9:27 The Long Road Back
10:05 Closing In
11:58 The Fall of the Axis
16:39 A Divided World
2
14
41
8,449
Somewhere, you're the first person someone thinks of in the morning. Remember that on bad days.
5
8
36
4,887
Philosophy Of Life retweeted
Companies that grow through acquisitions often end up running the same process five different ways.
That's what happened at a private aviation group we work with. Every operator it acquired brought its own processes, documents and way of onboarding a pilot. The group wanted one place for everyone to start.
Everyone already worked in Microsoft, so that's where we built it, with one developer. The first month went into the foundation: a group hub, a site for each department and a page for each person.
Then came onboarding. Pilots have 12 items to complete before day one, including a passport, licences, training records and a background check that only security can see. Office staff have nine.
That is where post-merger integration becomes practical. You have to agree on the work behind the shared front door:
> Role-based requirements: what a pilot, office employee or freelance flight attendant needs to provide.
> Role-based access: which department can see and approve each item.
> Workflow state: what is missing, submitted, rejected or complete.
> Access lifecycle: when someone joins, who gets them set up, and who removes access when they leave.
The trickiest case was freelance flight attendants. Some join for just three days. The process has to get them in quickly and remind someone to switch off their access when they leave.
During the demo, the client's process lead asked: what happens if a pilot uploads a picture of their dog instead of a licence?
Each section locks when it's complete, so one mistake could have meant uploading 20 documents again. Now the department can reject one document with a comment, and the person only fixes that item.
That's exception handling. A process needs a way to recover from mistakes without restarting everything.
We shipped six onboarding steps in one week and the remaining three the following week.
If you run a buy-and-build, this is the work that comes before AI. Agree on the process, the permissions and the person responsible for each handoff. Then you have something an agent can help operate.
That's what happened at a private aviation group we work with. Every operator it acquired brought its own processes, documents and way of onboarding a pilot. The group wanted one place for everyone to start.
Everyone already worked in Microsoft, so that's where we built it, with one developer. The first month went into the foundation: a group hub, a site for each department and a page for each person.
Then came onboarding. Pilots have 12 items to complete before day one, including a passport, licences, training records and a background check that only security can see. Office staff have nine.
That is where post-merger integration becomes practical. You have to agree on the work behind the shared front door:
> Role-based requirements: what a pilot, office employee or freelance flight attendant needs to provide.
> Role-based access: which department can see and approve each item.
> Workflow state: what is missing, submitted, rejected or complete.
> Access lifecycle: when someone joins, who gets them set up, and who removes access when they leave.
The trickiest case was freelance flight attendants. Some join for just three days. The process has to get them in quickly and remind someone to switch off their access when they leave.
During the demo, the client's process lead asked: what happens if a pilot uploads a picture of their dog instead of a licence?
Each section locks when it's complete, so one mistake could have meant uploading 20 documents again. Now the department can reject one document with a comment, and the person only fixes that item.
That's exception handling. A process needs a way to recover from mistakes without restarting everything.
We shipped six onboarding steps in one week and the remaining three the following week.
If you run a buy-and-build, this is the work that comes before AI. Agree on the process, the permissions and the person responsible for each handoff. Then you have something an agent can help operate.
8
19
31
6,342
Philosophy Of Life retweeted
You can't threaten a team into using AI.
Proton's CEO just told staff they'd be re-interviewed about how they use it, and that their jobs could depend on the answers.
Before you make it mandatory, make sure you've given them:
> one coding agent and one shared setup, so nobody is working it out alone
> a security answer, so people know what data they can and can't put in
> time for it, because they still have the same deadlines
> real work to learn on, from their own backlog
> someone who has done it sitting next to them
> telemetry, so you can see what's actually being used and what gets accepted
> a measure based on what shipped, because tool usage tells you nothing
If you've done all that and someone still refuses, then you've got a different conversation to have.
Proton's CEO just told staff they'd be re-interviewed about how they use it, and that their jobs could depend on the answers.
Before you make it mandatory, make sure you've given them:
> one coding agent and one shared setup, so nobody is working it out alone
> a security answer, so people know what data they can and can't put in
> time for it, because they still have the same deadlines
> real work to learn on, from their own backlog
> someone who has done it sitting next to them
> telemetry, so you can see what's actually being used and what gets accepted
> a measure based on what shipped, because tool usage tells you nothing
If you've done all that and someone still refuses, then you've got a different conversation to have.
24
13
43
8,056
Philosophy Of Life retweeted
this account shares useful prompts:
BREAKING NEWS 🚨: Gemini Notebook can now record an hour of anything on your phone and build your notes from it, like a $50 per hour note taker.
Open the app (it used to be NotebookLM, it's free), tap the mic, record. Then paste these 7 prompts:
4
37
1,144
146,946
Ignoring people who drain you isn't weakness. It's one of the smartest moves you'll make.
3
29
175
8,920