fake knowledge era

java spring library is battle tested with lots of features, how hard could it be to find a way to do a feature flag?

too bad im retarded so it's hard to sift through the documentation

i miss when there was a togglz already set up (if im even remembering correctly)

SHARK DENTIST https://youtu.be/p4U9Gc6hknM/...

My god, I look at Suno as a whole product, besides some serious perfect AI performance, that UI. I never worked on something that smooth / advanced. But times changed a bit / also worked on different kind of software. When I worked on such stuff it must always show the totals at the bottom and everything was in columns and should be all sortable. Now, nothing sortable and there are not totals anywhere. What is way easier on performance and stuff. Actually, in options the new software downgraded in many ways, but it looks so slick and is just more intuitive. What is the point of showing the totals and stuff in the bottom and having every column sortable (what was a big issue on some columns). Everything had to be live, now it's quite common to generate a report and wait a bit or so.

But i'm really surprised by the GUI. I know how to do it while I never did, but i was just never asked. Different times I guess. Beautiful was never a requirement to stuff I made in fintech..

It seems that AI is not the only thing advancing, I see a lot of stuff.

Imagine how smooth it would be if everyone just used web components instead of React. Urghx. I swear, native web components are less complexity. And yeah, doing that for over a decade. Some people call it modern. Haha.

Do any of you here have a relation to Firefox?

I posted a rant like 9 months ago about a VERY small specific bug in Firefox.

And since the last update, it's fixed lol.

The bug was:

When in Firefox and pressing WIN + F11, Firefox went into full-screen mode (probably just checked F11 without the WIN modifier).

Now it does not lol. Well, win for me, win for Firefox, and feels great.

(I have a custom global shortcut for WIN + F11.)

I'm working on a project, and we ran into a problem where the server memory was getting used up way faster than before. At first, everything was fine because the server was restarting during releases, which cleared the memory. But over time, the situation got worse, and now it only runs for a few hours before crashing.
What can be done in this situation?

100 new lines of code. 6 of them are new, the rest are tests. 30 comments and 100 commits later, changed code still not getting touched by tests. Who tests mocks?

Fuck my life, it's storming and something in the building is resonating after each gust of wind. Constantly tuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuut

fucking tinnitus simulator

Do you prefer local environments or cloud environments?

I think the major downside of having your important functionality in public cloud (usually not the case, but) is that when a major part of the cloud goes down (say, the previous Amazon issue), your services no longer (properly) work.
Of course, there's private cloud, hybrid cloud...
Pros and cons.

I've enrolled in a language class of a niche language. We had to do our first homework and there is a grandma that wrote her test via Gemini.

What is the purpose of paying for a language class if you don't do the effort to actually learn the language yourself lmao

Wow, just found out music generation trough Suno through as Snek member (thanks new friend!).

It's amazing. First, I did want to amaze a friend and did something I doubted if it was a good idea but I extracted 15 years of his reddit history and gave Gemini the huge jsonl file and let it generate two songs about the positive aspects of his life. The songs were gorgeous. While the background music was very familiar of one of the songs, they were due the high amount of content specified to him very unique.

Success. Friend liked as well.

Then, in the end of the evening I had some frustrations just because of life in general. So, i started to write a document with some struggles over the last seven years. They're all connected but I was never really able to put it under words. I asked Grok (the most humane LLM) to connect the dots and write a song with those lyrics. I implemented them into Suno. Created several aggressive rap versions, and then some euro dance / hands up versions (groove coverage style) with kinda vibes my personality. Both actually do weirdly enough.

Suno gave me credits for 500 songs for around 10 euro, I understand why 500, because I already made 20 variations! I almost LOVE them all.

I just realize how hard other industries are hit, or will be hit, as hard as ours.

While I really hated the vibe coder without knowledge, I am now doing exactly the same with music and have so much fun. And as vibe coder who really likes his creations because he can't do it himself and has some lack of knowledge, me like this music too with probably the same reason; lack of knowledge, inventing something 'new'.

