"Welcome to everybody's favorite show: Did It Break!?!"

"Here's our first contestant, Alex Brooklyn!"

* Audience claps *

''Tell us Alex, what command did you use?!"

ls -la

"And did it break production?!"

Not yet..., the website is still up, even checked without cache and on a different network, I haven't had any calls in half an hour and Sentry reports nothing

"Great to hear! On to round 2!"

Just made a laser sentry tower for my cats. Next up is adding some tracking so it can play with them by itself while I'm at work and after that I'm adding a Wi-Fi module and camera so that i can also play with them while I'm at work... I couldn't resist using a mouse to top it off 😂

I used the python to destroy python

Firefox is running in our universe and are some bits of data

1. Fucking MySQL database clusters.

There's nothing fun about MySQL clusters. Sometimes they start producing deadlock errors for no apparent reason... well, there's probably a reason, but it's never a transparent easy to find reason.

What was even less fun is that those errors took down a Sentry server. When your error log server goes down through ddos from your database messages, it's time to rethink your setup.

2. Wiring up a large factory with $2 arduino clones, each with a $2 esp8266 wifi chip, with various sensors for measuring flow of chemical solutions (I wanted cheap real time monitoring as an early warning system next to periodic sampling).

The scaling issue was getting over 500 streaming wifi signals to work in a 55c moist slightly corrosive atmosphere with concrete and steel everywhere, and getting it all into a single InfluxDB instance for analysis.

1. Slack. Pretty good chat app for dev companies, I use it to prevent people standing next to my desk 40 times a day.

2. Unit testing tools, especially when fully automated using a git master branch hook, something like codeship/jenkins, and a deployment service.

3. Jetbrains IDEs. I love Vim, but Jetbrains makes theming, autocompleting & code style checks with mixed templating languages a breeze.

4. Urxvt terminal. It's a bit of work at the start, but so extremely fast and customizable.

5. Cinnamon or i3. Not really dev tools, but both make it easy to organize many windows.

6. A smart production bug logger. I tend to use Bugsnag, Rollbar or Sentry.

7. A good coffee machine. Preferably some high pressure espresso maker which costs more than the CEO's car, using organic fairtrade hipster beans with a picture of a laughing south american farmer. And don't you dare fuck it up with sugar.

8. Some high quality bars of chocolate. Not to consume yourself, but to offer to coworkers while they wait for you to fix a broken deploy. The importance of office politics is not to be underestimated.

Me: * Browses devRant for about 10 minutes *

Phone: 0 notifications

Me: * Puts phone in pocket *

Phone: * seizures in pocket *

Phone: 3 new Jira issues, 9 Sentry warnings about critical bugs, 2 emails from my boss, roughly 60 Whatsapp messages and 3 new notifs on Slack

Why does this happen so often :/

dear api author at my company pt. 2:

If you're gonna create an api method that takes some arguments.

And one of those arguments is an array.

THEN MAKE THE FUCKING ARGUMENT'S NAME PLURAL YOU FUCKING PIECE OF SHIT.

REPEAT WITH ME, MOTHERFUCKER.
ARRAY, PLURAL, NON-ARRAY, SINGULAR.

I need to pass a shitload of filters for the data for this table, and for every suckin fuckin filter I need to singularize this shit. Thank god for es6.

I know this sounds like nitpick, but I swear to fucking alpha omega this guy is inconsistent as fuck.

Every time it feels like he makes up a new rule.

Sometimes I need to send arrays of ids, other times arrays of objects with an id property on each.

He uses synonyms too, sometimes it's remove, other times erase.

PICK ONE MOTHERFUCKER.

If you can't do the basic things well, then what is to expect of more advanced stuff?

Naming conventions you fucking idiot, follow them. It's programming 101.

You're already sending them as plural in the fucking response. Why change them for the request?

And that's just style, conventions.

This idiot asshole also RARELY DOES ANY FUCKING CHECK ON THE ARGUMENTS.

"Oh, you sent a required argument as null? 500"

We get exceptions on sentry UP THE ASS thanks to this useless bone container.

YOU'RE SEEING THE EXCEPTIONS TOO!!!!! 500'S ARE BUGS YOU NEED TO FIX, YOU CUMCHUGGER

And sometimes he does send 400, you know what the messages usually are?
"Validation failed".

WHYYYYYY YOU GODDAMN APATHETIC TASTELESS FUCK???
WHAT EXACTLY CAUSED THE FUCKING VALIDATION TO FAIL????

EXCEPTIONS HAPPEN AND THANKS TO YOU I HAVE NO IDEA WHY.

The worst of all... the worst of fucking all is that everytime I make a suggestion to change shit, every time, you act like you care.
You act like the api is the way it is because you designed it in a calculated manner.

MOTHERFUCKER. IF A USER HAS ONLY PRODUCT A, THEN HE SHOULDN'T BE ABLE TO ACCESS DATA FOR PRODUCT B. IT IS NOT ENOUGH TO JUST RESTRICT SHIT WITH ADMIN ROLES. IDIOT!!!!!

