
Creative technologist đŹ EN/DE/KO đ#ux #hci #cscw #blockchain #ai · he/him
Tallinn, Estonia
Joined February 2009
- Tweets5K
- Following953
- Followers697
- Likes5.4K
The first one in particular works wonders.
You can go one step further and specify a top professional USER in this field. Expertise + designing for real use.
When designing an accounting system, donât say âthink like a top financial engineerâ but âthink like a top CFOâ
Paul Grau retweeted
Burnout is going to be a huge problem!
Working with AI is intense, the mind needs more rest. But AI is so productive that taking rest is costly. The real winners find the right balance.
Replying to @karlhorky
Nice, literally just thought about writing a skill like this myself. What especially grinds my gears are the endless âhistoricalâ comments Claude adds. 6 lines of comments for what really was a bugfix, âthis used to be xyzâŠâ
Paul Grau retweeted
Rail Baltica is one of the European Union's flagship infrastructure projects, but it's also way over budget. Designed to bring the Baltics closer to Europe, parts of the rail line are already under construction in Latvia, Estonia and Lithuania. However, without a major boost in funding in the EUâs next Multiannual Financial Framework, construction may stall.
Read the full story by @pedersschaefer and @LoughlinNeuert: buff.ly/iSyplF1
Replying to @mattpocockuk
Vlad, the author of my favorite DDD book, also wrote some skills for this: github.com/vladikk/modularitâŠ
Hier die Version fĂŒr Estland
Liebe Freunde, wenn Euch wĂ€hrend der Festtage irgendein Verwandter erzĂ€hlt, dass KapitaleinkĂŒnfte zu gering besteuert wĂŒrden, zeigt ihm diese Grafik. Ich habe korrektermaĂen den SolidaritĂ€tszuschlag (Soli) ergĂ€nzt, der gleich zweimal anfĂ€llt. Die Kapitalgesellschaft muss Soli zahlen, und Euch als Anteilseigner wird bei der AusschĂŒttung gleich noch mal Soli abgezogen. Insgesamt gehen vom Gewinn der Gesellschaft je nach Höhe der Gewerbesteuer mehr als 48% ab
you become a senior engineer when you stop waiting for specs to be right and start building the conversation instead.
Replying to @levelsio
Yes, for me too. Also recently it started referencing my custom instructions, very uncanny. Like I told it to write in lower caps, and it replies with things like âhereâs the breakdown, all lower caps:â
Replying to @LefterisJP
I think they mean
Mutter đł = Mutter Nature = Mother Nature
Replying to @destraynor
That talk is so good still. A workshop I attended two years ago referenced it and Iâve been since sharing it with all product people I know
In the end, specs, sketches, visuals, and implementation arenât stages: theyâre parallel ways to think, communicate, and build. Pick the medium that fits your style, but make sure to cover the essentials:
reasoning,
alignment,
memory.
Apart from the visual work, itâs worth investing in curating specs. Collect context, explore directions, and document the reasoning. Figma captures the âwhatâ; good specs preserve the âwhyâ.
Iâve found that once the visual language is set, Figma adds little value for UX prototyping. For my team, information layout and flow are faster to reason about in low-fi sketches, and details can be better ironed out in implementation.
For daily product work I now just iterate on the wireframe stage (Excalidraw) and then go straight to code.
I use Figma only for visual details like choosing icons and colors or when working on fundamental look and feel (design system).
Figma is incredibly important. It allows you to think and prototype UI/UX quickly. Coding doesnt enable even 1/5 the speed of figma of iteration on this.
You need to be able to try stuff. Throw things away. See how it looks. You can always tell when someone skipped this step and went straight to code.
Paul Grau retweeted
The ideal is no more than 3 paints:
- a busy state, local to the interaction
- a loading state for new pages
- the final content, animated in
Replying to @martinrariga @heyequals
Have you considered localization? In some cultures (eg. East Asia) they donât have this red->green schema for bad->good but rather blue->red.
Replying to @makwarth
Surprisingly it seems there isnât any tool thatâs good at both the CRM and the in-app support stuff. Probably because itâs traditionally separate roles that deal with those?
A bit like how there used to not be a single tool good at feature flags AND adoption tracking ;)
I understand a free demo must be very limited but it seemed like a bug that I cannot do anything (1. Enter description 2. Signin with Google 3. Buy now?); at this point I donât understand what Iâd be buying.
Also I thought it guided me to âpick a nameâ but instead it picked one for me and I cannot change it?












