qxmat

I briefly worked at Games Workshop when the employee share save price was ~340p. Sadly they didn't pay enough for me to afford to buy shares on top of my rent, so I had to leave. Crazy to think they're all multi-millionaires now.

Europe is crying out for sovereign clouds. If this is to be a viable alt cloud, US jurisdiction is a no.

Not sure we can move away from cpu/memory/io budgeting towards total metal saturation because code isn't what it used to be because no one handles malloc failure any more, we just crash OOM

A fellow super brain finalist on hn?

Jira's now discontinued server version had a sequence table to stop you sharding it. It also made disaster recovery from a hard shutdown awful. I have nothing good to say about Atlassian.

Their Windows sensor has made development almost unworkable. Not sure why but I haven't noticed the OSX sensor slow things down appreciably. I suspect my Windows profile is configured to be more aggressive?

Knight Capital!

6 days is pretty reasonable to me because I'm an avid supporter of the release train (miss the release train, wait for the next one).

Governance is an important aspect of the software development cycle past the PoC stage. Releases shouldn't lead to an existential crisis.

This is something I've been unable to articulate as succinctly as you have - thanks.

In the past I put it down my experienced approach and what I need from others: make it work (mediocre solutions that deliver 80% value are fine!), then make it better (reflect and refactor until readable/approachable/idiomatic) before finally (stretch goal) make it faster (break idiomatic paradigms, vectorize etc.)

Python has a few weird issues like this. The last one I encountered was with a class inheriting Thread, join and the SQL Server ODBC driver on Linux. Fairly sure I hit page faults thanks to a shallow copy on driver allocated string data but didn't have the time to investigate like the hero of this blog post.

This appears to be the domain of Dagster + dbt, with which you get data lineage, not just composition.

Modern frameworks rely on components and the shadow DOM. If you understand how these are implemented you'll go far.

One of the trickier things to grasp is where your CSS begins and ends. CSS is quite leaky here but there are ample style guides that illustrate pitfalls.

I also found the C#/F# courses very well made. Specifically those by Mark Seemann, Kate Gregory and K Scott Allen... who I just found out died 2 years ago :(

Slow hash function + salt would solve this.. e.g. you'd be lucky to do more than 10 hashes a minute with bcrypt and 20 salt rounds.

I did the same a while back.

I used ANTLR4 to generate a .NET tree walker that would build up an IQueryProvider expression. IQueryProvider would then compile to Expression<T> and self-optimise (simplifying boolean algebra and removing redundant expressions). We hooked this up to npgsql and viola - a sane, typesafe, query string DSL without a single line of SQL.

Nowadays I hack together Terraform and Python ML- I miss .NET dearly... it was a simpler time.