I think having the wrong job can really bring down the quality of life.

My friend has to drive two hours each way to get to and from work. That's four hours wasted commuting.. and his job is service desk agent.
What are the consequences, you ask? He never has a spare second to talk to me, he's quickly developing gray hairs and he has no time awareness.

Having the wrong job is unhealthy and results in a cascade of bad side effects.. When most of your day involves work-related things, that's just wrong. There is no Yin-Yang there. I know because my work life is somewhat balanced.

And this, ladies and gentlemen, is why you need properly tested backups!

TL;DR: user blocked on old gitlab instance cascade deleted all projects the user was set as owner.

So, at my customer, collegue "j" reviews gitlab users and groups, notices an user who left the organisation
"j" : ill block this user
> "j" blocks user
> minutes pass away, working, minding our own business
> a wild team devops leader "k" appears
k: where are all the git projects?
> waitwut?.jpg
> k: yeah all git projects where user was owner of, are deleted
> j.feeling.despair() ; me.feeling.despair();
> checks logs on server, notices it cascade deletes all projects to that user
> lmgt log line
> is a bugreport reported 3(!) years ago
> gitlab hasnt been updated since 3 years
> gitlab system owner is not present, backup contact doesnt know shit about it
> i investigate further, no daily backup cron tasks, no backup has been made whatsoever.
> only 'backups' are on file system level, trying to restore those
> gitlab requires restore of postgres db
> backup does not contain postgres since the backup product does not support that (wtf???)
> fubar.scene
> filesystem restore finished...
> backup product did not back up all files from git tree, like none of refs were stored since the product cannot handle such filenames .. Git repo's completely broken

Fuck my life

the team gave access to the database to another team, and one of their guys did a delete cascade by mistake thinking it was theirs... everyone was scrambling for days trying to get a backup, thankfully there was one

People: Uhhhhh CSS is such a bad language it's impossible to maintain it, the cascade is stupid
Also people:

When you realize your face detection doesn't work because you used the cat face cascade

How I feel when I have to restore bits and pieces of a live database from an old backup

Cascade Style Shit

1. Coding gets me naturally high. Mentally sound and sharpens my focus.

2. Beating a challenge by code is fun. And watching something I spent much time on working is great. Like setting up all those dominos to watch them cascade and fall down one after another...bliss!

3. People think I'm smart because I can type instructions into inanimate objects and make lights flash on the screen.

!coding

I used to be a sysadmin, which meant I was in charge of quarterly server patching. My team managed about 2500 servers, running various flavors of linux and legacy unix. The vast majority(95% or more) ran Linux(SLES). Our maintenance window was always in the overnight-- 10pm to 6am --so the stroke of 10pm would be a massive cascade of patching commands sent to hundreds of servers.

Before I was brought into the process, it made use of the automation product we were tasked by mgmt to use: Bigfix. It's a real piece of shit. Though we had 2500 or so servers, this environment was dominated by windows. All our vcenter servers ran it, and more importantly, our bigfix nodes were all windows machines. That meant that while we're trying to patch, the bigfix servers would get patched by the windows team. This would cause lots of failed and timed out patching, because the windows admins never quite understood that taking down the automation infrastructure would cause problems.

As such, I got tired of depending on a bunch of button-pushing checkbox-clickers who didn't know shit about shit, so I started writing an ssh-wrapped patching system. By the time I left for my current job, patching had been reduced to a single command to initiate each group's patching and reboots, and an easy check to see when servers come back up. So usually, the way it worked out was that I would send patching orders to 750 machines or so, and within about 5 minutes, they would all be done patching, and within another 20 minutes all the ones that required rebooting but about 5 would be done rebooting.

The "all-nighter" which happened every time was waiting for oracle servers to run timed fscks against a dozen or so large filesystems per server, because they were all on ext3/4, which eats complete shit. Then, several hours later, as they finished, I would have to call the DBAs to tell them to validate their shitty servers.

Me: Oh, man, there are hooks for react-redux now? I don’t have to wrap components in a higher order component to get information from the redux store and dispatch actions? Could this solve the problem I’m having with data fetching and consistency in the app I’m working on?!

Spends entire Saturday writing a basic server, connecting to an mLab instance, filling said instance with dummy data, starting a create-react-app, writing a reducer, action creators, components, etc. just to test how useSelector(), useEffect(), and useDispatch() would work in an application that isn’t just a simple counter (why is it that like every example is always the counter example?!). Bonus, react-router now ALSO has hooks, so got to play with useHistory() and useParams()

Conclusion: Maybe. It does appeal to me to not have the cascade of virtual DOM that you always get nesting HOCs, but I’m also wary of appearing too willing to jump on it just because it’s the new thing.

Has anybody else played around with react-redux hooks? Your thoughts?

Also, yes, I know, not every app needs redux. It had it when I was brought on and I don’t really have the ability to change that implementation detail now.

There are no stupid or dumb questions. A lot of headache has been and could have been saved by one person asking what seemed like a stupid question.

I would now expand on this to say that if the question is procedural in the sense that it’s asking “what” or “how”, you should make every attempt to come to an answer yourself and then ask for clarification. If the question revolves around “why”, there are no stupid questions. A lot can be overlooked in a cascade of moving pieces.

