@retoor althougt the idea is sound in moderation, there is such a thing as over-partitioning.
Imagine you had to cook 50Kg of raw rice.
This is too much for a single cooking pot. So you divide the load into smaller deliverables.
Great. Unless you budget for 50 thousand pots, each to cook a single grain. The overhead of setting each one up and joining the final product will take longer than it took to plant and grow the rice.
That is the sort of over-reduction of deliverables that I'm dealing with.
Bloody buzzword-only management.

And so the WSL was born

I've worked in the food service industry, and you'll just get yelled at by insufferable customers at unreasonable hours for a pittance of pay.
I've worked in what is probably the most structured of all industries - the Navy. They tell you when to sleep, what to wear, what to eat, what to do in extremely specific details, and even what to say when someone talks to you. Oh, and how to accept the blame when something makes your officer/boss look bad. If deadly office politics and intended lack of autonomy is something that annoys you...
I've spent some time in academia, and it is pedantic even when trying to be practical. It is like moving to a big city after living your whole life in small communities. Your skills are useless unless properly presented and within some seemingly arbitrary confines. And gatekeepers reign unchecked. But time is abundant.
And I've been in the industry for a decade. DevRant has a lot to say about it.

Tl;DR The grass ain't all that green on those other sides.

If the thinking that a degree will automatically and undoubtedly push you into a job, that is a mistake.
A major or minor uni degree is, like, step 4 out of 8 in the ci/cd of a good job. You can't skip it, but this stage succeeding doesn't implies that the further stages will succeed.
However, failing to obtan an uni degree does means that further stages are toast.

@Lensflare I had never seen the ternary operator called "the Elvis operator". But now I can't unsee it.
Although kids nowadays will most likely call it by the name of some Bollywood bloke.

@Wisecrack the walrus operator - a twisted thing from the depths of a twisted mind.
Behold!
(Look for the " := " that someone thinks looks like the face of a walrus laying on its side)

```
def square(val):
return val**2

odd_squares = [
sqr
for val in range(10)
if (sqr := square(val)) % 2 != 0
]
```

Try betting on emerging markets. Argentinian treasury bonds are USD denominated and have stupidly high yields (about 9.4%). Also quite high chance of default (like 6% high), but roulette will pay you 35:1 on a 1/37 chance of winning, netting a sucker's expected outcome. Thus you get better odds on the LATAM casino.

COMPLITELY UNRELATED ULTRAGE BAIT FIRST SCENTENCE!
OPPOSING POLITICAL AFFILIATION TALKING POINTS!
MISREPRESENTED HISTORICAL COMPARISONS!
MISSPELLED WORD SALAD!
POINTLESS ARGUMENT IN ALL CAPS!
EASILY DEBUNKED UNTIMELY MISINFORMATION + AN UNVERIFIABLE BUT SUSPISCIOUSLY CONVENIENT ANEDOCTAL EVIDENCE!
<POORLY EXECUTED MEME HERE>

Ok, I think I've given enough fuel for the internet rage machine. Let the next comments increase the garbage dump fire.

Now do a walrus operator!

Girl, I have some bloody poor news. "Finishing my thesis" is, like, about as hard as half of all the classes on a typical program...combined.
At least you get to do it when inspiration strikes (like at 2AM) and not when some uni decides it's class time.

It appears that you are experiencing problems with one of the earlier iterations of ChatGPT. Have you tried turning it off and on again?

Because nearly every product owner / project leader in the entire tech industry drank the AI cool-aid and starts every planning by asking "How can we pivot even harder to AI?"
I imagine that, like, logitech will soon launch a mouse that predicts where you will move it to or something. You just have to sign up to their (paid) service and allow them to record your screen forever. And it's not optional.
Microsoft will put copilot in the freaking window header next. Just wait and see.

Try asyncio. Just as spaghettic and even uglier than threading, but with twice as hard to debug.

@cuddlyogre I wish there was some way to avoid this future. But it is not, because the future has been like this for more than a year now.

Nowadays nobody can cook, not since food delivery was invented. No one can drive, too. Uber made sure of that. No one can write a single word without being punished by autocorrect, guilty of orthographic crimes.
Can you believe people used to tie their own shoes? Zippers ended the art of knots. Soon no one will be able to see or hear without a VR headset, just like they are unable to walk without a Segway.
I blame the homo habilis. Since that stupid "tools" thing, no one knows how to use their teeth and nails.

