coderdd
coderdd on Hacker News
Having read the book Dealers of Lightning about Xerox PARC and Kay,I think Smalltalk 72 was the original smaller simple language, with which children were taught.
Then others at Xerox added more professional stuff, the kind programmers would want, which resulted in Smalltalk 76 and so on. These were not as approachable for children anymore allegedly.
Nowadays there's Squeak which is a Smalltalk implementation, which influenced Scratch I think (first version of Scratch was written in Squeak).
Search the internet for Adam Kay's documents on Squeak and educating children, helps to put on context what he had in mind (if you, like me, just install Squeak and expect a stunning tutorial... it's not like that, at least I didn't find).
Kay also said, having an IDE only takes you to the 70s from the 60s too... So there's work to be done yet.
Technical skills, shared values, collective memory. If you were wondering.
I recall reading it, and strangely I felt that making of the game is just a side-happening, while the author was on pursuit to get into movie industry rather.
Am interesting contrast, given most people know and are amazed by the game in retrospect.
Glean, at least tangentially?
We watched it recently after decades of hearing how great a film it was.. it was a superficial letdown instead.
Decryping is ephemeral though. No request body gets stored, except in RAM. Malicious operators etc, well that's always a possibility, but they supposedly have controls for that. And as others noted, they are not the only players in the path of serving your data.
How does it compare to PlantUML with the C4 plugin is the first question coming to mind.
A turn-key solution to avoid confusing turkey and Türkiye.
Not sure I used Piviti, but used Shortcut, Openshot and Kdenlive. Kdenlive wins hands-down in stability and least amount of UI glitches.
(I recall that these interestingly share the same video editing backend, just the integration is different?)
Tic80.com - might overgrow it quickly, but excellent for start. Has Lua, Fennel.
> If you want to press C-c, use the right Control key with your right hand
First thought: but C is on the right.
Second thought: ah, I use Dvorak
I was pondering about using simple decentralized databases that are kept synchronized asynchronously.
I arrived to a design where SQLite databases would be synchronized by Kafka. Kafka is really robust, and has a friendly semantics when configured to be in-order delivery.
The catch is, you don't issue writes to SQLite anymore. You write Kafka messages, and have to prepare to resolve concurrency problems at read+write-to-db time. For example, user registration is not an atomic action anymore - you write a registration attempt message, and then it might race with a concurrent registration attempt from an other node (say due to retries and random load balancing).
You resolve the race in message-reception time (doable due to stable order on multiple reader nodes). I expect this would work nice, but needs you to rethink all actions that used to be synchronous db writes.
I worked at Google and have no idea what they mean by stacked change. You could push multiple changes to a single CL, but those were rarely reviewed independently.
Maybe they mean keeping a stack of CLs ready, while waiting for a review? I often had 1-2 CLs based on.. rebasing was fun sometimes.
Or they mean diffbasing these subsequent CLs, for an early review? That was useful, but due to volatility dependent on the first review, a bit risky.
Plug for a code review project: https://reviewpad.com/
Great to see this space moving! Any pointers on diff vs Kythe? Kythe has a mostly fixed schema, for one.
One of the pain points using Kythe is wiring up the indexer to the build system. Would Glean indexers be easier to wire up for the common cases?
Other is the index post-processing, which is not very scalable in the open source version (due to go-beam having rough Flunk support, for example).
Third, how does it link up references across compilation units? Is it heuristic, or relies on unique keys from indexers matching? Or across languages?
IANAL but EU reverse engineering exception is granted for purposes of interoperability as I remember? Think API, protocol, file format.
You can't reverse engineer and share random internals.
I would add great pacing, with long, slow shots. I counted random modern film scene switches, it is average 2 seconds per switch.
Other is adding atmospheric elements that serve no purpose to the plot, just paint scenes of life. In modern films, most things shown will have to compulsively have some utility later.
> Pull requests don't prevent bugs
Doesn't match my experience. There's two levels to this:
A good review can catch bugs directly. But even more important, it can dispute an obscure design, ask clarification for intent of ambiguous pieces of code, ask for added tests.
A hassle short term, but saves accumulated debt long term.
Express this dismay to them, in a honest open conversation. Discover what holds them back. Be open, don't scold, maybe they reveal a problem in your attitude as well.
Jerry Weinberg asserted that you need 5x the hourly rate as a consultant, due to overhead, to get even.
I really recommend Secrets of Consulting. I was vary since it sounds a BS title, but excellent book.
Clicking the first image link about the exhibition triggers some Android spam pop-up fyi.
Ideally yes, but most of the time I find I have no idea about what I want to do. Idea leads to code, code reveals constraints, those lead to other ideas. If we could specify things, code writing AI would be easy. But most of the time, we just have no idea.
I have great success using Zoekt, a Google codesearch reincarnation, for instant grepping.
There was discussion here a while ago, that effect is genetically affected as well. Some people have traits which makes them weak against asbestos, some go without problems.
I like how the subtle repetition of using the word "gain" programs the mind to associate to grain.
People who can pass the whiteboard interview might have a problem persisting on long, not very challenging grunt things. Migrating that database over a period of a year. Overhauling some bits of that terrible UI. If you are already employed, look for the opportunity of improving something terrible that no one finds sexy enough. The role will be appreciated.
Having done some chidokai, first thought on seeing the site is "wow, that's a poor stance". YMMV
I saw the following model work: offer a compilation of your best (or themed xyz..) articles for money. Add that you can mostly find these scattered on the site anyway. Very fair, and people would pay for getting an organized package vs clicking through random posts.