Viewing profile — ZephyrBlu
ZephyrBlu
HN member- Joined
- Sat, Jun 29, 2019, 8:49 AM UTC
- HN karma
- 7,766
- Public activity
- 2,357 items
- HN profile
- View on Hacker News ↗
About ZephyrBlu
No profile information was provided.
Recent public activity
-
comment
Comment #48292539
I completely agree with your distinction and that is exactly what they mandated :) I don't think that is what most people colloquially mean by "feature flags" though. Even most tea…
-
comment
Comment #48292231
In a company the size of Shopify people flipping their feature flags would very often impact *other teams*, and like I said feature flags got abused with even seemingly innocuous c…
-
comment
Comment #48292123
Feature flags need to be treated as short-lived and experimental otherwise they end up getting abused for everything and make it very difficult to reason about your application. If…
-
comment
Comment #48180655
No other provider works like Copilot did with "premium requests". Usage limits (Codex/Claude Code), which are inherently linked to tokens, are the most common. Some providers like …
-
comment
Comment #48176447
Why would you extrapolate from Microsoft's very poor setup to tokens in general then if you know it's stupid and not representative?
-
comment
Comment #48172909
The fact you are trying to use Copilot as an example here shows you don't understand how Copilot's previous billing worked. Previously they used "premium requests" which would allo…
-
comment
Comment #47850821
Scheduled maintenance in 2026 is insane
-
comment
Comment #47776868
No point in discussing with someone who is arguing in bad faith. I already agreed that some parts of the engineering process are safety critical. If you think there is no bullshit …
-
comment
Comment #47764226
People like to make this point, but traditional engineering has the opposite problem: insanely overwrought processes and box-checking that exists for no reason and slows everything…
-
comment
Comment #46532312
No it was the 3 co-founders, a part-time person and 4 engineers. Now they are 3 engineers down.
-
comment
Comment #46530475
He said he wanted to state it like that because he thought just saying "3 people" undersold the impact.
-
comment
Comment #46530386
On his morning walk/podcast thing about the topic he said 75% of the team = 3 developers
-
comment
Comment #46530042
Definitely more than 200k per head. I remember seeing a job posting for Tailwind Labs for a (design?) engineer which was 250-300k TC. Seems like it was an insanely profitable produ…
-
comment
Comment #45891446
Material and cut/design. Material is not just about quality, but rarity or uniqueness. For example, japanese denim can get very expensive in part because it's very low volume. For …
-
comment
Comment #45710355
Because it's not his job. He should elevate someone else into that IC role instead of holding it for himself. The way he describes it, there is no one else in the company who can d…
-
comment
Comment #45702245
I wouldn't really call it "demand". It's more like one-shotting humans with a product which maximally stimulates them through what is basically a psychological hack. We were not bu…
-
comment
Comment #45623608
The thing I'm most curious about from this article is how/why the author was demoted from E9 to E7. A demotion in itself is pretty unusual, but being bumped down 2 levels seems sup…
-
comment
Comment #45510405
I used both English and Hangul to search. Searching for general things like food was good, but if I was trying to find a specific address it was very difficult. Sometimes it would …
-
comment
Comment #45487275
They lack a lot of polish. Functionally they're mostly usable, but some interactions are janky and I found the search to be super hit or miss.
-
comment
Comment #45450586
Pretty crazy improvement, seems like he's putting his money where his mouth is
-
comment
Comment #45407690
On vibe coding being self-correcting, I would point to the growing number of companies mandating usage of AI and the quote "the market can stay irrational longer than you can stay …
-
comment
Comment #45406943
> No it isn't. There's literally nothing about the process that forces you to skip understanding. Any such skips are purely due to the lack of will on the developer's side This is …
-
comment
Comment #45139267
From the title and URL I thought the substack was "Big Tech Public Relations"
-
comment
Comment #45113747
__350x-ing__, not 35
-
comment
Comment #45064884
I tend to agree, which makes it all the more amusing that companies brag about being so selective. It seems like largely artificial and random selectivity.