Sharing with HN: a starter app to understand Cloudflare Containers (introduced in June 2025 as beta)
The official docs were vague and examples pretty bare, so I made a inspector/debugger app to understand the reverse proxied container env that you cannot ssh to.
This could unlock cost effective Python services for you.
pro tip: if you're dwelling in apartments and can't spare a bedroom or closet, use a "grow tent" ($150-$250 on Amazon) to isolate your workspace from toddlers and spouses
- big enough for standing desks
- most noise isolation headphones will clean up your audio for meetings
- add whatever solid color backdrop or virtual backgrounds to clean up your video
- built-in air circulation to/from windows
Best part of reading this is coming away having learned the existence of units the CLI. How did I spend 20 years on the shell and not have needed or discovered this?
the Talk Python series is actually a great way for Python programmers to discover authors and libraries you wouldn't organically come across on HN or GitHub browsing. I highly recommend it to intermediate python programmers to expand their knowledge scope.
If you want to build the web with Python, IMO the emphasis should be bringing Python to the web. I think a more promising project is http://pypyjs.org/ - a Python runtime in your browser powered by asm.js
I want to also vote up Cactus despite the lack of attention paid to it lately. IMO it's very well designed and deserves to be worked on by a wider community.
I've gone down that path before of storing encrypted secrets in SimpleDB. Unfortunately, encrypting string values will bloat the length of your strings, bumping against the 1024 value limit of SimpleDB: http://docs.aws.amazon.com/AmazonSimpleDB/latest/DeveloperGu...
I agree with his sentiment. Working on side projects keeps this career interesting. During the most boring, most soul-sucking projects of my corporate jobs, being able to accomplish projects on the side reminded me of why I am excited to be building software in the first place.
Apple is rolling in cash from the 20+ Macs/iPhones/iPods I've personally owned or got from work over the years, I don't feel a tinge of guilt, I'm probably one of their best lifetime customers.
I've built Hackintoshes since 10.7, but I would never offer to build one for friends and family, only because I know I'll be called upon to fix the inevitable problem during software updates. This is a social obligation I rather avoid, lest I become the "IT guy" for yet another dependent.
My recommendation is - if you don't have the knowledge or patience to build one yourself, you should not ask one to be built for you, because it will break and you're gonna have an unproductive day/week while you wait for help to arrive. Not worth the headache and lost productivity.
Hackintoshing should be strictly treated as a hobby.
Same here, I run a spec that Apple simply won't sell me. The moment they sell me a computer that's user upgradable over time and allows me to choose the monitors (no glare, please) that fit my needs, I'll say TAKE MY MONEY!
My Hackintosh built in 2012 for less than $800, it has:
- Core i5 3.4 GHz (still competitive with Mac CPU specs sold in 2014 and into 2015)
- GeForce GT 640 with 2 x DVI + 1 x HDMI for a triple monitor setup (much better than anything in Mac Minis and some iMacs)
- 2 SSD drives for main OS
- 2 x 3TB magnetic drives (sync'ed to Amazon Glacier)
Note that two years after my initial build, faster CPU options and graphics cards can be swapped in with incremental upgrades as my requirements increase.
I'll post separately in this thread tomorrow about my recommendations and experience running this machine, but it's hands down the best Mac money can't buy, with room to grow.
I don't do it because I don't want to give Apple my money, I have to do it because Apple won't take my money.
-
P.S. IMO, Hackintosh only makes sense for desktops. While the various methods could get it to work for laptops, no manufacturer comes close to Apple's build quality. That trackpad is just amazing.
Sometimes it's not a good idea to give too much feedback, if any at all.
I used to automatically provide feedback of why a candidate did not pass the interview, then I had a few sour encounters where the candidate just did not react professionally. For example, one candidate bemoaned the emphasis on CS fundamentals in our interview. In that case, the candidate was coming in from a mostly front-end webdev background, but our tech stack extends far below the typical webdev "full stack", where knowledge of OS/Networking/Compiler fundamentals is helpful in everyday design decisions. As a small team, we bias towards generalists for now, so while the person might be a great fit for his skillset in another organization, it just wasn't a great fit for us at that time. I tried to explain this, but I received a wall of text complaint email back. I had taken an hour out of my day to write immediate and specific feedback about his interview, and all I got was pushback. This is probably why HR stands between engineers and candidates.