545 karma · joined August 11, 2017
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.
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.
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.
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.
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?
[1] https://www.machow.ski/posts/galls-law-and-prototype-driven-...
No wonder the most promising students drop out and go on to join finance or tech firms - the pay is an order of magnitude higher.
I recently launched a project for tracking crypto market data and suggesting trades. I went to Fiverr to see if I could get someone to design me a UI, and after going around one guy quoted me ~1.2k USD.
I decided that I could do it myself, and proceeded to spend multiple evenings working on it. I did learn something true, but it delayed the launch by weeks and if I factored my hourly rate in i probably "overpaid" several times over.
Getting past this "do it all" mentality is going to be one of my goals for the remainder of the year.
Also, don't worry too much about perfection. It's actually better to launch something before it is perfect, since the hard part is not actually doing the project, but getting anyone to care. Better to get That step out of the way as fast as possible.
For a second I though had been dosed with something hah.
1. Self publish, I.e. Host the blog yourself. There are many options but I personally go with Hugo/Netlify which uses git and markdown as my "backend" and has the upside of basically being free.
2. Use a publishing service such as Medium or Substack. This is easier, but you have less control over your content that you would self publishing.
Irrespective of this, getting people to read anything you write is the hardest part. You need to share your content, talk to people etc, it takes time.
These happy clappy "systems" usually fail to take into account (almost biological) realities of how power structures work.
1. Load a data file here
2. Tell me some facts about the data
3. Here's another dataset, can we use both to figure something out.
4. One of the executions for this order is missing, how can we find which one.
5. Here is a data feed, can you write a process to ingest the data and calculate something in real time.
I by far preferred this system to the alternative which was to ask trivia questions and see if the candidate memorised the docs. There is of course some value in asking basics, or to elaborate etc. But on the spot algo questions are usually only useful in filtering people who either like leetcode problems, or have grinded them for the last 6 months.
Not sure how it is where you are, but where I am the payment is automatically done every month from your bank account. There is 0 chance of missing a payment, as long as you have a sufficiently positive floating balance in your account. If someone do not, then I would question their suitability for a credit card in the first place.
However, what should be penalised heavily is blaring your horn in frustration or when stuck in traffic. This happens near where I live on a daily basis, and causes my blood to boil. It seems for these people it is almost instinctual, and they will do it at the slightest slowdown or inconvenience.
Not a big fan of enforcement actions, but this is incredibly anti social and provides zero/negative utility. A couple of weeks of police camping intersections and handing out liberal fines might perhaps encourage a change in behaviour.
Doing it from the bottom up solves this problem, however I think in a general sense (eg. with different sources of gravity it would become more tricky!