@Hazarth , they are using models to try and identify man-in-the-middle attacks that are based on DNS, like DNS tunneling.
https://research.checkpoint.com/202...
They literally sniff every package during a DNS lookup...

If the term "post-computer age" smells so bad to so many noses, I guess you could say "not only desktop/laptop age".
Those used to be the only way to use the internet to any practical ends.

Then instagram became a source of income, banking became "mobile-first-but-in-fact-mobile-only" and one can not even order at a restaurant without first asking google for permission to look at the menu.

Too many tears flushed at the same time. Plumbing can't take that much sorrow.
Sorry, I meant "plumbing can't take that much company culture".

Products are designed according to their maker's perception of the needs of the target market.
But AI generative-AI-for-software companies don't want to sell to devs. They want to be in the B2B arena.
So they sell the old narrative that "making smart employees more productive only increases your dependency on them! You should buy our tool so you can hire only clueless, easy to replace, and cheap bumpkins - and fewer of those"

Look at the recent changes in corporate culture seen in large software companies. Innovation is focused on cutting costs, no longer on pushing the edge of possibility. Employees are seen as no more than a hindrance to non-consumer-related deals (like financial, military, and government contracts), and not as strategic assets to be kept even at high costs. Layers and layers of middle management are created to avoid autonomy and standardize operations. Legal became more important than marketing.

They grew tired of devs. So they've forsaken quality and creativity.

@ars1 so, AI would use humans to watch ads (in the matrix) and then download updates? Admittedly, that is like 80% of the modern screen time anyway.

@joewilliams007 , @Ouya , my wife once asked me if she should buy the MacBook Air. I told her how freaking expensive it was, especially given its relatively low specs.
I've shown her other models, just as compact and much, much cheaper.
She ended up buying the freaking fruit brand anyway.
She explained her decision to me: "It is like wearing heels. No bloody practical use, uncomfortable, and objectively a nuisance. It is still what is expected of me in certain situations."
Fucking societal expectations, man.

@Tounai when you're working with some application that goes through many development cycles, it pays to have component and integration tests guiding you.

My team maintains scores of data pipelines that gather from APIs (REST or otherwise), transform and load the data into our databases.
So tests for the gathering components allows us to detect poorly documented vendor API changes, and fix the right software artifacts.
Tests for transformations (mostly statistical analysis of the results) detect data loss or duplication, and ensure compatibility of the results with the target system.
Thereby, a proper test-bed helps a lot when maintaining a complex data pipeline.
And when dealing with known-format outputs (like when adding another source to an existing DB table), it is often better to write the test before writing the payload code.

Frankly, ultra-orthodox TDD is a bit much, but most of the principles can be applied in real life situations.

Gatekeeping in interviews is real, though.

@ceaser basically. To answer your first question:
no, fixing bugs all day long won't be how you spend the rest of your career. It will be a small fraction of your time. The rest will be taken by corporate bullshit, that eats more of your time as you advance your position on the corporate circles of hell.
But the pay may get really good, though.

Dolorem ipsum ... that is not fake Latin, that is an actual poem that says "to pursue pain... because there are some feelings that only pain can provide"
We throw ourselves into software problems because that is the only way to create actual software solutions.

That being said, a bit further into your career and you will miss those moments, crave them even. Because your entire day will be spent on pointless meetings, stupid team building exercises, mandatory safety training on the only approved way of using non-plastic coffee cups, on-boarding clueless juniors to do menial tasks, filling out forms that will never be seen again, explaining the same thing over and over to the same people, and typing your password to log in every 12 minutes.

Because the only devs allowed to code are those that can't really do it. Everyone with more than a pinch of talent is doomed to be made into an overpaid bureaucracy tool.

@magicMirror yep, that is the point... (nearly) *every* mistake AI makes scales to millions of dollars.

@Demolishun there are some workers (in every company) that would do a better job of they didn't do anything at all, so... maybe? for some types of workers?

@cafecortado and a bad tool for the job they're using it for.

@SidTheITGuy it is worth it to comment on things that are just observations, like "the ERP os down", "the booking system is down", "the fucking laptops of the sales team are down", stuff like that. Then, some time later, after thorough analysis, we can finally point fingers at Microsoft. And then tee time.

but a choice, complexity is.

@Demolishun I literally haven't noticed it was CROWD strike and not cloud strike until you pointed that out.
And I've read like 50 different essays on the matter by now. + releases.
Guess I have a serious case of the "service provider blindness"

Now it is time for polishing the LinkedIn