768 karma · joined January 11, 2022
I remember making watch face bitmaps with paint!
And it seems as though it’s happened to the best of us, more or less the entire YouTube iPad app is unreadable in light mode
https://erikdemaine.org/papers/Origamizer_SoCG2017/paper.pdf
^ provides an algorithm for generating any 3D solid via folding a 2D net (origami style)
1. Making stuff is fun and goofy and hacky 2. Coding is formal and IMPORTANT and SERIOUS 3. What cool products and tools can I make?
I feel like this pattern probably happens in many fields? Would be fun to kind of do a survey/outline of how this works across disciplines
(Also, landing page nit, but the kerning on the H1 is pretty wide, and the kerning in the wordmark is a bit tight IMO.)
Basecamp isn’t necessary though, Github discussions is a very decent answer for forums and discussions. It feels like things that go on in discussions are much more permanent and searchable, and can be tied to tickets, etc
??????????
For real, I would absolutely love to know why that constraint was needed. Does anyone have info on why?
This seems like a similar idea with a nicer UI. I don’t really see a huge upside on the “feed” aspect, but this would probably be an improvement over slack.
After getting rid of slack I feel this huge weight lifted off me, and there are far fewer distractions for stupid shitposts and little status updates that frankly just aren’t important to look at more than once a day.
I think there is a very cool version of this where the primitives are simpler and easier to compose (the composition demo I saw was a bit difficult to pull off). Then, rather than program the purpose of individual tags, you can create programs physically on the table
Even though technically we could make forward() a method at the top level in the context of a paint program, we chose to make things more OOPy to prepare them for later when students get to the 2D game engine and there can be multiple sprites to control.
Re: the fact that syntax errors are possible: it is really really hard to make an editor where invalid states are impossible while trying to make expressions easy to enter. Scratch and other block languages do this by forcing you to write code in prefix order. I want to PLUS 2 and 3, vs in Pickcode where you write 2 + 3, and the expression is in an invalid state before you enter the 3. Rewriting 2 + 3 to 2 + (2 + 1) is really hard when you have to think in prefix notation. One advantage that we have is when there are syntax errors, they are necessarily at the expression level, so in the worst case the student can just scrap the line and start over, vs in plain text where the error message for a mismatched paren could land lines later.