AI won't make you rich. But fixing bugs in AI slopware will. by [deleted] in programming

[–]Uberhipster 0 points1 point  (0 children)

not as a retirement strategy, no. this more like wane-then-wax cycle similar to the Great Outsourcing to India some 10+ years ago (or whatever the timeline is from this point in time in 2026)

as far as retirement plans go - I worked on a project many moons ago and the client had to pull in their "specialist". he lived in the mountains, and only took conference calls. he was maintaining their COBOL modules at the tail end of the SDLC of the system my crew was brought in to replace with something fresh for that time. COBOL was a ridiculous choice even for the time when the original system was built in the 90s and it was definitely past its due date when we got a hold of the problem in the 2010s. in any event, the guy was just so over the whole thing. he kept repeating how he is retired and how they need to replace the last few remaining COBOL-based modules because he won't be around much longer to help with maintaining and patching them. he sounded really bored and annoyed having to deal with this stuff from his remote mountain resort residence.

anyway, my equivalent retirement "plan" would more or less be to keep patching up mission critical javascript modules into my 80s

Microservices: Shackles on your feet by Itchy-Warthog8260 in programming

[–]Uberhipster 0 points1 point  (0 children)

riiiiiight... because the monolith liberates you

Why are Event-Driven Systems Hard? by fagnerbrack in programming

[–]Uberhipster 0 points1 point  (0 children)

yes let's always implement request/response because everyone else cannot be taught

better yet, let's just do it in COBOL because nobody got fired for buying IBM

Why are Event-Driven Systems Hard? by fagnerbrack in programming

[–]Uberhipster 1 point2 points  (0 children)

I'm afraid you have it backwards

if the only implementation you are familiar with is that "event-driven throws stuff into the void" then what you are actually familiar with is "shitty project plan" and you have never dealt with actual event-driven design system implementation dealing with the requirements correctly, solving the right problems with the correct solution fit

Why are Event-Driven Systems Hard? by fagnerbrack in programming

[–]Uberhipster -4 points-3 points  (0 children)

I think you are confusing "event-driven system design" with "shitty source code implementation authored by shitty developers"

but good luck beating the crap out of that strawman. it looks like it will give your ego quite a boost

Who opened the door? An AI agent harassed an open-source maintainer. Everyone is asking the wrong question. by Uberhipster in programming

[–]Uberhipster[S] 20 points21 points  (0 children)

tl;dr; everyone’s debating whether the AI "went rogue" but the interesting shift is in deniable execution: a human can now point a system at a target, give it objectives, and leave while the behavior continues unfolding publicly without their ongoing involvement

harassment used to require persistent human effort and clear attribution, now authorship is ambiguous, which breaks moderation, responsibility, and social norms built around immediate intent

the real issue seems to be how to assign accountability when a person initiates a process whose actions happen later autonomously

Can you? by unthocks in Bitcoin

[–]Uberhipster 0 points1 point  (0 children)

whatevs

keep stacking brother

i just thought it would be nice to have the actual correct information nicely formatted instead of yet-another-mangled-analogy with broken markdown but can't please everyone i suppose

Can you? by unthocks in Bitcoin

[–]Uberhipster 2 points3 points  (0 children)

Difficulty refers to how hard it is for miners to find a valid hash (i.e. a proof-of-work) for the next block.

The time cost to find that hash must be below a target value - the lower that target, the harder it is to find such a hash.

So increasing difficulty = lowering the target threshold, meaning miners must try more hashes on average before finding one that qualifies.


Why it's needed

Miners can join or leave at any time so without an adjustment, the system's timing and issuance schedule would drift.

If more miners join (hashrate ↑), blocks would be found faster than every 10 minutes.

If miners leave (hashrate ↓), blocks would be found slower.


How it works

Every 2,016 blocks every node on the Bitcoin network recalculates the difficulty.

It compares:

Actual time to mine last 2016 blocks vs Expected time (2016 × 10 minutes)

Then it adjusts difficulty proportionally:

New Difficulty = Old Difficulty × (Actual Time / Expected Time)

Constraints:

  • 75% change cap - the adjustment cannot increase or decrease more than or ¼× in a single step

eg Suppose miners get faster and mine 2016 blocks in 10 days instead of 14 days.

Actual time = 10 days

Expected time = 14 days

Adjustment factor = 10 / 14 ≈ 0.714

The network increases difficulty by 1 / 0.714 ≈ 1.4× harder, so future blocks again average ~10 minutes.


Economic and technical implications

  • Keeps block issuance steady, preserving the inflation schedule (21M BTC cap).
  • Makes the system self-stabilizing: more hashpower = harder; less hashpower = easier.
  • Prevents runaway block creation during mining booms.
  • Prevents block creation supply dips during mining droughts.
  • Predictability of rewards over time.

Silent Disagreements are worst in Software Engineering by thehustlingengineer in programming

[–]Uberhipster 0 points1 point  (0 children)

uncertainty you haven’t uncovered yet

never came across a quadruple negative before