I see people ++ my post.

I myself cannot even find the ++ button.

I'm blind as a bat and I write CSS for a living.

I just realized my senses must have adapted and I can probably hear stylesheets cascade.

Bad leaders are simple - they give someone a job - simply to return an eon later unhappy with the progress - without seeking to understand a single component of the events that transpired during their absence. Place this mentality at the top of the hierarchy, and it will cascade throughout an entire organisation.

Seeing the way people write CSS I understand why they think it's badly designed. It's just that they don't use it properly, they don't think about general structure of the system, they just haphazardly pile up declarations, recklessly abusing cascade.

CSS - with great power comes great responsibility.

Whoever came up with the idea of styled components and other idiotic css-in-js bullshit because they couldn't be arsed to understand fucking cascade deserved all the bullying they got in the highschool. And all those idiots who adopted it because they couldn't be arsed to understand fucking cascade should get waterboarded.

Embedded database is so lack of choice. SQLite, might be best, if you want stability / ACIDity.

Again, SQL means normalize everything, if I've ever want to index it...

Then, ON DELETE CASCADE? TRIGGER? Also, MANY-to-MANY kills.

I loosely set aside Friday evening, Sunday and Monday for a rush job that was supposedly urgent. Monday I was sent the style-guide. It's mandatory to be written with bootstrap. Tuesday 10am, no copy, no images, no idea where the code will go or how it's context's global CSS will cascade over mine. Visual designer says the logo they provided me isn't crisp enough. How many grown adults does it take to screw in a lightbulb? 9?

"Front end developers" who don't understand the cascade are my favourite thing. Just use BEM dude, you don't need some fucking scoped components with dynamically evaluated CSS-in-JS.

"To be truly great, we have to understand the motivation of our clients, maintain constant two-way communication with shockingly uncreative people, get a firm handle on copywriting and how that craft exists symbiotically with the visual element, and foresee how the finished whole will be greater than the sum of the bits and pieces we spent hours obsessing over. All of these factors cascade into the final product." - Kevin Potts

The days are long right now. The company portal, that I built, is being rebuilt now that we have decided it needs to be responsively designed.

I always knew there would come times in my career, if I leant towards the front end, that periods of time would be taken up with HTML/CSS.

I just didn’t appreciate how soul sucking it can be when you are adjusting margins for 8hrs a day for a few weeks. And how much that is compounded by people changing their minds on things that cascade throughout an increasingly complex system of media queries...how you can spend ages tweaking something only to find it breaks on an another screen size...

The love I found in coding...it is not here...

I fucking hate it that "front end developer" came to mean "data flow for react engineer". It seems most frontenders now don't understand shit about HTML and its standards, don't know anything about basic accessibility and proper content structuring.

It's even worse with the styling. Cascade? The fuck is cascade? Scope everything! And, of course, write that CSS as a JS object because how else. Fluid typography? If by fluid you mean 16px, sure. Any more advanced techniques? Lol forget you're getting rounded boxes with a shadow and you're gonna like them.

But yeah, I'm glad they're overengineering Redux again because their reactivity model is fundamentally broken. That's exactly what """frontend""" should be about.

Start my code day, no bugs in sight,
Each line I write, like code's delight.

Second function, errors suppressed,
Silent fixes, my skills put to the test.

Third loop, logic numb, yet breaking,
A contradiction in every line I'm making.

Fourth bug, clinging like a leech,
In the grip of coding's caffeine breach.

Fifth syntax, thoughtless actions cascade,
A program's dance, in lines arrayed.

Sixth compile, colleagues say, 'Go home,'
But where's home in this code dome?

'They say home is where the heart is,
But my heart's in a million logic twists,
Which line shall I follow?
The optimized or the broken,
I cannot tell them apart.'

In the last bit of code, I saved my hope,
When debugging was still an option,
So go ahead and save yourself from glitches,
For you are worthy of a million exceptions.

FUCKING. HAAR.
WHY CAN'T YOU FUNCTION PROPERLY EVEN AFTER SPENDING HOURS INTO TRAINING YOU???!!
DO YOU REALLY WANT ME TO ABANDON YOU CASCADE CLASSIFIER?
You were like a brother to me. Now look at what you've done.

Hibernate Cascade Type is in fact the source code of all evil...

I'm going insane.

So let's say you have an object in database, with 20-30 related objects (Or lists of objects) (All related objects have a foregn key to the "main" object).

Now, as long as you just edit/create thinga everything is fine.

But the deletion... Oh MY GOD

"Just put on delete cascade", right ? RIGHT ?

WRONG ! presence of some objects should block delete, while others can be deleted and some are "situational" depending on the first object state.

So delete operation with all the checks takes .... 1 - 2 seconds.

Seems fine ? WRONG ! When you have 40 or more objects to delete, even 1 second is too long.

Should I say "fuck it" and just write a stored proc which will crash if object cannot be deleted for any reason ? because with Entity Framework, I don't see how I can do it effitenly.

But I HATE stored proc, after couple of month/years noone remembers how they work...

RHAAAAA.

Ok I feel better.

Finishing work on a Friday when cascade delete won't cascade delete in EF and throws foreign key issues. That's my weekend doomed to be spent obsessing over why.

Piss.