Running all migrations before every tests can take you a surprisingly long way.
Once that gets a bit too slow, running migrations once before every suite and then deleting all data before each test works really well. It's pretty easy to make the deleting dynamic by querying the names of all tables and constructing one statement to clear the data, which avoids referential integrity issues. Surprisingly, `TRUNCATE` is measurably slower than `DELETE FROM`.
Another nice touch is that turning off `fsync` in postgres makes it noticeably faster, while maintaining all transactional semantics.
There are a bunch of these four-wheel bikes (https://vokbikes.com/) rolling around where I live. They're meant for commercial use and are slow enough for sidewalks and they do have a roof covering the rider. Cost more than $2000 though.
> I am fairly convinced that most modern DBs have almost zero impact from relationship constraints
It cannot fundamentally be zero impact, the database needs to guarantee that the referred record actually exists at the time the transaction commits. Postgres takes a lock on all referenced foreign keys when inserting/updating rows, this is definitely not completely free.
Found this out when a plain insert statement caused a transaction deadlock under production load, fun times.
As a start you can just go to Thingiverse to search for a model that fills your need and send it to the printer. That would take you all of a couple of minutes. Per try, until it comes out ok.
If you want to try your hand at 3d modelling then you'll probably download Sketchup as a start and noodle around while watching youtube tutorials on the side. In about 8h you'll feel confident enough to actually model something meaningful. After ~40h you'll be able to knock together a model quite proficiently.
After you'll have gotten tired of Skethub producing broken STLs and not allowing you to change your mind after modelling a thing, you'd move on to one of the real CAD software package, like Solidworks or Fusion 360 (which is great for beginners, btw). That rabbithole goes exactly as deep as you've got time for :)
Fiddling with the printing itself will take a bit of setup time before each print and then a lengthy wait (hours to days) to get the result, or see it fail in some new and unfunny way. It's not really all that difficult, to be honest, just takes some time to develop an intuition about what's likely to fail.
The described system is absolutely great for selling your vote, as you can prove within 30 minutes of voting who you voted for. It also allows you to change your mind an unlimited number of times until the voting deadline.
It is a very inconvenient system for buying votes though, as the voters can pick up your money and then go vote for whoever they wanted to in the first place.
How would you pull money from an account by knowing just the IBAN? That's just the public address of your bank account and can be used to give you money, but you need all kinds of authentication to actually get money out of that account.
Chrome dev tools make testing RESTful backends with curl very easy: right-click on a request in network panel and choose "Copy as curl". Priceless little gem.
Also, the speaker looks pretty much like Jabra Speak 410. And the camera looks like a Logitech fullhd webcam without Logitech logos. Which are all admittedly excellent products for doing video meetings.
The "interpretation of computer programs" part is nice to know, in my opinion. But the book gives a whirlwind tour of a sizeable chunk of computer science on the way, and the examples are concise to the point of being beautiful. Great book. Used it to learn clojure along the way.
In my opinion these examples are mere annoyances compared to the evil of the skype plugin. It actively monitors and modifies all of your browsing so it can inject those green skype "call" buttons in unexpected places. Now that I call evil.