HN user

lazystar

899 karma

tech industry since Q1 2018

Posts1
Comments391
View on HN

from OP:

setting off commercial grade fireworks bursting hundreds of feet in the air. The house was shaking,

I'm in Bellevue, WA, and experienced house-shaking fireworks for the first time this year. I was inside with my cats - theyve always been more or less fine with fireworks, just hiding under the bed - but this year's house shakers were on another level. When the first one went off, I thought an accident had happened and a cache of fireworks had exploded. Scared the hell outta me. Then there were about 5 more like that spread across the next 5 hours. 0% of pets would be ok with these ones, I guarantee it. Idk if theyre new this year or what but Ill be doing the same as OP next year.

the biggest issue with reddit/digg/hackernews style comments is how top comments can be gamed for profit. old forums had the problem of "first" and "bump" comments, but steering the conversation was harder.

ELIF: You trick the CPU to display screen data at a different starting point than as designed by the hardware. This is tricky and need to be executed cycle exact.

heh, is there a new meaning for ELIF? im not sure that there are many 5 year olds who would understand that ;-)

well... just because you know how to ssh into the prod DNS host and manually update the prod zone files in vim to remove orphan A records + duplicate CNAME records, in order to fix an ip address exhaustion issue that is blocking new VM's from spinning up for your customers... it doesnt mean that you should, lol.

that was 8 years ago in my first gig. now i kinda wonder... having those skills made it easier to put off implementing a robust long term solution. it was playing with fire, sure, but i was a rookie

Because if you tell me directly that you have asked Claude, next time I will probably ask Claude directly as I don’t need you.

and what if i tell you i asked stack overflow?

well, once they do, kohberger and who knows how many others will be let loose on the public. sets up a hell of a bargaining chip for the feds to prevent it going to the supreme court.

also makes you wonder if any of this would happen if the usage and post trial application of the death penalty were higher. less of a bargaining chip.

the counterpoint is that allowing unlimited discourse places an enourmous amount pf power in the hands of the chatbot owner, who has access to all logs and input from each user. this prevents one chatbot owner from advertising "you can say anything here!!" then using the logs as blackmail down the road.

aye, fair assessment.

funny story, figured out the root cause behind 3 years of brain fog just a few hours after i left this comment. it wasnt long covid; turns out my eyes were so swollen from screentime, that they were cutting off blood flow to my prefrontal cortex. started using a portable eye massage device, and poof - back to normal. just have to clean up the mistakes i made while i was sleep deprived and caveman like.

aye, totally correct.

funny story, figured out the root cause behind 3 years of brain fog just a few hours after i left this comment. it wasnt long covid; turns out my eyes were so swollen from screentime, that they were cutting off blood flow to my prefrontal cortex. started using a portable eye massage device, and poof - back to normal. just have to clean up the mistakes i made while i was sleep deprived and caveman like.

my team is anti-AI. my code review requests are ignored, or are treated more strictly than others. it feels coordinated - i will have to push back the launch date of my project as a result.

another teammate added a length check to an input field, and his request was merged near instantly, even though it had zero unit testing. this team is incredibly cooked in the long term, i just need to ensure that i survive the short term somehow.

Or, do you tell it the basic functionality you want, test it out, then add feature after feature that you want, sometimes dropping them and sometimes adding new ones that you thought of as your worked

the problem with this is long term maintainability. it works - and the engineer understands how it works - but a) the AI does not prioritize cleanup/organization/naming, and b) there's a blind spot/boiling frog type of phenomenon that can prevent the engineer from spotting the growing problem. the codebase becomes recognizable only to them. the engineer sees all features working, all bugs fixed, 90% test coverage, and submits it for a PR.

the engineer tasked with reviewing the PR will treat it as slop.

i think theres a paradox here. intelligence needs a judge - if nothing verifies that the optimal outcome was chosen, it's too easy for the intelligence to fall into biased decisions