"As it turns out, this world isn't all that complicated. It's pretty simple actually. It's all a game, a very simple game. Of course, some will try to make it difficult. But you can handle them, I know it. I know you can!"

There's a lot of truth in that. When you get into the depths of how the world works, things turn out to be pretty simple.

One thing I cannot rationalize though. The human spirit. The desires that it embodies. I've had this question for so long - what makes us humans human?

If for example a future surgeon - able to exchange individual cells between me and you - would do so, at which point do you become me, and the other way around? 50+% exchange? But that'd mean that at least part of me is still "you". In that state, are you truly you?

Not sure what the cellular definition of an individual is, given that we're headed towards a bionic society where synthetic organs will likely become more relevant than the donated parts of me that I've recently applied as a donor for. I wholeheartedly encourage that future, but the philosophical questions that surround it become more relevant.

How about the impact of influencers on the mind? For example, I've seen the term "certified enganeers" become a trend here, which I'm very grateful for. It does raise a question though. If for example I were to die, would the term live on? And if so, is that a part of what makes me "me"? Would a part of me live on in you? Would your spirit be partially me, due to mere influence?

What makes up the human creature anyway? I think of my own body as a mere vessel for my mind, but I can't quite grasp what makes up the mind, and philosophical questions like "if I were to upload my mind to a robot and instruct it to kill me, would that carbon copy become *me*?"

The human nature is such a weird thing.. and technology doesn't make it any simpler. Is it really just a simple game, with simple rules and e.g. a biological program running inside of a biological motor? Or is there more to it?

2 hour meeting to brainstorm ideas to improve our system health monitoring (logging, alerting, monitoring, and metrics)

Never got past the alerting part. Piss poor excuses for human being managers kept 'blaming' our logging infrastructure for allowing them to log exceptions as 'Warnings', purposely by-passing the alerting system.

Then the d-head tried to 'educate' everyone the difference between error and exception …frack-wad…the difference isn't philosophical…shut up.

The B manager kept referring to our old logging system (like we stopped using it 5 years ago) and if it were written correctly, the legacy code would be easier to migrate. Fracking lying B….shut the frack up.

The fracking idiots then wanted to add direct-bypass of the alerting system (I purposely made the code to bypass alerting painful to write)

Mgr1: "The only way this will work is if you, by default, allow errors to bypass the alerting system. When all of our code is migrated, we'll change a config or something to enable alerting. That shouldn't be too hard."
Me: "Not going to happen. I made by-passing the alert system painful on purpose. If I make it easy, you'll never go back and change code."
Mgr2: "Oh, yes we will. Just mark that method as obsolete. That way, it will force us to fix the code."
Me: "The by-pass method is already obsolete and the teams are already ignoring the build warnings."
Mgr1: "No, that is not correct. We have a process to fix all build warnings related to obsolete methods."
Mgr2: "Yes. It won't be like the old system. We just never had time to go back and fix that code."
Me: "The method has been obsolete for almost a year. If your teams haven't fixed their code by now, it's not going to be fixed."
Mgr1: "You're expecting everything to be changed in one day. Our code base is way too big and there are too many changes to make. All we are asking for is a simple change that will give us the time we need to make the system better. We all want to make the system better…right?"
Me: "We made the changes to the core system over two years ago, and we had this same conversation, remember? If your team hasn't made any changes by now, they aren't going to. The only way they will change code to the new standard is if we make the old way painful. Sorry, that's the truth."
Mgr2: "Why did we make changes to the logging system? Why weren't any of us involved? If there were going to be all these changes, our team should have been part of the process."
Me: "You were and declined every meeting and every attempt to include your area. Considering the massive amount of infrastructure changes there was zero code changes required by your team. The new system simply worked. You can't take advantage of the new features which is why we're here today. I'm here to offer my help in any way I can with the transition."
Mgr1: "The new logging doesn't support logging of the different web page areas. Until you can make that change, we can't begin changing our code."
Me: "Logging properties is just a name+value pair dictionary. All you need to do is standardize on a name and how you add it to the collection."
Mgr2: "So, it's not a standard field? How difficult would it be to change the core assembly? This has to be standard across all our areas and shouldn't be up to the developers to type in anything they want."
- Frack wads smile and nod to each other like fracking chickens in a feeding frenzy
Me: "It can, but what will you call this property? What controls its value?"
- The look I got from both the d-bags I could tell a blood vessel popped.
Mgr1: "Oh…um….I don't know…Area? Yea … Area."
Mgr2: "Um…that's not specific enough. How about Page?"
Mgr1: "Well, pages can cross different areas, and areas cross different pages…what do you think?"
Me: "Don't know, don't care. It's up to you. I just need a name."
Mgr2: "Modules! Our MVC framework is broken up in Modules."
DevMgr: "We already have a field for Module. It's how we're segmenting the different business processes"
Mgr1: "Doesn't matter, we'll come up with a name later. Until then, we won't make any changes until there is a name."
DevMgr: "So what did we accomplish?"
Me: "That we need to review the web's logging and alerting process and make sure we're capturing errors being hidden as warnings."
Mgr1: "Nooo….we didn't accomplish anything. This meeting had no agenda and no purpose. We should have been included in the logging process changes from day one."
Mgr2: "I agree, I'm not sure why we're here"
Me: "This was a brainstorming meeting as listed in the agenda. We've accomplished 2 of the 4 items. I think we've established your commitment to making the system better. Thank you all for coming."

