The only reason I use Linux is because I can't get a mac.

I just love refactoring :) that feeling when an agonic 50loc method with ifs, loops, streams, other shit shrinks down to 3 lines with descriptive and SRP-compliant method calls.. When you can actually read code as a nicely written story. When there are no rubbish comments, cryptic variables and no overly complex if-else skyscrapers jamming all the logic in one conditional chain. When all the abstractions are designed so nicely and design patterns applied so perfectly that extending either of the components is as easy as a walk in a park.

When everything is nice and neat. Only then can I sleep well and enjoy the autumn :)

just some random thoughts after today's coding session :)

Best practice of the day:
Single responsibility principle - One class should be responsible for everything!

Either that or someone was payed for LoC. 😁

Now my facebook messenger app does it's updates inside the app without my consent to install an apk.
I'm scared

When they tell you they put all the js code in a `core.js` file

My password manager!!
I use passwords I can never remember, stay logged in, next time I need to log_in I use the passqord forgotten button, reset it with my e-mail or better phone

After working with a coworker on some odd issues, I finally decided to check on the actual ticket he needed assistance with.

From now on, we will optimize our HTML for aesthetic appeal in Chrome's dev tools. display:none is verboten.

Sometimes I wonder if I've had a stroke or if I've died and am in purgatory.

This class adheres to the single responsibility principle: it is singularly responsible for the entire application.

A shower thought:
vaginas have a design superior to penises, because they follow SRP more closely

You know you hit rock bottom when can only comunicate with a chat bot.

So, I was given the task to fix a bug from a "legacy" codebase, and then I saw this.

I'm starting to feel like coding is too much boilerplate all the time.

I've been thinking about why, and I think (and I'm trying to sound humble here) it's because I'm usually honoring the SRP. But this entails this enormous drawback of enormous amount of code!

Don't get me wrong, I'm usually glad with the design I end up with .... but only after what seems to be hours of typing

Anyone recognize this problem? Suggestions, comments?

The sticker would look amazing on my laptop, too bad i'm not going to get one soon 🙁🙁

#Suphle Rant 9: verbatim exception scare

In multiple rants, I've bitched about laravel stealing suphle features. By some very weird coincidence, it appears I've been given a taste of my own medicine. Let me explain:

We're having a chat this morning on a laravel group chat when someone says he uses their notification component a great deal. Curious, I ask him what he uses it for since I only used it sparingly during my laravel days. To pry an answer out of him, I ask whether he uses them for sending app error alerts to a slack channel, and he responds with an eerily familiar term. I quickly look it up and the results on the docs are chilling: errors can be sent to bugsnag (which suphle has an integration for), sentry and Co. Errors can either be broadcast or disabled. Specific kinds of errors can be caught. My heart sunk. My brother called for something while I was going through it and I was struggling to pull myself together

Their exception component is almost identical to mine and I'm only just realising. It's shameful that I'm just learning about functionality present since 5.8. I thought my creation was novel. BUT! The good news is, the implementation differs

Too many errors went unnoticed during my time there because error broadcasting is optional. Since none of my colleagues read that part of the documentation, we were firefighting by pulling and wrangling production error logs. This informed their abolishment in suphle altogether

A relatively minor difference is in the APIs –their philosophy makes significant use of global functions, violating SRP, etc.

But the most important difference, that still cheers me up, is that they only catch known errors. Suphle has a construct for isolating calls to a decorated service. Any unforeseen error to occur during its execution will do a series of things before control is returned to the caller

Anybody using Jetbrains PyCharm on Linux ?

I'm using Fedora 25/ pre-release, and It's rock solid except for wifi hotspot and I don't need it.

Now my school gave me a Windows 10 pro key, and I'm hesitant.
Should I install it ?
Will I need it ?

Just found a service method that saves an entity that isn't related to that service, that returns a ModelAndView object. I think my brain just broke. 1) Single Responsibility Principal. Do not save ObjectB in ObjectAService. 2) Services should not be aware of your view context. That's what controllers are for. Do not return a ModelAndView from a service method.

I need a scraper, or a f$$$in api