Dj honku

https://pin.it/4Z6bkhY4U
This is a work in progress tbh
Idk where it is even going but I figured sharing it

Explainer, susana calendar

so
1 year = 60 DAYS , in my calendar

the standard 1 year consists of 6 of susana years

the rotation of nothing affects it

(technically im 138 years old now)

day one or the new year begins on April 24 (my birthday ofc)

No day offs, one national holiday per year (Sunday brunch)

.
.
.
IM SO EXCITEDDD

Love this
https://www.wikidata.org/wiki/Q2

Sticker guy got some competition

They done YC’ified shinkurt😭😭

Puzzle #2 from the 3b1b monthly series. This one looks harder than the first one (haven’t tried it yet though)

As a person in tech this video is so right
It will piss many people off though

I spend more time designing on claude code than figma these days.

Let me yap a little about the end to end workflow that works for me.

Step 1. Task briefs
Record every meeting. Understand and ask all the right questions, even if out of scope.
The human mind’s job is to ask questions, to have ideas, and solve problems not memorize information.

Export trannoscripts of meetings and upload them to your Chatbot of choice. Prepare projects for each major product you work on, and make that your context base and a living breathing context aware database for the product.

Since I use claude code + atlassian integration on claude, I prefer using claude on the 1x pro subnoscription (for now atleast :])

As a career designer, you probably have trained your mind in three primary areas
1. solving problems
2. UX and usability
3. Aesthetics

You will use the AI to structure the information you get from all your knowledge bases to aid your decision in those three things you are good at. Some prompt engineering is required here to make the AI operate within the knowledge base you provide it. Think RAG techniques as the big brother of this.

Things to not do in this preliminary step:
1. Do not ask the AI for design decisions
2. Do not ask the AI to generate designs
3. Do not use the AI as an ultimate source of truth. Always make it site sources. Hallucinations are still real, especially in complex tasks and high information density projects.

Once design decisions are outlined, I create a new branch, spin up a dev server and primarily work within the application instead of primarily designing on figma first.

It is best to prototype and design in a development environment (or even a separate design environment where there is variation of limited mock data).

The holistic idea is that I prompt changes then use figma for complex components to design static versions that I then plug into the application to test the prototype instead of sending static figma designs to engineers.

I use two things in conjunction.
1. Claude code export pages to figma. (They unveiled this like last week)
2. Figma to claude code MCP

At tasks above a certain level of complexity, I tell claude to export to figma, I make changes on figma then I tell claude to refer to the figma designs to implement changes which I describe on the prompt.

Tip here: tell the AI to create a todo list of sorts to achieve a desired outcome instead of telling it what to do. Give it boundaries and outcomes and it will thrive. You will then iterate on the results using methods I wrote above.

Second tip: AI thrives on organized data. When you have organized components that sit in storybooks and UI libraries on the side of code, and design systems complete with component libraries on figma, and when these two are synced well, AI has less of a hard time being consistent at generating results that meet your frontend brand standards.

Third tip: always make sure the AI knows you are a designer, and include in your initial prompts/skills files that developers will then engineer the output for performance and scalability later.