This is the work of someone who has no passion for programming.

Ya boi got a new vehicle. Its an SUV(cuz i got kids) a nissan murano 2017, maaaan this one is a good vehicle.

When I leave the truck on and I take the keys with me it makes this little beeping sound. And because I am weird I like to say: "ah, sentry mode"

I spent 10 years driving a Honda Civic. Not gon a lie, it was a really good car and it never gave me any issues. But it was starting to show its wear and tear and I didn't trust it for a long trip sort of deal.

Is this dev related? Fuck no, I was just fixing to be random and te y'all I got a new vehicle.

Texas

Today I received an Exception triggered Sentry issue that just read "Nope".

Last Scrum Meeting, set up our new Container Server and installed Sentry (Bug Reporting Tool) on it. I was pretty proud, since it was one of my first DevOps thingies I had to work on. (I may end up as a DevOps Engineer after my Internship) In the scrum meeting, the colleagues just start saying everything with a French accent and just laugh about their french jokes while I'm in the middle of showing them sentry.. they were literally unstoppable... 😡 And weren't paying any attention to my presentation.

Embarrassing screenshare story? Yeah, I've got couple of those.

- Showing one client a VSCode workspace of another client's. I was lucky they didn't escalate or anything.

- YouTube open in PIP mode and accidentally showing that to the higher-ups in company. What made it more embarrassing is that they informed me about it, I thought I was sharing a window not Entire screen.

- WhatsApp open in one window and I accidentally shared it on screen, thinking I wasn't sharing my screen, but I was, and everyone saw my texts with a girl I was "dating" at the time.

- Presenting my entire screen to a client and out of nowhere Epic Games pop up with a notification saying ""Your buddy sent you a message - Ready to start playing?". But that was 11pm so I got off easy.

- Opening sentry to show one thing to the client but they notice many new bugs and I got slammed by my boss for it.

2 hours ago my vacation started

5 minutes ago I got a sentry error, a certain page is inaccessible for some reason

Guess who's definitely not going to fix that

(there are other people that can fix it tomorrow)

Lovely, We just got told to ditch Sentry and just check the /var/log/ of the server for issues......

How do I argument back against this...

So after multiple hours of wrestling with Jira I finally managed to autofill fields in the service desk. How? By installing a plugin to show message boxes and injecting JavaScript through it, what else?

Fucking wonderful piece of crap :)

Next up: automatically capture errors triggered by employees with Sentry and raise Jira requests. "A button didn't work" isn't enough god damn it.

Today we got our Sentry integration (exception aggregator with a lot of nice features) working just to see a user using IE5 on a Windows 2000 machine causing exceptions. It made my team’s day.

We use celery at work, and one of the issues we face is that we use Django logging.
I'm not sure how it happened, however we only get 1 level of tracebacks from it now.

This has made debugging painstakingly difficult, since we have to manually traverse the code every time.

(we're in the process of moving to sentry, and we'll get our full logs back soon)

Yesterday I had a user reachout via email because his account became inaccessible when he updated it.

This was something I didn't realize could happen... so it was fun recreating this scenario locally.

Basically he somehow bypassed the lowercase requirement for the updateUsername endpoint. So in the DB, his name was uppercase. And the SQL query was searching for his exact username without doing LIKE (by design).

It was failing on that getProfile endpoint and showing a Whoops screen. 😬 Should be a 404 screen, I know. I'm working on it.

Since then, I added Sentry logging to the backend and frontend.

And this showed me there were endpoints still being triggered nightly to remove stale data. (I forgot to remove). And these endpoints were getting 401's. I'm thinking who TF is triggering these endpoints. I soon realized those specific endpoints needed keys that expired monthly. 🤦‍♂️

Had to reinstall Gmail on my phone... Settings lost, it defaulted to push notifications for all messages.

Someone broke a per-page analytics call.

1,300 Sentry warning emails in an hour later, I'm finally annoyed enough to do something about it, but the settings UI is horrible. 😥

I hooked our Web app to Sentry and fixed a bunch of never before perceived errors. It now feels like a bullet train steaming down sturdy tracks instead of a goat suffering from fainting syndrome.

Who else is frustrated/burnout at building products that never gets into production?

When I work for a company I always tend to do everything with good practices, spend a lot of time thinking on the best ways to build x feature, and then the company falls into the infinite loop of adding stupid features, and then I've been working for 2 years and 0 paid customers. Funny that we've Sentry, GA, Hotjar sitting there doing nothing.

I'm honestly hating the startup environment rn. Good thing is that I've learnt a lot and salary is good. But also I lost all motivation.

Any recommendations for a tired dev?

Sentry going up.
*Bap*
*Bap*
"I built that"

First time using Sentry is like seeing colors for the first time...
My life has changed forever. I can't go back!

Guys can you help me with sentry integration in angular 7 app ?
It capture errors but need to know the line number in the typescript source file not in the minified js file. Any hint ?

#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

My biggest revelation of all time: "sentry"