I have a legit laminar flow hood (airclean 600, 32 inch) in my home for plant tissue culture. I gotta say, I thought it was going to be easy street to sterile culture- it was not. Sterile protocol matters so much that I think it would have been just as easy to do what I needed to do in a glove box with all the extra precautions I had to take. It's honestly hard to beat an enclosed container with zero airflow.
Readit Newsscottcodie commented on Testing a cheaper laminar flow hood chillphysicsenjoyer.subst... · Posted by u/surprisetalk
scottcodie commented on "You Don't Need Kafka, Just Use Postgres" Considered Harmful morling.dev/blog/you-dont... · Posted by u/ingve
One thing the other blog post missed and this post misses too is that you don't need Kafka to use Debezium with Postgres. This gives you a pretty seamless onramp to event streaming tools as you scale.
scottcodie commented on Is Postgres read heavy or write heavy? crunchydata.com/blog/is-p... · Posted by u/soheilpro
I've spent my entire career developing databases (oracle, cassandra, my own database startup). Knowing if your workload is read or write heavy is one of the first questions when evaluating database choice, and is critical for tuning options. I would give this article hate just because it feels partially written by AI and the title needs a possessive 'your' in it, but its core ideas are sound and frame the issue correctly.
Stream processing/materialization engine written in rust that can be compiled to wasm.
Graffiti art.
Deleted Comment
scottcodie commented on Ask HN: I’m an FCC Commissioner proposing regulation of IoT security updates · Posted by u/SimingtonFCC
Is there a definition of a "security update"? Software has an infinite number of bugs and it is cost infeasible to fix them all. If it's years down the road, the engineers that wrote the code may be long gone.
scottcodie commented on The best approach I've seen for hiring junior engineers rubick.com/hiring-new-eng... · Posted by u/mooreds
I've always wondered why companies don't take a kind of staircase approach to compensation with younger engineers. E.g., if the salary is $1000/week with a 4 week staircase, then week 1 would be $250, week 2 would be $500, week 3 would be $750, and weeks 4 and onward would be at the usual salary.
If the primary cost of younger engineers comes from helping them get on board with how things are done at a given shop, this seems like it offsets the initial learning curve quite well. You could argue that the learning curve takes a lot longer, but surely there's an 80/20 rule at play here where the most important 80% can be learned in the first 20% of one's tenure at a company.
Paying poorly would bias you to candidates who will accept poor wages. Good candidates, even if they are young and inexperienced, can have a high market rate.
scottcodie commented on Payment systems while working at a pizza place nickjanetakis.com/blog/wh... · Posted by u/nickjj
> For example, if a pie costs $16.95 right now and you have 1,000 orders that happened in the past at that price and then bump your pie to $17.95 you can’t go back and adjust all of those previous orders to have $17.95.
> Just about everything about that receipt should be denormalized, AKA. the details about the receipt are all self contained in that 1 row.
The way I'd probably model this would be to mark the $16.95 pie as deleted/deprecated/no longer for sale and create a duplicate entry with the price changed to $17.95, rather than creating copies of all of the product details each time I record a sale.
You could also use a temporal table.
Deleted Comment