HN user

wuster

325 karma
Posts10
Comments128
View on HN

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

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.

It's open sourced via BSD 3 clause: https://github.com/koenbok/cactus

I especially liked the "deploy to s3" feature, IMO the cheapest way to run a highly scalable static site today.

Alternatively, a "deploy to GitHub page" would be neat as well.

I would work on extending Cactus if it was a bigger problem personally, but so far what's released fits my needs already.

Side projects 11 years ago

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.

I choose who I work for by these attributes:

1) does the company provide a product or service that makes a world a better place? (e.g. Nest, Tesla would qualify)

2) are my potential colleagues great people that I will enjoy spending time with and learning from? (it's miserable to work for miserable people)

3) will the company pay me a market wage such that I can provide for myself and my family

I entered college in Fall 2001 and enrolled in my university's CS program in Spring 2003. While in high school, I witnessed the high flying late 90s dot-com boom from the sidelines, at times wondering if I should drop out of high school or skip college to join in on the good times. Then the dot-com crash and 9/11 happened and the country went into a recession. I had friends telling me I should not major in computer science, and that most jobs are being outsourced away. To be honest, the truth on the ground did not invalidate that opinion at the time. Internships were hard to come by, you either submitted your resume into the dark pits of corporate job portals, or you emailed your resume to small local companies no one has ever heard of. Even in a top tier university at the time (Univ. of Washington), many classmates of mine were happy to get interviews with IT departments of companies whose core business is not computer-driven, e.g. logistics or healthcare companies. Not every CS major lined up a lucrative summer internship then, and some had to graduate with minimal to no work experience, throwing them into the catch-22 of no-experience = no-hire. Must've been frustrating for many. The first sign of life came with the success of "web 2.0" sites like Flickr and Google Maps 1.0, and "modern" developer tools like Ruby on Rails & jQuery. What felt like grunt work just a few years before had turned into more of a joy. Within 2005-2007, I noticed increased enthusiasm from the web community to re-build old ideas with modern user experiences, and the web became exciting again. Then in 2007 the iPhone happened, which led to enthusiasm for mobile-optimized sites, followed by the native iOS craze of late 2008/2009. After that, YC and some of its early companies got recognized in mainstream press, Google succeeded with Android, and open source got real exciting with the emergence of Git & GitHub. From that point on, it was just a dizzying pace of change in web and data technologies.

Ex-Googler here. Working at Google is very different than making a presentation representing your own idea. At a big company, assuming a collaborative culture, your teammates are rooting for you to do well and you don't go into a meeting expecting that to be the last word if they don't like your idea. OP had already quit his job, staked his reputation/ego on his demo, and had to speak for himself in a tough room, so I think it's reasonable to feel some level of nervousness.

UI is very nicely done, but to echo some other sentiments here, I'm not sure it's $10 better than Adium. At $5, I'd just buy it to support great OS X developers, as I want to encourage this type of effort.

Great concept, thanks for sharing. This is a valid alternative to getting a cloud machine (e.g. EC2) and providing a reverse proxy from your localhost to an open port on the cloud machine.

Once upon a time, I had sent an email to an org with criticism of their web site and how it's hurting their image, only to find out that they gave the web dev opportunity to a high school kid in the area who really wanted the experience. The org was completely legit, and IMO they did a good thing by giving some kid a chance. If the org's product is not the web site, then I don't see why they should waste money/time on an amazing designer/developer when that money could ease operational needs elsewhere.