Not a founder, but a serial side-project'er. Initial prototype typically has no tests, at least for the bits that are wired. Specific bits of complexity will have unit tests. At some stage might add integration tests using something like docker compose.
Use TDD for bits that have very limited scope and function. For instance, an order book class or similar. Otherwise code first, test bugs if needed. For smaller projects (that aren't critical espc.) overtesting can kill your momentum and motivation, which is an often overlooked resource.
Indeed, I've always thought there is a veritable bounty of great SciFi stories to put into film. The recent popularity of SciFi shows suggests to me that we will start to see more works transferred to the big (or small) screen, though as always this seems to be a very hit or miss process.
Personally, I'd love to see e.g. The Culture novels be made into a show, or series of films. There was talk of making a Consider Phlebas TV show some time back, though I don't think it went anywhere. Heinlein's "The Moon Is A Harsh Mistress" could also do well as a stand alone movie, though possibly with Heinlein you would need to tone down the polygamy themes.
As to why PKD became such a cinematic mainstay I can't quite tell. I would think part of it would be to do with the fact that many of his stories were less about the "lasers and spaceships" part of SciFi, and more about the moral and human aspect, meaning costs could be saved on big budget set pieces ala Star Wars.
Sony XM4 headphones. They are pricey, but a fantastic bit of kit. The noise canceling is not perfect but good enough that sometimes I will just wear them while walking around even if not listening to anything. I like how they "dull everything out" giving you room to think.
Maybe this is a bit off topic, but does anyone know the legal footing of having a business with another businesses name in it? For instance, this tool uses the word "YouTube" in its name, though it is used as only a part of it, and it is not a competitor. I've always wondered how this works.
Many years ago I took (oddly) a physics class called (iirc) "Self Organisation" while doing a year abroad in Germany. Despite being a quite small class, it really inspired me from the perspective of self organizing systems.
I find structures like conways game of life, or slime mold or sand dunes to be fascinating for this reason. That from unit simplicity can emerge aggregate complexity, imitating facets of nature.
Two item that always come with me in my day bag along with my laptop are a simple A5 notebook, and a pen.
In my case any design be it software, a drawing, or project or something else needs to start with a couple of rough diagrams and notes on paper. I have tried numerous times to do this electronically and it has failed every single time.
Not sure why, but there seems to be something about the fluidity of writing that allows you to get thoughts and expressions down quickly in a way that boxes and flowcharts just don't facilitate.
Most of the time I view these notes for a few days while I work or write proper documentation and after that they are left behind. I have several stacks of various notebooks lying around filled with stuff like this.
Indeed, but once you start getting to that point I'd argue you are starting to get beyond a prototype. But you raise a good point, id say if the intention is to throw the code away (which you probably should) then if add as few tests as will allow you to make progress.
I've always favored exploration before implementation [1]. For me TDD has immense benefit when adding something well defined, or when fixing bugs. When it comes to building something from scratch i found it to get in the way of the iterative design process.
I would however be more amenable to e.g. Prototyping first, and then using that as a guide for TDD. Not sure if there is a name for that approach though. "spike" maybe?
One thing I really like about kdb+/q is the fact that it has strict right-to-left execution/precedence. While I know it's a standard, I don't want to deal with bodmas, or whatever it is. Having right to left makes it clear and unambiguous how it will execute. Saying that, it does also encourage huge one line abominations. Everything in moderation i guess...
This is a good point. I have been wondering how does one do SEO for such online tools? If you only have the tool present, it will be definition not have much text content which Google uses to gain context for the site.
I made it to try and learn d3 and typescript in general. I posted it as a "Show HN" but it got no clicks so I sort of just let it sit there. To be honest, when I saw how good most online drawing tools were, and how basic and amateur level my tool was I got demotivated and decided to leave it as is.