philihp

Joined 12 years ago

Karma
202
Submissions
112
Member since
Jul 16
[ my public key: https://keybase.io/philihp; my proof: https://keybase.io/philihp/sigs/q5NZV9hK8O5-UuSLkgVNbaNb_1GKI0-YrwJZnMaIuaE ] vjija3diliz32cm4ef4a0zjn
View on Hacker News

Recent submissions

Comment · 9 months ago
Can we settle for Factorio and 2028?
Comment · 1 year ago
Possible, yes, but pretty damming to Microsoft's reputation if proof that their infrastructure has been compromised and anyone realizes it's happening. This sort of thing killed Sourceforge when they started shipping adware bundled into installers of the programs they distributed.
Comment · 2 years ago
Not much can stop a lone bedbug carried in. What you're trying to do is prevent your mattress from becoming a nest.

The problem with DE is it's so inexpensive and effective, and that makes it difficult to sell as a product. I got a 2kg bag of it for $10, and it's enough to last decades.

Comment · 2 years ago
The way you've trivialized a database vendor swap makes me curious how often you do this.
Comment · 2 years ago
Alexander wept
Comment · 2 years ago
When you control the devices to which you're deploying to, there is little reason why you wouldn't deploy as often as you can. It helps a great deal in isolating bugs to keep your changesets small, and you can either do that by slowing down the product iterations (and getting poor feedback from each), or releasing more often. This is ubiquitous with web development.

Weekly releases (or slower) is appropriate when you rely on users to update their software or firmware. Most mobile app development does this.

Comment · 3 years ago
Comment · 3 years ago
I remember you remembering that when we celebrated 1500000000!
Comment · 3 years ago
Running actions triggered from a non-main branch does it for me, either on pushes to the branch, or 'workflow_dispatch'. You'll otherwise never get that level of fidelity to what happens in production.

Keep the logic in your YAML "dumb". Avoid variables and subroutines in the file, if you want to DRY something, create your own custom action. You can have unit tests on an action, you can't have unit tests on a GHA workflow.

Comment · 3 years ago
For a frontend developer who is younger than jQuery, starting a project following this advice would be a good opportunity to learn why we do the things we do like build steps, and remember how much development sucked before HMR.

I suspect the author hasn't actually done this on a project with more than one person, supporting 99% of browsers in the wild. I also suspect they didn't run their own code, because either my screen is not as tasty, or "onlick" is not an handler of div.

Comment · 3 years ago
I still have the music for egatrek in my head!
Comment · 3 years ago
Sounds like you have a bigger problem if your browser isn't properly sandboxed.
Comment · 3 years ago
The design of Quora is awful. It's like Yahoo Answers, but instead of an inane unqualified answer, you get a dubious answer surrounded and camouflaged by answers to sponsored questions you didn't ask.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton