albertsikkema

4 ms·

1.
by albertsikkema 8mo ago
Great idea!
2.
by albertsikkema 8mo ago
Thanks, will keep that one in mind for next time!
3.
by albertsikkema 8mo ago
Thanks!
4.
by albertsikkema 8mo ago
Even if that was the case: is it a real problem? I am not a purist in any sense: whatever tool gets the job done, I am fine with it.
5.
by albertsikkema 8mo ago
It's a pattern I see with more tools (lovable.dev does something similar). However looking at the code produced, lovable seems to be more precise about the code itself: just cleaner even over several iterations. Which is nice because i
6.
by albertsikkema 8mo ago
Funny, actually not the case. Co-authored partly yes, mainly to compensate for my lack of knowledge of the intricacies of English (not my native language). Anyway: take from it what you want, if it helps you: nice! Else: have fun doing some
7.
by albertsikkema 8mo ago
Interesting that you feel this is necessary. Why would a disclaimer be needed? If I read the technical docs for a library and use that in my code, should I explicitly mention that I got this from the docs? I know a lot, but am happy to admi
8.
by albertsikkema 8mo ago
Never thought about using that, thanks for the tip!
9.
by albertsikkema 8mo ago
that is a good one. Will try that next time.
10.
by albertsikkema 9mo ago
That is a funny observation! You are right, that is strange.
11.
by albertsikkema 9mo ago
Figma's API returns 400 for .make files, so I dug into the binary. Turns out it's a ZIP with a custom format: Deflate for the schema chunk, Zstandard for the data, then Kiwi binary decoding. Scripts on GitHub if useful: https:&#x
12.
Show HN: Extracting React apps from Figma Make's undocumented binary format(albertsikkema.com)
55 points by albertsikkema 9mo ago|24 comments
13.
Faking a Rational Design Process in the AI Era: Why Documentation Matters(albertsikkema.com)
1 points by albertsikkema 1y ago|0 comments