HN user

corvus-cornix

91 karma

[ my public key: https://keybase.io/simoncrowe; my proof: https://keybase.io/simoncrowe/sigs/fs35BLyM0zVohVfck-0Fw62U2ABnPGLWq9Cfl66nFa0 ]

Posts6
Comments13
View on HN

Some of the formatting for emphasis and em-dashes looked a bit iffy. It's hard to imagine AI wasn't involved, at least an an editor or to discuss ideas. To be clear, I don't think there's necessarily anything wrong with this.

I'm looking at engineering job specs at the moment and it's very wearisome that every company seems to have pivoted from highlighting the unique value they provide to customers to putting AI front and centre in their employer branding. My eyes immediately glaze over at what may have been the result of "Claude, take this HR/marketing/whatever copy and inject some AI".

I've adopted the tools because they're useful, but businesses need to chill. AI seems to amplify existing bottlenecks within organisations, so we should probably tread carefully when it comes to pushing the tech. Fix the organisational problems first and hedge our bets.

I wonder if anyone reading this was around during the dot-com bubble because maybe it felt the same...

Goal: Setup a minimal working example where pods in GKE and EKS can access two buckets, one in S3 and another in GCS with no static credentials or runtime configuration. In other words, running the below commands should just work from within a pod in both clusters:

I only use notebooks when I need to analyze a csv and a python repl session would be cumbersome. For this limited use case I think they're fine.

They never mention the economist he collaborated with in inventing game theory: Oskar Morgenstern. There were also collaborators involved in developing "Von Neumann" architecture. He was just the biggest name involved. He was a genius, but there's some politics at work in who is remembered for collaborative intellectual work.

Learn FastAPI instead (for new projects where you don't want the template-based MVC). Django is showing its age and comes with some unpalatable design decisions, particularly in its active record ORM. Django's most useful feature is arguably automated DB migrations, but this can also be achieved with SQLAlchemy+Alembic