Placca retweeted
playin' with stickers again 🕹️
different materials, sounds, wear marks
via css or webgl 🧑🍳
Placca retweeted
Your name. Your number. Your country.
18 countries are now in the KONK! Cap Workshop. Pick yours, put your name on it, choose your number, and take it to the table.
Make your cap free at konk.world
From Ghana to the world. 🇬🇭🌍
#KONK #CountersBall #Ghana #BottleCapFootball #IndieGame #MobileGaming
Placca retweeted
The reason I always hesitate to comment on issues of students’ BECE grades is to avoid committing a fundamental attribution error.
The tendency is to always blame children for poor performance without considering the situational circumstances that may have contributed to those results.
I am living proof of this.
I got aggregate 27 after BECE and it was so good that my father had mother make me guinea fowl light soup . And if you know northern fathers and their guinea fowls, you know this is was a big deal.
But I had only one teacher for the whole three years of JSS. He taught Mathematics and Science. We didn’t have teachers for the remaining eight subjects. We had no textbooks, no desks and no electricity.
The year group ahead of us had only one person who passed and proceeded to secondary school. The rest failed.
The only handwritten notes we had for some of the other subjects were handovers from previous batches of students, dating back five years. Those students had one or two teachers for the other subjects, who gave them notes before quitting along the way. That was what we depended on.
Mind you, those notes didn’t even help them pass. They failed too. But at least, they offered a reference point for what JSS Agric, RME, Social Studies or English looked like.
Imagine merely laughing at me for getting aggregate 27 without considering the full context and the extenuating circumstances.
At the time, the cutoff point for all senior high schools was aggregate 30. Only three of us, from a class of 20, got within the mark and went to secondary school (aggregates 25, 27, 30). The rest either went back to JSS or ended their education altogether.
I got admitted to my beloved Kanton Secondary School, and in my SSS class, I had the worst aggregate. No yawa lol.
But after three years of secondary school, I got aggregate 13 and went straight to Legon.
At Legon, I got a scholarship and went to America to complete my Bachelor's degree.
I know the grades sound bad on paper, but sometimes, those terrible grades are a product of circumstances far beyond the child. And sometimes, an opportunity at a good secondary school can be the game changer.
So, don’t laugh at a kid with aggregate 35 who wants to go to Presec.
Investigate the circumstances that produced that 35. That child may have been performing at the absolute limit of the opportunities available to them.
The context is important. Perhaps you give them a different environment, better teachers, better resources and a proper opportunity to learn, and you may see a completely different student.
Sometimes, the grade tells you what happened. It doesn’t tell you why.
The funny thing is that the author of any program running on your machine can literally access any part of it.
The limit they go is only determined by their ethics.
Forget all the permissions they keep asking for, it's to give you the illusion that you're in charge.
Placca retweeted
Keep your problems smaller than your life. A flat tire is a flat tire. A bad meeting is a bad meeting. A canceled flight is just an extra two hours. These things become catastrophes when you let them. But they stay manageable when you remember the depth of your real life- the people you love, the work you care about, the beautiful years still ahead. Zoom out. Fit your reaction to the size of the problem.
This quoted post is unavailable.
Introducing Canvas UI, the first ever html-in-canvas component library.
Your DOM is the render target now. Real-time shaders over real, interactive UI.
24 components. React, Vue, Svelte, vanilla TS.
Free. Open source. 🧵
canvasui.dev
Placca retweeted
We hired a new VP of Engineering who is obsessed with agile methodology.
He called a meeting on his first day and said we need to transition to 2-week development sprints.
He wanted daily stand-ups, retrospective boards, and continuous deployment pipelines.
He wanted us to actually write new code.
I realized immediately that he was an existential threat to my lifestyle.
I let him finish his impassioned speech about workflow velocity.
Then I stood up, walked to the whiteboard, and drew a single horizontal line.
I told him agile sprints are a localized solution for a localized mindset.
I said our infrastructure operates on a Zenith Release Cycle.
He asked what a Zenith Release Cycle was.
I told him it's a holistic, macro-stabilization framework where we observe the system in a state of prolonged stasis.
By not touching the code for 18 months, we allow the legacy dependencies to organically settle.
I told him that deploying bi-weekly updates creates micro-abrasions in our database architecture.
I used the phrase chronological data scarring.
The CEO was in the room and audibly gasped.
He told the new VP that we can't risk chronological data scarring just to satisfy a trendy tech buzzword.
The VP looked at me like I'd just invented a new color.
He was completely paralyzed by the sheer density of my fabricated jargon.
He quietly agreed to adopt the Zenith Release Cycle.
We're officially scheduled to deploy our next update in the third quarter of 2027.
I spent the rest of the afternoon buying things I don't need on Amazon.
Agile is a disease invented by people who want to be punished for their salary.
I refuse to participate in my own suffering.
Placca retweeted
i hooked up a rotary phone from the 1920s to an AI agent, that replies on a mechanical display
it’s like a dumbphone without distracting notifications
here’s how i built this w/ @cursor_ai
Placca retweeted
Been coding with AI a lot this week and it's wild how much of an edge real architecture knowledge still is.
Seeing frontier models constantly reach for the wrong abstractions. Easy to course-correct, but only if you already know what good looks like.
Most software engineers are facing an identity crisis bordering on depression.
As CTOs aggressively evangelize tokenmaxxing, a class divide ensues.
The lazy. The lazy push code. They don't write it. They don't manually test it. They don't even read it. They're on autopilot. See Jira ticket, prompt for task, submit code. Many of them are barely on their computer the whole day. A comment on the PR asking why they did this? The lazy ask AI. A Slack message? The lazy ask AI. Need to prepare for standup? The lazy ask AI. As long as it sounds enough like them and isn't detected. Some of the lazy are even overemployed, and work multiple jobs. The lazy smart ones get away with this, and even rewarded. After all, software engineering for the lazy is just a dance to convince your colleagues you're smart and hard working.
The craftsmen. The craftsmen are tired. Very tired. 15 PRs in queue. Slack blowing up. The entire burden of review falls on the craftsman. The burden of understanding. They try. They work their way through the code, thoughtfully commenting to improve what ships. The response? A lazy: "That's a clever idea! You're absolutely right." with an incorrect change. It's fine, the craftsman says. I can fix them. They write a doc urging his colleagues to be better. The next day? 20,000 line PR to review. Day after day, their workload grows. Bugs seep into production. No one seems to care. Another round of AI is thrown at it. Their animosity to their colleagues rises. Eventually, they give up. It's just not what it used to be. The craft they loved is dead. They eventually wake up, a lazy.
This isn't all companies. Many companies are genuinely more productive, adopt the right set of principles and practices around AI development and have highly talented teams that trust each other. It tends to happen in bigger companies that are 10+yrs old with a higher talent variance. But it happens. A lot.

