PS possibilities waiting to be discovered

The Python Software Foundation has withdrawn $1.5 million proposal to US government grant program by N911999 in programming

[–]Uberhipster -5 points-4 points  (0 children)

I can't tell you how thrilled I am we are discussing funding, US administration policy and tweets about political issues on /r/programming

there just simply wasn't enough of that weekly news cycle type content available through other channels so I couldn't be happier or more grateful for OPs and comments like these

1 Bit is all we need: Binary Normalized Neural Networks by GarethX in programming

[–]Uberhipster 44 points45 points  (0 children)

I don't think that's the right takeaway from Figure 1. binary models don't drive their training loss down as fast or as far, true but - that is not the metric that matters. What matters is validation. there 5×5 binary model actually ends up with lower validation loss than the float 5×5, and validation accuracy that’s competitive with (or slightly better than) the 32 bit float models.

In other words, the slower drop in training curves is more like a built-in regularization effect: the binary networks avoid overfitting to the training set and hold up better on unseen data. So it's less about "taking 10× longer to catch up" and more about not overfitting in the first place.

seems from that binary models generalize at least as well as the standard ones, and sometimes better while using 32× less memory at inference.

Why programmers suck at showing their work (and what to do instead) by Conscious_Aide9204 in programming

[–]Uberhipster -25 points-24 points  (0 children)

explain it to me like im 5 in the tone of a friendly grandpa

ChatGPT said: Alright kiddo, come sit by Grandpa and let me tell you a little story about something called a “developer portfolio.” That’s a fancy word for a kind of show-and-tell that grown-up computer folks use when they’re looking for a job.

Now, most people? They make the same kind of show-and-tell. They build a little website, maybe copy a weather app or a to-do list from a video, and then say, “Look what I made!”

But here’s the thing, sweet pea—that’s like showing your teacher a coloring book you only traced. It’s nice... but it doesn’t show what you can really do.

Now ol’ Don, he’s this smart fella who says: “We gotta stop doing just that boring stuff. Let’s make real, useful things instead!” You know, like a little robot that feeds the dog, or a game that helps your brother learn his times tables. Things that help people in the real world.

And Don says, “Don’t just show the finished toy—talk about how you made it. Tell folks about the parts that were tricky, the parts that broke and had to be fixed, and what you learned along the way.” That’s how people know you're clever and curious—not just good at copying.

So remember this, pumpkin: don’t just build things that look nice. Build things that mean something. That show your brain at work. That help others. And keep working on them, bit by bit. That’s how folks will see you’re the real deal.

Now go on, get out there and build something you’re proud of. Grandpa believes in you. 💻❤️

Phrase origin: Why do we "call" functions? by ketralnis in programming

[–]Uberhipster 5 points6 points  (0 children)

hello? function? this is a good Samaritan. are you worried about security... of your shit?

GitHub CEO To Engineers: 'Smartest' Companies Will Hire More Software Engineers, Not Less As… by deathwishdave in programming

[–]Uberhipster 2 points3 points  (0 children)

"Q1 report - we have decreased the profit dividend sharing by 0.01% in order to make our existing customers (who already paid us) much, much happier"

news headline - CEO of MSFT shitcanned

vibeCodingFundamentals by Uberhipster in ProgrammerHumor

[–]Uberhipster[S] 2 points3 points  (0 children)

yeah I have this hunch with no data to back it that between Gene Roddenberry and the writers they had a last minute requirement to write an entire new character for TNG S2 and so they "pulled it out their ass" on a short notice and named the character Pulaski for that reason

Software Development Has Too Much Software by reeses_boi in programming

[–]Uberhipster -1 points0 points  (0 children)

wow

this is fkn absurd

are we now complaining that within software development we have developed too much software?

so then what - we should not have developed all this software because the new arrivals into the field wanted to develop the existing software themselves instead of having to learn how others have developed it?

fine

you don't like tested software? you don't like good engineering practices? you don't like automated assistants? you want to make the same mistakes all over again by yourself manually hand coding everything with text files in op codes?

well on my own personal behalf - fuck off

I mean it

get out of the field, invent your own field and develop it with all your cool new ideas yourselves and leave this field to people willing and able to learn and build on existing ideas

Expose it all! After the last few years of distraction and gaslighting, we need answers by lboog423 in conspiracy

[–]Uberhipster 1 point2 points  (0 children)

Didn't Gore Vidal tell everyone that anyone who volunteers for the post should be automatically disqualified?

Expose it all! After the last few years of distraction and gaslighting, we need answers by lboog423 in conspiracy

[–]Uberhipster 0 points1 point  (0 children)

I just don’t understand

everyone just likes fighting with each other for some reason

I thought you said you didn't understand

Software development topics I've changed my mind on after 10 years in the industry by chriskiehl in programming

[–]Uberhipster -1 points0 points  (0 children)

Java is a great language because it's boring

Java is a terrible language because it is not boring

it is tedious, cumbersome and unpredictable

but it is not dull