- Mgr1 and 2 left without looking at me or saying a word.

So, I fixed this shitty code, real shitty, inlined some shit and shaved off some other shit and it was fixed...

The reviewer says we'd better request a review from the dude that's actually responsible for that piece of shit code - what the fuck...

Here comes this bossy fucker saying they don't really understand that shit so they don't know for sure if there could be a better way...

Me, ignorant as always, popped a vessel figuring out a cleaner way.

I tell those sick fucks that we'd need to change some shit over at another repository, also maintained by the latter turd.

The latter turd says they like my second suggestion better, to which I reply,

'ok, I agree.'

In my mind that pull was done, should be closed and water under the bridge but oh how clueless I was...

SIX FUCKING MONTHS later the same shitbag pops out of god knows where asking if I still wanted to work on the pull....

"Motherfucker, my pull was for this fucking code, not for doing work on the other, obviously I'm not interested in doing that or else I would've opened a pull there instead of here, dumb-dumb" - I thought

Thou what I said was:

"No, I don't. I agree it's a problem better solved at the other repository."

Maybe I was a bit mean, was I? I don't know, honestly, people confuse me

"Graphic design has been likened to a wine glass. When we drink wine we barely notice the glass it’s served in. It wouldn’t be true to say that we don’t care what glass we drink out of – we wouldn’t choose to drink a rare vintage out of a Tupperware mug, for example – but it’s the wine that matters, not the vessel it comes in. " - Adrian Shaughnessy

I'm torn on dev bootcamps.

On one hand, I learn the most in hands-on direct tinkering and bootcamps tend to exude this with well-trained instructors following best practices.

On the other hand, the short timeline means corners are cut and an overwhelming amount of material is dropped all at once leading to a leaky retention vessel at the end.

I prefer ramping up learning over a period of time to gain experience than a fire hose approach.

One of these days i'm gonna pop a blood vessel, trying to keep all my dotfiles organized: syncing the files themselves is easy, just shove them into git, the problem is that i have to install dependencies on different distros (Arch, Debian and Ubuntu):

The package names are different, the paths are different, fuck with Debian i need to compile from source anyway because most of the packages i need aren't available. Its taking me so much time writing distro-specific installers, just so i can deploy my setup on different machines...

Its at times like these that you appreciate just how mind-boggling fragmented Linux is as a platform :D

I jumped on this NodeJS codebase to quickly implement an additional method in the custom logger. How hard could it be, right?

I implemented the method alright. But I can't find where to use it... There are like 10 different logger instances used in this tiny app and in one place logger is even used as a vessel (holder object) for the client's JWT token (to access it from the interactor).

oh, and it's a javascript app (somehow I assumed that node apps are typescript.. silly me!)

What the fØ©ĸ spaghetty-fest is this!?!?!

For PHP guys here. Are you using Laradock, Vessel or custom/vanilla docker written from scratch? I'm currently using Laradock.

What are the pros and cons? Thanks! 😀

Anyone know of tutorials which use...unconventional project premises? Usually you see To-do apps, sample blogs, and other such generic offerings. Not that those are bad, but I'm interested in finding more outlandish, unconventional examples. Like, say, developing a mock GUI for a spacefaring vessel.

I'm personally interested in examples pertaining to React, VueJS, and Laravel, but if it fits the outlandish and unusual criteria I'd love to see it all the same!