It's btw not allowed to prompt into the `style` box "Eminem" or something. So I used Grok to describe concise (since the style box only allows 1000 chars) the artist with the right style i wanted to have. Learned more about the genres I listened to.

So, I found some piece with the unknowledgeable (why i this not a valid word?) vibe coders and wish them all their happiness with their fabrications.

A vibe coder will maybe never be a programmer, I will never be a producer. But that does not mean we can't make some awesome stuff.

I think everyone has a kinda life story and it could be nice for yourself to make a song about it to process something, turn it into something beautiful.

* enlightened, 5:26 AM, time for sleepii attempt again *

10 Things I Wish I Knew as a Junior Developer

After a few years in tech, I’ve realized that most growth doesn’t come from new frameworks — it comes from mindset shifts. If you’re just starting out, here’s some advice I wish someone had drilled into me early:

You’re not competing with anyone but your past self.
Forget comparing your code to that genius on your team who breathes JavaScript. You’ll get there — and faster if you focus on consistent growth over ego.

Google is your best mentor.
Asking questions is fine, but make them good questions. Try solving things first. Seniors love helping, but they respect those who’ve clearly done their homework.

Readable > Clever.
Fancy one-liners might make you feel smart, but clear variable names and simple logic make you a great teammate. Code is for humans first, machines second.

Reviews aren’t attacks.
A pull request comment isn’t criticism — it’s collaboration. Listen, learn, and keep the good discussions going both ways.

Never fake knowing something.
“I’ll check and get back to you” will earn you way more respect than pretending you know the answer. Engineering thrives on honesty.

Think before you type.
Rushing code just to “finish it fast” often leads to rework. Taking time to plan saves you more time later than you’d imagine.

Document like someone will use it tomorrow.
Because someone will — maybe you. Nothing feels worse than debugging your own undocumented code months later.

Soft skills aren’t optional.
People remember how you made them feel, not how you formatted your code. Be kind, patient, and reliable. Those qualities get you rehired.

Run toward the scary stuff.
That weird legacy code? The new API nobody wants to touch? Take it on. Growth hides in discomfort.

Keep learning, even when your job doesn’t require it.
Your company won’t future-proof you — you have to do that yourself. Read, build side projects, and stay curious.

At the end of the day, being a great developer isn’t about knowing everything — it’s about always being willing to learn.

apparently "cure for depression" posts are all clips of animals or babies that literally don't know any better that any trust they extend to someone will get them slapped and abused for dumb useless shit and any help they extend to someone will get them manipulated and exploited for their good graces

Aaahz the subtlety of AI induced bugs. Them fucks are so great at lipsticking bad code I'd end up fucking it before giving it a good look. Not now, thou, not now. My brain has figure out a workaround by telling me when shit is bad. My left eye starts twitching and I know, I KNOW that shit's bad

https://youtube.com/watch/...

The more you know.

I knew about Hertz, but not about speed repetition causing a sinewave.

What a disastrous deployment: instead of deploying one thing, 50.000 unexpected other things had to be done before. When the "official" deployment was done inside our own network, nothing worked as expected, servers had to be reconfigured, errors everywhere. Mind you it was tested multiple times by multiple people in a testing env. Difference between test and prod, classic.
When it was finally deployed, other errors started emerging, things that weren't considered before came to surface.
On top only the main dev knows the ins-and-outs, no substitute in case anything happens.
Deployment was rolled back in the end.

Regarding coding style, would you rather prefer:

1) Mutating state
This one sounds intuitive and performant because you are working with only one memory segment in place. I think that if you are skilled enough to efficiently modify the state without bugs, then everything should be efficient and powerful.

2) Copying state and modifying the copy
This one seems counter-intuitive to me because it sounds like you are doubling the resources it takes to perform the operation

Funny enough - at least for React, Python and my experience at work - it seems approach 2 is gaining popularity. Does this also apply to C? I would think not. Hm.

everything suuuuuucks, faaaawk

My new place to visit while my Github actions is doing its thing:

https://pointerpointer.com/

TFW you think stating your intent and what you want will get you discriminated against for funsies so they can pull you around and make sure you never get what you want