Declare variables not wars,
Build packages not walls,
Execute programs not people,
Throw exceptions not stones.

IOS SUCKS!! SWIFT SUCKS !! OBJECTIVE-C SUCKS!! SUCK MY DICK APPLE YOU PIECE OF SHIT !! Why did you have to make the language sooo counter intuitive, and so different from the popular languages you pain in the ass piece of shit, Why can't I throw exceptions from a constructor of a class?? Why do I have to use a fucking struct to just throw exceptions?? Can't class constructions fail you peice of shit?? huh? GOD DAMN IOS MAGGOT DEVELOPERS IF I EVER RUN INTO THOSE FUCKERS IM GONNA FUCKING RAPE EM BURN THEM ALIVE AND HAVE THEM FOR DINNER

Like many others my favourote shameless hack is a cronjob to restart our app server at 2am, thus preventing out of memory exceptions

When you finally accept that the code will never be bug-free and instead make friends with the uncaught exceptions.

Did this on my first programming exam.

int index = 0
int value = 0
try {
while true {
value += array[index]
index++
}
} catch NullPointerException {
System.out.print("Sum: " + value)
}

The task was to add together all numbers in an array.

I somehow aced the exam, but got called in to teachers office this is not the way to use exceptions.

After several months of bug fixing, I can proudly say the application I inherited at work has gone a whole day in production without an unhandled exception (from a peak of above 1200 a few months ago).

Well, either that or I've broken the error logging and am now living in blissful ignorance.

Senior Dev: "Be mindful of what you email to the team, some may be rubbed the wrong way."

Me: "I'm going on a year, I figured it was okay to send a meme when appropriate like [the other guy]."

Senior Dev: "Well, [the other guy] has been here for 17 years, so it's sort of expected from him."

Me: "You know what would be weird? If I was here for 17 more years and then 'started' having fun with the team."

Senior Dev: "Yes, but [the other guy] is the only one doing his particular job, which makes him important, so he tends to get away with more."

Me: "No, I get it. If you're a linchpin you can reply with cat memes, but people like me need to mind their place."

Senior Dev: "It's an uncomfortable conversation, but it's all bureaucracy."

Me: "Duly noted. But could you please forward me the specific email I sent that caused the concern?"

Senior Dev: "I'm not sure what the exact email was, when it was sent, or specifically whom it offended."

Me: "Okay, because that would be like me walking up to you and saying that you have a problem that needs to be fixed, but I don't know what your problem is or why it needs to be addressed."

Senior Dev: "You're right, but just be mindful of the emails you send outside of the group."

Me: "I've never group-emailed anything outside of the team."

Senior Dev: "Well, I'll let you get back to work..."

[FML!] 🤦‍♂️

Definition of Linux users...

"A computer lets you make more mistakes faster than any other invention in human history, with the possible exceptions of handguns and tequila." - Mitch Ratcliffe

Best way to handle exceptions..

There's a fancy new coffee machine in the office. When it breaks, it displays java exceptions on the screen. 😂

Java: Ok, any ideas on how to make women more interested in us ?
.
.
.
C++: Make more exceptions ?
Python: Redefine our methods ?
C: Stop treating them like objects ?
.
.
.
*Java furious at C*
.
.
.
*Java throws C out of the building*

It always throws back ;)

Hmmm..

Just spent the whole day rewriting a 5,000 line function with variables like num55 or num287. These variables constantly get re-used for different purposes and overwritten at will.

Everything is now broken. Including my spirit.

Annoyingly typical office conversation:

Person 1: "Good morning."
Person 2: "Good morning, how are you?"
Person 1: "Good. How are you?"
Person 2: "Good."
Person 1: "Good."

NO! Not good, fuckers. I hear this all day long, come up with something real or original. Talk about the massive shit you just took, or how hard you're taking the news about Diablo Immortal. It reminds me of that scene in Office Space with the repetitive call center lady, lol.

Phone in my cubicle goes straight to voicemail when someone calls. Boss wants me to get it fixed so clients and he can reach me.

Yeah, I'll get right on that. 👌

When you see .NET exceptions making their way into Indian Railways!
Damn that was unexpected!

Got laid off on Friday because of a workforce reduction. When I was in the office with my boss, someone went into my cubicle and confiscated my laptop. My badge was immediately revoked as was my access to network resources such as email and file storage. I then had to pack up my cubicle, which filled up the entire bed of my pickup truck, with a chaperone from Human Resources looking suspiciously over my shoulder the whole time. They promised to get me a thumb drive of my personal data. This all happens before the Holidays are over. I feel like I was speed-raped by the Flash and am only just now starting to feel less sick to the stomach. I wanted to stay with this company for the long haul, but I guess in the software engineering world, there is no such thing as job security and things are constantly shifting. Anyone have stories/tips to make me feel better? Perhaps how you have gotten through it? 😔😑😐

I login this morning

Everyone going crazy as prod is broken in a million ways. 2.5 million exceptions In 24 hours.

We talk for 1 hour and solve nothing.

I diagnose the 2 biggest sources of exceptions and explain every step I took with screen snippets to reach my conclusions

The one other competent person on my team agrees. Otherwise complete silence.

I'm told not to fix the issue because I am leaving in 6 weeks and other people have to start taking responsibility.

No one fixes the issues. Instead they leave early. Now it's the weekend and the product is fucked.

Fucking useless people. Can't wait to leave.

Some days I feel like I work in a different universe.

Last night our alerting system sent out a dept. wide email regarding a high number of errors coming from the web site.

Email shows the number of errors and a summary of the error messages.

Ex. 60 errors
59 Object reference not set to an instance of an object
1 The remote server returned an unexpected response: (413) Request Entity Too Large

Web team responds to the email..

"Order processing team's service is returning a 413 error. I'll fill out a corrective action ticket in the morning to address that error in their service. "

Those tickets are taken pretty seriously by upper mgmt, so I thought someone on the order processing team would point out the 1 error vs. 59 (coming from the web team's code).

Two hours go by, nobody responds, so I decide to jump into something that was none of my business.

"Am I missing something? Can everyone see the 59 null reference exceptions? The 413 exception only occurred once. It was the null reference exceptions that triggered the alert. Looking back at the logs, the site has been bleeding null reference exceptions for hours. Not enough for an alert, but there appears to be a bug that needs to be looked into."

After a dept. managers meeting this morning:

MyBoss: "Whoa..you kicked the hornets nest with your response last night."
Me: "Good. What happened?"
<Dan dept VP, Jake web dept mgr>
MyBoss: "Dan asked Jake if they were going to fix the null reference exceptions and Jake got pissed. Said the null reference errors were caused by the 413 error."
Me: "How does he know that? They don't log any stack traces. I don't think those two systems don't even talk to one another."
<boss laughs>
MyBoss:"That's what Dan asked!..oh..then Jake started in on the alert thresholds were too low, and we need to look into fixing your alerting code."
Me: "What!? Good Lord, tell me you chimed in."
MyBoss: "Didn't have to. Dan starting laughing and said there better be a ticket submitted on their service within the next hour. Then Jake walked out of the meeting. Oh boy, he was pissed."
Me: "I don't understand how they operate over there. It's a different universe.
MyBoss: "Since the alert was for their system, nobody looked at the details. I know I didn't. If you didn't respond pointing out the real problem, they would have passed the buck to the other team and wasted hours chasing a non-existent problem. Now they have to take resources away from their main project and answer to the VP for the delay. I'm sure they are prefixing your name right now with 'that asshole'"
Me: "Not the first, won't be the last."

Well fuck me in the ass and call me Charlie.

I just had to bare witness to 2 years worth of files being deleted due to a minor.. well.. minor in the sense of not checking for an empty string, but massive fucking bug.

Thank all the gods of all the religions for backups!!

I love when job postings are like, you will use THIS tool, and THIS is how it will be accomplished!!!! NO EXCEPTIONS!!!

bitch, i'm the senior engineer, I should be the one picking and choosing tools to match your needs, not you and HR pals!

no wonder your job offer still isnt' filled!

i'd love to ask these organizations why they chose such boomer technologies in the first place and why there is no effort to change to much more developer / user friendly tools.... just a red flag from the start

What's the worst thing you can say to a programmer parent?

"You've not raised kids.. you've raised exceptions"

"Fatal Error"
Exceptions? No, let's just halt the entire program.

Apparently a CS professor wrote this code.

"Needed to keep the compiler happy"

that's quite accurate :) ofc there are exceptions (looking at you two naughty bois, metaspace and off-heap allocations!), but it's true for the most of it :)

try {
…..
} catch {
// this would never happen
}

and then it happened

fucking always print something when you catch exceptions

My programs never crash. I wrap my main functions in a try catch, and silently ignore exceptions.

Rather than singling out one person, I wanna present what I see as incompetent/stupid/ignorant:
- no will to learn
- failure to follow the very specific instructions & later asking for help when they FUBR sth & not even knowing what they did to fuck up in the first place
- asking how to solve stuff, then ignoring the suggestions & doing sth totally against recommendations
- failure to remember most basic stuff, especially if not writing it down to look at later when needed
- failure to check logs & 'google' stuff before asking why something isn't working the way they want it
- after two weeks, asking me how feature xy works, mind you they coded it, not me
- asking me why they did something in a specific way - WTF, am I a mind reader?! Who designed that crap?! Me or you?!!
- being passive/aggressive & snarky when told to do something or being asked why isn't it done already
- not testing their shit properly
- not making backups when upgrading (production) servers
- not checking the input value, no validation.. even after many many debacles on production with null ref exceptions
- failure to admit they fucked up
- not learning from (their) mistakes

What?!

I finished two projects. Both of them need to connect to each other. However, the tool to do that is not currently licensed to achieve my desired outcome. I email my boss to check the status of the license key I need, that they promised, and the only thing I get back is "Correct." Seriously? 😠 The person who has the company credit card and authority to buy, also the same one that gives me a deadline to turn this shit in, can't give me the time of day to respond to an email? Their response wasn't even relevant. I've been trying to move beyond this roadblock for a week now! I'm a pretty independent guy, but I'm not going to buy the license myself for a tool that I didn't even want to use. So when someone comes to my cube and I'm raging on Steam, ✋ I don't want to hear anything about company time, because mine isn't being respected either. 👊👊

Handle all exceptions with
catch(Exception ex)

I'd like to see a horror movie called "Exception", where the main character experiences exceptions which should not happen according to the code's logic.

I've met some brilliant people in my career, the problem is, the more brilliant, the more of a jerk they are (typically, there are some exceptions though). Sure you may be incredibly smart, but no one wants to work with that kind of arrogance and it's probably why you still can't find a job.

The good Java practices...

Yahoo, Kotlin is the first class language for android. So no more fucking Java codes. No more 100 lines for basic configurations. No more null pointer exceptions.

Only beautiful code and fun.

Also a cautionary depiction of coding in dim rooms without a dark theme...

"Change your algorithm"

Answers like this are why Stack Overflow almost becomes worthless when asking questions. I asked for some clarification why my code, which reads some files and outputs another, was hitting System.OutOfMemory exceptions. And that was the response I got.

"Change your algorithm"

How? In what manner should I be seeking to change my algorithm? OBVIOUSLY I SHOULD CHANGE MY ALGORITHM YOU WASTE OF OXYGEN. That was a given by the exception my program threw!

I swear to god, SO has got to be one of the most unwelcoming, condescending sites on the internet.

found this in our codebase today

try {
//do something
} catch () {
try {
//do something else
} catch () {
try {
//do something else else... this goes on 4-5 levels deep
} catch () {
//log... couldn't do
}
}
}

Behind-the-scenes of basically every commit titled "added exception handling"

Handling exceptions like a boss.
Thanks for the informative message, ATM.

So the story start like this, 6 months ago i left my job in a big company for an oportunitiy to work on a new one without all the bureocracy and shit and with better benefits , the first months were wonderful we were using a nice stack of technologies and the team that was assembled was a nice one with smart and hard working people with a few exceptions, but overall very good. One day out of the blue the manager started to presure us to release a project that was on time and wanted us to make extra hours and work on saturdays, sadly we blindly did because we cared for what we were creating, fast forwarding to yesterday, the whole team was called to a meeting and our contracts were terminated without previous advice because the company could not afford to pay us for more time and blahblahblah..., soo here i'm feeling used and sad but with renowed feelings about starting my own business!!

Just found a
catch {
// TODO: correctly handle exceptions
}

In production code.

Rule 34.

"If it exists, there is porn of it. No exceptions." Rule 34 (novel), by Charles Stross

Same thing applies to npm modules.

The GashlyCode Tinies

A is for Amy whose malloc was one byte short
B is for Basil who used a quadratic sort
C is for Chuck who checked floats for equality
D is for Desmond who double-freed memory
E is for Ed whose exceptions weren’t handled
F is for Franny whose stack pointers dangled
G is for Glenda whose reads and writes raced
H is for Hans who forgot the base case
I is for Ivan who did not initialize
J is for Jenny who did not know Least Surprise
K is for Kate whose inheritance depth might shock
L is for Larry who never released a lock
M is for Meg who used negatives as unsigned
N is for Ned with behavior left undefined
O is for Olive whose index was off by one
P is for Pat who ignored buffer overrun
Q is for Quentin whose numbers had overflows
R is for Rhoda whose code made the rep exposed
S is for Sam who skipped retesting after wait()
T is for Tom who lacked TCP_NODELAY
U is for Una whose functions were most verbose
V is for Vic who subtracted when floats were close
W is for Winnie who aliased arguments
X is for Xerxes who thought type casts made good sense
Y is for Yorick whose interface was too wide
Z is for Zack in whose code nulls were often spied

- Andrew Myers

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.

When you're tired of googling your errors

TIL: C# has a "Catch When" syntax to help you filter exceptions. It already allows you to filter by Exception type, but this is news to me since it allows for finer filtering like:

try
{
//Shit code that will throw an exceptions more than Hillary's tantrums about the elections
}
catch (ExceptionType ex) when (ex.ErrorCode = "0x696666")
{
//Log this fuck up
}
catch (Exception ex)
{
//More logs
}
finally
{
//Run code that doesn't depend on the successful execution of prev code
}

I love C# and use it every single day, but this "When" keyword in Try...Catch...Finally blocks is new to me and will be interesting to start using it now :)

No one fucking knows how to handle/raise errors.

I feel like this is the least talked topic in all fucking programming industry. This shit needs to be tought even more than the fucking SOLID, DRY, KISS, YAGNI and other kinds of buzzwords that fancy devs love tossing left and right.

Basically everyone just does "whatever you dumb error just dont bother me". They will just log/return null/ignore the errors and be in their oblivion with bugs propagating upstream the call stack.

"Throwing errors you say? Ew, why do you want to produce more errors?". Yeah, right, just stick another log/return null/or ignore the fact that the monke calling your function with bullshit arguments.

"But bro it's so difficult and time consuming and it would never happen!" Yes, you fucker! Yes! Programming IS fucking difficult if you want reliable systems! Did you not know that!? Well now you do! Go and fucking learn it!

FUCK!11!1!!

Is it only me who gets screwed up by such silly little things?
Last night I was working on an Android app. I connect it to a URL. It always threw exception. I scratched my head for one whole hour to find out that Cellular Data was not turned ON on the emulator. 😛

When you want to filter Android studio by exceptions for your app and the exceptions that pop-up are from another app lol, in this case SoundCloud.

Worst. 2 am on campus, js file for a web app project. It didn't work, no exceptions thrown, no errors. I call the assistant teacher. He calls the teacher. Teacher calls the head of department. Four of us staring at the screen for an hour, trying different browsers, environments etc
3 am, switch cases had semicolons rather than colons. Sleepy coding is the worst.

Me: develops my first android app with firebase by google.
Me: finishes app, tests it and it works.

Firebase after 3 months: we were first going to scale our servers on our own based on how many people are simultaneously using your app. But now fuck you, we will have a cap of 100000 simultaneous users.

Me: fuck this kills my app if it scales. Have to Shard everything on the db side and overhaul the entire app to work will multiple db instances. Takes a month.

Android after 6 months: dude your app is working fine without any hiccups. Let me fuck it up. We will stop all your services when your app is not running or backgrounded. Also we will make it illegal to start services in this case and we will throw exceptions.

Me: what the actual fuck. They now want me to focus on a JobScheduler, fine... But now even intent services won't work properly. So use a job scheduler to start a JobIntentService which is essentially another job scheduler for queuing. wtf android.

Ps solved it and works again.

PS: WAITING FOR ANDROID TO FML WITH ANOTHER NEW VERSION. Maybe they'll say you can't run your app at all now

I hired 2 fresh out of school junior devs to work with me on my old web app.
They were brilliant, knew a lot of things, and were motivated.
They started complaining about how the code was shit, the db was shit, there were no best practices, the technology was old, bug fixing was boring, no comments in code.

I felt bad, very bad during 3 years, because they were absolutely right. I tried to work with them through better coding practices, rewriting, documenting etc.

Now they both have left.
I'm alone maintaining and evolving the application.
And I start to come across the code THEY developed.

What a bunch of shit. SQL queries bringing down the server. Duplicate code, because they didn't want even read the old one. Useless comments.
Performance killing functions. Exceptions swallowed without mercy. I have to clean up they poop.

I feel somewhat better, though. The application is still growing and holding the ground after many years and generating at least 800K$ per year in revenues.

Maybe better, but sad. I really wanted to share the project with somebody else but I failed, and I'm left alone....

Inmates are trying to take over the asylum again.

Got a message from the web team manager deeply concerned because since switching to the new logging framework, the site is significantly slower.

She provided no proof or any data to what 'significantly slower' means.

#1 The 'new logging' has been in place and logging for 5 years. We only recently depreciated the ILogger interface ('new' ILogger interface only has 1 method instead of 5)
#2 The 'old logging' was modified 5 years ago, so even if you were using the 'old' interface, the underlying implementation is still the same.

She tried to push the 'it wasn't this slow before' argument, so I decided to do some fact based analysis.
Knowing they deployed their logging changes couple of weeks ago, I opened up AppDynamics, looked at the average call time to Splunk (along with a few other http calls they are doing)
- caching services - 5ms
- splunk - 30ms
- Order Service - 350ms
- Product Data Service -525ms

Then I look at the data they are logging, for the month of June, over 5 million messages. At 30ms each, that's almost 42 hours spent logging errors...yes errors. Null reference exceptions, Argument exceptions, easily fixable stuff.

So far for the month of July (using the 'new' logging), almost 2.5 million errors. Pretty close so far with June's numbers.

My only suggestion was to fix the bugs in their code so they don't log so many errors.

Her response.."Can we have one of our developers review your logging code? We believe we can find ways to optimize the http requests"

Oh good Lord. I'm not a drinking man..but ...I might start.

cssRant

Why for the sake of world peace can't Edge inherit "opacity" to children?
This drives me insane!!!11!!one!eleven!!1!!

Get you fucking turds together dear browser developers!

The whole webDev business gets serious crippling depression from your brainless way of pooping out what you call "browser"!

In PHP (yes, it's a language I... don't hate) I've always hated exceptions. They're like GOTO, in an OOP world with interfaces and contracts, try/catch is really odd as it breaks a promise about returning with a typed value.

But you can now do this in PHP8, which comes pretty close to Maybe/Either monads (Option, Result whatever it's called in other languages):

function getUser(): User | UserNotFound

PHP8 unions don't come with the same strong guarantees as in other languages but *pets PHP gently on the head* you did well, my boy.

Now I would really love it if PHP9 could do:

function getUsers(): Collection<User>

Type Tree<T> = Null | Node<T>;
function 🎄(): Tree<Branch<Ornament|Light|null>>

Porting Java Code to Kotlin manually, just to get a better understanding of the language. Best thing so far, NO more Assertive Exception Handling.

Damnit Java, I know it for a fact that the damned thing won't throw an exception! There's Careful and Paranoid. KNOW THE DIFFERENCE

The best software license ever seen :

my patches and additions on top of Ian's code are licensed under the ABSE ("Anyone But Stefan Esser") license.
note that an additional exception to the license is added, forbidding use/redistribution of said content to his
trainees as well, but only when in a 5 mile radius from "Stefan Esser" or while holding any sort of (video)conference/chat with him.

note that this license will only be used as long as what would capstone decode / that one other arm64 ida
plugin thing by i0n1c ("Stefan Esser") are not under the MIT license.
afterwards, all exceptions are cleared and basically WTFPL applies

if you need a copy of the rest of the license feel free to google it or something.

"Never write a single line code for anyone for free"
(Open source projects are exceptions) 😜

Fuck uninspired jr devs that are simply collecting a pay check.

I have been handed a project that a jr dev was allowed to wallow on for over two fucking years. This lazy mother fucker managed to create 5 functions, a whole fucking mess of bullshit that I now have to straighten out on top of the 8 other things that I have to deliver on in the next month.

They never followed requirements. Not-a-one. The API is fully broken. The DB schema is BEYOND fucked. There's ZERO validation/sanitation on I/O. The deployments only work half the fucking time. Their code is so spaghetti I'm getting triggered from when I worked at Olive Garden with Eminem. But hey, at least they were able to demo it to the client to say "it works".

I don't condone violence, but every time I find malformed if statements, linter exceptions, broken deploy configurations in this project -- I just want to kick them in their stupid fucking face.

Wherever you ended up you piece of shit, I hope your dreams of becoming a rich asshole only bring you unending despair. I believe you can make it though, because you're already halfway there.

Fuuuuck this corporate bullshit. I'm basically sitting around twiddling my thumbs waiting for some jackass to grant me access to the server that my boss moved my code over to. Why the hell did you put my app on a production server that runs every 30 minutes...THAT I DON'T HAVE ACCESS TO?? Now there's a critical bug and a $50K order in limbo because I can't push any fixes. Fuck me. The worst part will be in the next hour or so when dozens of people are calling, emailing, and attacking my cubicle like rabid animals about why orders aren't moving and I'll have to explain that production is a train wreck because reasons. Just end me.

The last software I worked on in my previous company (a few months back), was a temporary replacement because they were switching techs. It was meant to be replaced within 2 years.

So, before I left, I added a kill. 2 years and 2 months into the future. First it spams the devs with emails "how is the tech upgrade going?" with no further clues. 6 months later it will start throwing random exceptions at random intervals. 6 months after that it just terminates the application immediately upon startup. Snuck it in between large commits, and since they stopped code reviews when I left, doubt they found it.

There is a setting in configuration with an obscure name to disable it all.

I marked the dates in my calendar. Would love to be a fly on the wall then.

try {
// something
} catch (SomeException e) {
}

Swallowed Exception.. what the fuck is wrong with you?! And I see this shit in a lot of places in the code!

My only nemesis are sales people.
* They try to sell the impossible to the customer.
* They think even the biggest change takes only some minutes to implement, and tests do not even exist.
* They promise to deliver an app within half the time which means we have to cut out animations or some tests to deliver when due.
* They often get a commission (sometimes not as part of profit but revenue!) for calling their pals and asking them if they wanna buy something new (some say they also take the risk, but they don't, the company does).

There may be exceptions, but my perceived ratio between good and bad sales is about 1/20.
Now I am in a very small company with only one sales guy. Guess what, he is a good one! I hope he stays forever.

1. Learn to read and understand the errors and exception messages. While writing code you're going to be facing exceptions most of the time and the real cause of them is under a lot of generic error messages. That and a lot of patience and perseverance.

2. You're going to face clients and bosses that ask you to do a temporary "workaround" even though you know there is a best way to solve a problem even if it takes more time and effort. Don't "crash" against their ideas, try to find a mid-term between the fast and easy work around and the best solution and leave it open to improve it in the future. I have met a lot of developers that let the frustration stops them to be creative just because the approved development is not what they wanted to do.

While building a Java net sniffer app, I finally write the code to run a Linux binary in a separate process after three days. It works perfectly!

Then I export my app to a runnable jar file.

About nine exceptions are thrown, including a security exception. So much for being done. 😐

Trying to discover why the DB listener wasn't being called in my app for like 30min. Many log messages, no exceptions or errors, DB rules revised, DB content revised, changed constructors, simplified code and nothing worked... problem: the phone's wifi was disconnected.

So it's 23h30 last night and I've turned on the projector to watch the last episode of Mr Robot.
As I start the episode, I receive an email on my phone telling me that some important Azure webjob is throwing exceptions...
Fuuuuuuuuckkkkkkkkk
1 hour later it was fixed, and I watched my episode. Win!

I know I was one at some point, but juniors can be so frustrating at times.

After some pairing for a while they're quick to adopt the "Dev" mindset and think as far as they need to...

... but with this latest batch... that day couldn't come sooner 🫠

Having to explain how exceptions work again is the last thing you wanna do under tight time constraints 🙃

When a small part of your company still uses production Cobol and VB6. 💀

Still dealing with the web department and their finger pointing after several thousand errors logged.

SeniorWebDev: “Looks like there were 250 database timeout errors at 11:02AM. DBAs might want to take a look.”

I look at the actual exceptions being logged (bulk of the over 1,600 logged errors)..

“Object reference not set to an instance of an object.”

Then I looked the email timestamp…11:00AM. We received the email notification *before* the database timeout errors occurred.

I gather some facts…when the exceptions started, when they ended, and used the stack trace to find the code not checking for null (maybe 10 minutes of junior dev detective work). Send the data to the ‘powers that be’ and carried on with my daily tasks.
I attached what I found (not the actual code, it was changed to protect the innocent)
Couple of hours later another WebDev replied…

WebDev: “These errors look like a database connectivity issue between the web site and the saleitem data service. Appears the logging framework doesn’t allow us to log any information about the database connection.”

FRACK!!...that Fracking lying piece of frack! Our team is responsible for the logging framework. I was typing up my response (having to calm down) then about a minute later the head DBA replies …

DBA: “Do you have any evidence of this? Our logs show no connectivity issues. The logging framework does have the ability to log an extensive amount of data regarding the database transaction. Database name, server, login, command text, and parameter values. Everything we need to troubleshoot. This is the link to the documentation …. If you implement the one line of code to gather the data, it will go a long way in helping us debug performance and connectivity issue. Thank you.”

DBA sends me a skype message “You’re welcome :)”

Ahh..nice to see someone else fed up with their lying bull...stuff.

People talk about how they would love to switch to Linux, but cannot, as they claim that gaming lives on Windows. This may have been the case ten years ago but it isn't now.

And further, Microsoft is working hard to break steam, humble, gog, and any other delivery systems they do not control. Such anti-consumer behavior should not be tolerated, let alone rewarded. One result of this is that almost every indie game that comes out now has native Linux support within months, if not on day 1.

The only weak spot is AAA games. But as AAA games and mobile games begin to converge, in terms of the subscription/microtransaction models they're both moving toward, with very few exceptions, I personally don't think I'm really missing anything when I see a Windows-only game for $60 with no Linux support.

And if I really want, I can play un-wine-able Windows games through parsec, though that's getting rarer and rarer all the time.

Give them free tech support.

Fuck sake, so my bank has been migrating/rolling out new IT system and app/site have been broken for about a week (others noted evidence of devs debugging in production)

Assuming I don't lose my money as some mischievous assholes will inevitably exploit the fuck up, and rob the bank, I will be moving my funds to a different bank...

In mean time I'm trying to prepare for uni, and they're making a ton of semi-random changes in addition to rolling out a site with course details and info along those line, and good fucking god is it bad.

Is is slow as fuck? Check. Does it use never-seen-before naming for standard things? Check! Is the UI pulled from late 90's? YOOU BETCHA! Are the pages bloated with unnecessary content? Fuck yeah! Do I get SQL exceptions when I finally locate my course? Of course I do. Does clicking "back" take me back to the landing page instead of previous page, when I'm several steps deep? .....

I could keep going, but don't feel like ranting and feel more like punching someone in the throat.repeatedly.

11.1/11.4 GB of RAM is being eaten open on boot, even though I just rebooted. Almost half of my swap is in use too. WTF! Windows is no help in explaining it either...SO ANNOYING!

Exceptions are always there in any society.
A good society is the one that treats them well.

Roses are red
Exceptions are blue
Empty catch blocks are going to hurt you!

try
{ somethingVeryDangerous() }
catch { // No Op
}
finally { SaveFile() }

GodDAMN, C# 7.0 is so ridiculously feature packed. I can pattern-match inside a predicate on an exception filter. Want to catch ONLY NHibernate's exceptions caused by a SQL timeout? Boom:

catch (GenericADOException adoEx) when (adoEx.InnerException is SqlException sqlEx && sqlEx.Number == -2) { return Failure("timeout"); }

-Discovers new tech
-Follows the "getting started" page
-Spends hours to get the example project working
-Gets bunch of exceptions
-Cries

Another 404... Anyone know how to send data to localhost?

Real developers throw inceptions

Read code, exceptions, comments carefully. Double think before asking. But never hasitate to ask if you are stuck.

I really like this book on the basis of the philosophy overall, no this doesn’t solve all problems but it’s a good baseline of “guidelines/rules” to program by. Good metrics or goals to architect and design software projects high and low level projects.

Fight Software Rot
Avoid duplicate code
Write Flexible, dynamic, adaptable code
Not cargo cult programming and programming by coincidence.
Make robust code, contracts/asserts/exceptions
Test, Test, and TEST again and Continue testing.. this is a big one.. not so much meaning TDD.. but just testing in general never stop trying to break your software.. FIND the bugs.. you should want to find your bugs. Even after releasing code the field continue testing.

Finding the right balance between well written, need-one-week, maintainable software, and fast-written, ready-in-2-hours-and-never-look-at-it-again software.

Last time it took me 20 minutes to integrate with a new API. I had a script that did everything you needed. I then spent 2 weeks on handling error responses, unexpected responses, exceptions, intelligent retries, logging, unit tests, integration tests, caching, documentation, etc.

Does anybody else think the new expressions are nice and all, but most of them are not really made for those small avatars we have?

most often it looks like the person is about to ask me about how they got their scars or they are making fun of asian eyes while laughing about it

it looks great once you zoom in on the profile, but on the smaller size version it just looks odd

there is some exceptions that actually look great on the small avatars too, but most of them don't

Rant much...
I just started working on project after a group of students.
The project has various of bugs (ofcourse) and not catched exceptions.
I found variables like 'abcd' or shorts of classes like 'rrms'.
I would be fine with all of that but there is one thing is just making me crazy:
THERE IS NO SINGLE FUCKING COMMENT IN WHOLE SOLUTION (three projects and about few hundred files with javascript and cs).

Imagine freaking pure react (no jsx) full of null arguments and multiple custom control written like 'var gl= GreenLabelled(null,null,text,5)' (a button ) with again, NO FUNCKING SINGLE COMMENT.

I just cannot stand it. Just spent 3hrs to wrapp my head around events in this react classes...

Devrant !! A platform for frustrated devs ranting about their runtime exceptions which only devs can decompile ... Cool

Web development is the worst!
I still cannot understand why it is not possible for browsers to correctly support all official specs... Exceptions here and there, dirty fix for this one, add a little margin here, hide this...
The daily struggle never stops.
Don't even get me startet with PHP!
Next round is on me ;)

The best thing about perl is it doesn't care about errors and really tries to do what you ask, without throwing exceptions.
The worst? It does exactly what you ask, no matter how insane.
Typed $arri[ $0 ] instead of $arr[0] inside a function that detected what changes were needed in dns zones. $0 is script name and path, strings are converted to integers as needed and there's a little thing called vivification.
You see where this train wreck is going.
Also my dog died today.
Got to love Mondays :/

Is it so hard to comment your code?

I work on collab projects here and there and both the comments and documentation are both awful, nearly always, there are some exceptions.

This is a plea to all those who teach anyone to program. "This performs a loop" is not a helpful comment, nor is "This sets variable x to 1" where the line below is "let x = 1".

The last piece of code brings me on to my next point meaningful variable names. If x is a variable that stores the age of a machine call it ageOfMachine or age_of_machine. Not aom, not x but what it actually is, modern IDEs and text editors will fill this out for you.

Finally documentation, a good friend of mine sent me this quote a while back, I can't find the image but "Documentation is like sex, when it's good, it's great. But when it's bad it's better than nothing." Your documentation should be good, a good pattern to follow is the Node.js documentation, it tells the function, what it does and what parameters it takes.

Anyway rant over; and I'm sure that this applies to people outside of this community only.

DevDuck is so ducking incompetent. Just stares at me while I'm shouting at it. 🦆😭🙃

Correct me if I'm wrong, Python is absolutely built on:
--Data encapsulation
--Dependency Hell
-- ambiguous object types
-- You BETTER hope that package has a function to turn that object into another HOPEFULLY SUPPORTED object (basically even more encapsulation)
--Oops this package doesn't support this other package, so you need to do another 20 lines of conversion
I really don't understand what makes Python so likable?? Am I just being stupid, or does exceptions like "This does not support multiclass" the worst fucking exception i've ever seen? Or "Shape (None,1) not compatible with (None,7)"? I get it that you can fix it if you've seen this issues multiple 100s of times, but for the first time, how the fuck am I supposed to debug this?

Okay...not a rant. But my boss's boss is amazing! I've been with this company for about a year, and every time my lowly ass needs permission elevation to do something, I have to practically beg. And then I get elevated one little permission at a time. I have a presentation to the board on Tuesday, and all damn day it's been one network permission problem over the other. It's become insulting that I'm the only team member that has to beg for permission scraps. Today, they take me out to lunch and when I get back, sends an email and copies me on it basically instructing that I'm to receive near-God like permissions on the network. Quite an honor for being everyone's junior by like 20-25 years! I feel like I'm about to receive an Infinity Stone or something...best day ever!

Took me a year after graduation to land a job that stuck. Submitted about 100 job applications, most of which were immediate or semi-immediate denials. Got through one screen call and one technical call with Google before getting passed on. I did two technicals with G.E. where I really thought I knew my stuff...but didn't make the cut. I finally landed a job with a contractor for the Department of Defense, but my clearance was going to take over a year to finish, so they let me go after a couple weeks.

Every day, I would sit at Starbucks for eight hours; four of which, I would apply for jobs and practice for interviews. The other four I would self-medicate on Steam and wonder if the last six years of schooling was worth it. I was ready to move out of state and/or cut my losses to find a new industry when I was blessed with my current job.

For anyone going through what I did, don't jump straight to doubting your skills. Breaking in to an industry can be very hard. Have patience, keep getting better at what you do, and be open to opportunities. 💯👍

I’ve said it before and I’ll say it again.

If you live in a major city and you stand on the slow fast side of the escalator (could be left or right based on location)...

then you deserve to be punched in the back of the neck.

No exceptions.

I JUST SPENT A PAINFUL TWO HOURS TRYING TO FIND OUR WHY MY EXCEPTIONS WERE BEING THROWN AFTER EVERY SINGLE INPUT THE USER ENTERED...

I commented out the try catch, it worked, I commented out the throw and it worked, so I uncommented them both and it worked again? WHY DIDN'T IT WORK BEFORE Y U DO DIS

We receive an email from Splunk when errors go above a certain threshold, and a particular service has been especially problematic this week (throwing hundreds of exceptions). Email response from the team mgr responsible for the service.

"We are working to address these errors. We don’t currently have a way to prevent a user who’s account is locked from logging into the service and performing work."

The exception? NullReferenceException: Object reference not set to an instance of an object.

The code? (paraphrasing)

var user = GetUser(request.Login);
if (user.CanPerformWork) ...

<facepalm>

I'm doing my best not to reply .."Really? No way? You do realize we can read code, right?"

The try, catch block kills 50 percent more exceptions than the Infinity Gauntlet

Some kid keeps asking me how to session hijack. I keep telling him there's no point if:
A. You're not on the same network as him / her (I'm sure there are exceptions to this but normally you'd have to be on the same network)
B. The connection is encrypted
He doesn't understand either of those things. Not to mention it's illegal unless you're given consent.

Fucking finally

Okay, well, fuck you! Why would I wait 30 minutes? I'll just buy from Amazon, shithead.

If an http request can't perform the requested operation, should server send 500 error code? Or 200 with status and status message in response?

Isn't 500 used only for unhandled exceptions on server side?

Heard Java 7 provides catching multiple exceptions in single catch block ! hmm .. why need when I got this 😎😁
try {
// do something...
} catch (Exception e){
//log it ..
}

When you're in a rush to write a new feature but your compiler keeps nagging about not handling exceptions

Not being able to directly read in inputs as any data type rather than string and thus having to convert it and check for Exceptions if users enter bullshit

I explained last week in great detail to a new team member of a dev team (yeah hire or fire part 2) why it is an extremely bad idea to do proactive error handling somewhere down in the stack...

Example
Controller -> Business/Application Logic -> Infrastructure Layer

(shortened)

Now in the infrastructure layer we have a cache that caches an http rest call to another service.

One should not implement retry or some other proactive error handling down in the cache / infra stack, instead propagate the error to the upper layer(s) like application / business logic.
Let them decide what's the course of action, so ...
1) no error is swallowed
2) no unintended side effects like latency spikes / hickups due to retries or similar techniques happens
3) one can actually understand what the services do - behaviour should either be configured explicitly or passed down as a programmed choice from the upper layer... Not randomly implemented in some services.

The explanation was long and I thought ... Well let's call the recruit like the Gremlin he is... Gizmo got the message.

Today Gizmo presented a new solution.

The solution was to log and swallow all exceptions and just return null everywhere.

Yay... Gizmo. You won the Oscar for bad choices TM.

Thx for not asking whether that brain fart made any sense and wasting 5 days with implementing the worst of it all.

Dear other developers,

Don't throw exceptions in async callbacks goddammit. It doesn't abort the outer function where you think it does, and it crashes the app because you can't catch it.

Corporations... huge, old, monolithic
We want you to automate but will do everything we can to prevent you from getting resources to do it. Restricting policies, decisions by managers on "what they do not want". No procedures on how to achieve the result within policies. Half the business lives in a gray zone and sea of policy exceptions.
We finally decided to get at least Azure subscription instead of trying to develop similar framework internally, but wE DoNT WANt YOu to dEPlOY thERE As WE Don't cOnSIDEr it sAfE ENough.
Like pissing against wind.

Reverse engineering an applications internal object model and creating an database model for it...

The reason: Several versions of application exist, each deliver flat data by rest. The data is a complete potpourri of several different entities. *yaaaay*

Eg. an example fictional call (real call and data would get me in trouble I think....)

get_fiscal_report returning the fiscal data for _several_ companies, the companies _subsidiaries_ and the respective _segments_ for a _year_ with a key value enumeration.

So it's an happy fuck up of N:N associative data that usually would be a hierarchical relationship...

Year - Company
Each Company has subsidiaries
Each Company subsidiary has segments
Each segment has a fixed enumeration of keys
Each key has then the monetary value (e.g. 'operating_income' - 155_000 US-$)

Example is made up, but my data contains exactly such a lovely nested hierarchical data flattened and misnamed to a point where it's close to garbage.

Yaaaay.

I had now 6 days of untucking this mess to a usable database representation...

Sprinkling Unique Keys everywhere...

Running persist script...

Getting exceptions...

Changing associations...

Running persist script...

Screaming.

Changing associations...

Violently cursing.

Running persist script.

Starting sacrificing interns...

6 days.

I need a new brain and a format of my soul.

-.-

Reverse engineering proprietary software is really an morbid adventure.

Slant.co is either homophobic or hacked (bottom-right)...

Lua is one of the stupidest languages to ever exist.

Oh, the language is easy to learn? The syntax is friendly? There's only like negative 10 functions you ever need to know? Everything is a table?

EVERYTHING IS A TABLE?! WTF CARES? WHAT ABOUT NIL?!

The arrogance this language has is extraordinary, literally. No lang, except Lua, imposes such an opinionated dichotomy. Everything is a fucking table, or, it's nil. -- That's so fucking stupid.

And look, I get it, this lang (oh sorry, scripting language (?)) CAN be good and fun and whatever... the moment you start to do IO is the literal end of days.

Everything is nil. Except, if it's defined... then it's not nil. -- OK. That sounds sensible/reasonable enough. -- What if it's not defined? You get nil. What if it's not the right data? You get nil. Do I get errors/exceptions or whatever? No, absolutely not, you get nil... unless the application you're using with Lua with has a lib that handles that.

There are so many more issues I have with this lang, but honestly... Am I fucking missing something? Is this lang like actually super dooper awesome and I'm missing something? -- I can't not look at this language as just dumb and arrogant. -- It's literally a language where you have to manage and remember ALL conceivable state at ALL times.

Not a rant but I spent 30 minutes writing a fix for 2 integration tests while screen sharing. Ran the tests and they both pass first try, no exceptions, typos or silly mistakes. 2 additional unrelated tests also started passing. It felt good.

When Java exceptions mean nothing

Cinemark's recommendation system could use some tweaking, lol.

That's it. From now on I won't pay a penny for the game if it has no Linux port. No exceptions.

Can't help but when watch most profiles(some exceptions)of ranters I see are front end developers. Aren't here some guys who work on developing frameworks, work on linux kernels or maybe work on linux distros?

P.S.: I love RoR and will contribute to make it better. So the image.

All classes (with a few exceptions) have nothing but static methods just so that I can call them like "Class::Method()" from anywhere in the project...

My boss is the CEO of the company, it's a small company with less than 15 people altogether. Now in the office it's even less there's 7 of us every day, the rest are remote or the boss.

The boss last week Thursday night sent an email talking about vacations, keep in mind she's currently on her third vacation in 6 months.

In the email she says no one but 'special' exceptions will be allowed to take summer vacations from now on, and if you would like to take your vacation you have to give a minimum of 4 months prior notice

Now I personally don't take vacations, (never needed to, no job before this was stressful enough to make me want to take one) but everyone else in the office is working on their resume's and planning to quit before the new year.

apparently being overworked and thrown under the bus time and time again, as well as an abhorrent number of other issues isn't enough to make people quit . but take away their vacations in the most hypocritical way possible and that's the straw that breaks the camels back.

I finally got a car, I've been practicing driving, and hopefully before September I'll have my license and that'll make it easy for me to get out too before things start collapsing too fast.

My plan/resolutions for 2018?

Have at least 1 commit per day w/ maybe exceptions like special holidays and such 😁
(No commits just to have a commit like adding a line of commentary or stuff like that)

#iwannabetheguyshetellsyounottoworryabout

Encapsulate tasks
To abstract your case,
Full of the catharsis
And exceptions to face.

Didn't commit, oh wait,
More trouble? One reset.
We return and all hail
This programming mindset!

A dev found a bug I created where I set a SQL parameter name to @OrderID instead of the expected @Order. The standard is @OrderID, there is one stored proc where it's @Order.
Oops...I didn't catch it because the integration test didn't cover that area of the code. My mistake...I should have checked...I take complete responsibility for the screw up.

He let me know by email..
"When refactoring, from now on check the stored procedure parameters, there are a few that don't follow the standard."

I was like "from now on..."? ...wow....bold comment from someone responsible for code that doesn't check for nulls, doesn't log errors, and relies on exceptions for flow control. You wouldn't even have known about the error if I didn't modify your code to log the error (the try..except returned false)

I really wanted to reply ...

"Fixed. From now on, when you come across those easily found bugs, go head and fix it, write a test, and move on. Don't send a condescending email to me, my boss, your boss, all the DBAs, and the entire fracking order processing team. Thanks."

But..I thanked him for finding and letting me know...we're a team..blah blah blah..

Frack..people suck.

Architect: I've been using this architecture for 20 years now and this works nice since pascal, that's why we are using it in this J2EE app.

This was the justification that I received after hearing that I shouldn't use exceptions, just make the function return a false and add the error message to a embedded message list and make the caller capture it.

Should have kept a copy of my best code off of my work computer. That way it wouldn't have been confiscated along with the computer during the layoffs. [sniff] I had some beautiful Stored Procedures I can't satisfactorily remember how to reproduce. 😅

So I just had a bit of a shower thought. Suppose you could get the linguists to break a language down and define all the rules that make up that language as if it were a protocol - exceptions included. If you get an arbitrary string of text, could you match against those rules, then break that down to the information it contains, and use that information against a new rule set to construct a new valid sentence containing the same information. Would you just have made the ultimate translator?

Helpdesk: We can't figure out our own ambigious error message, you should solve it in another way...

Me: I see in the console that I get an execption response with an ID, you must be logging these exceptions, can't you check those?

Me thinking: you've just reduced yourself to desk without the help part

I don't work for Walmart, but they almost put my job in jeopardy today. I have a console app in production that pushes Walmart orders from their marketplace into our system for fulfillment. For half a year, I have handled thousands of orders, but overnight, all customers were getting massive price cuts on products in the Walmart feed! I looked at the data and initially thought it was my error due to using a quotient instead of a product in the code. But upon closer inspection, some fool at Walmart had changed code on their end without telling my team! Broke all the things. Lucky we were able to pull a full stop before we lost disgusting amounts of money, but you would think that a big player like Wally would at least announce a breaking code change to their users. 😲😡

What's your opinion on the error-value vs try-catch debate?

I'm usually on the error-value side of things.
Its the preferred error-handling in Go and the pretty much only decent solution in C.
Also, frequently thrown exceptions seem to impose a larger overhead than the constant checking of the error-value.

Who the hell invented this industry where smartest individuals are being evaluated by those who didn't understood technology well enough and moved to management (it's usual scenario, though there are exceptions)?

Can you imagine surgeon performance/quality being evaluated by some clerk who may or may not had studied medicine earlier, but wasn't good enough to become surgeon itself so ended up in hospital administration.

Or can you imagine bridge engineer having his/her performance/quality evaluated by someone who had built bicycle shed 5 years ago?

Damn, yet in software industry it's pretty normal.

(Don't confuse management with performance evaluation. I know management have different scope and duties, but idea that management does the performance evaluation is so damn broken.)

Spent hours troubleshooting an internal app that had zero logging today. It would just terminate, no exceptions, no feedback to the debugger, NOTHING.

Turned out to be the damn corporate virus scanner blocking "malicious" behaviour. Good thing my desk is so heavy or I woulda flipped it...

30 mins before:
Started a project on Xamarin, faced Unhandled exceptions while navigating.
Reaction : Xamarin Sucks :/

Turs out, I forgot to initialize the Navigation Stack 😂

Reaction: Xamarin Rocks 😂😂

A few years ago, i had a task to implement a webservice of an insurance-company into our .NET Development.

The security requirements of this insurance-company webservice were top notch.
As a client you had to build a request that used a negotiated certificate, canonical header structures, security timestamp, a secret token in header, ...

To configure all this stuff via web.config WCF was pure pain in the ass.

After many phonecalls and emails, i finally managed to meet all security requirements to send a valid request.

First, i didn't recognized my breakthrough, because my client still had thrown exceptions while calling the insurance-webservice.

Why was that?

The exception told me on the most possible gentle way, that .Net isn't able to process an unsecured response, when there was a secured request before.

So there was top notch security for requesting, but dumbass unsecured responding with all the precious customer information.

*epicfacepalmnuclearexplosionfollowing*

I even had to raise the. Net Version of our. Net client, because i wasn't able to configure that it is allowed to process an unsecured response after using a secured request.

Whyyyyyyy?!!?!!1el even!?!

The ability to start my projects and finish them.

Like for real I have a bazillion ideas yet none was even started, and the few exceptions that were started are unfinished...

The guy who wrote a ton of legacy code at my company apparently had no idea that you need to close a file stream. And also that IO may throw exceptions.

Wooo

Participating in a non-profit project related to corona outbreak. It should help thousands of people to say at home, have a peace of mind and stay healthy.

Our project should go Live this/next week and we already have a blessing from our government. They are already making some legal exceptions to us.

That feels good!

Unity's "quirk" messed me up again. This time, I wanted the time when the key was pressed as precisely as possible, independent of the framerate.
So I put the input reading routine into the thread pool, which causes the first few readings to throw null reference exceptions. No biggie; the system needs a few moments to warm up. So, I try-catch that part.

But when I build the game, as soon as I reach the part where the game tries to read the input value, it hard-crashes before try-catch can act 🤦

I'm just frustrated. I wanted a simple, statically-typed language that doesn't get in your way and offers GC. I can't find anything "just perfect".

- Go: enforces a style on you, nono.
- Rust: ownership system. I love it, but it's too low level for what I want.
- Scala: seems to have a bunch of useless and bug-prone features.
- Java: I hate how you have to declare and catch exceptions. Good practice, yes, but the code gets bloated with try-catch statements.
- C and C++: Too low level, no GC.
- C#: maybe? idk

I want to make a back-end for an app but I want it to be easy and fast. I need something with a gentle learning curve, not keep fighting the language. I'm between Java and Rust. Java's easier to use. Rust is rust <3, but it's hard, I haven't learned it properly and I just keep fighting the fucking compiler.

I'm so tired of being on the second floor of this shitty office building. There is a constant vibration from all the employees walking around; moreover, someone walks down the aisle beside my cube...it's like a small fucking earthquake. A group or really fat person walks by? Shit's falling off my walls. Damn it all. 👊

typeof rant === "Encouragement"

Never let your self down, try to be your own const in life that know his scope and traits well enough to construct a peacefull life without any uncatched exceptions. Also try to return something to the public, keeping your magic pointers to your private makes it hard to review your glorious source of thoughts. And if it is getting hard try to REST a bit and git some timeout.

😉

Happy Thanksgiving, DevRanters! Gobble 'til ya wobble...

Auto tuning for Azure SQL databases is cool but :
DON’T allow it to automatically drop indexes ! (My bad, I should’ve tested that before)
It dropped one of the most used indexes in the DB. Yep, just like that. 150+ timeout exceptions and customers going crazy

Project requirements include a database. I don't have permissions to create a new database on the server, so I go to the person that spins up new servers and deals with group policy. They rustle some papers around, looking aggravated, throws up hands and says, "I guess I'm the DBA now..." Well, what the fuck am I supposed to do shithead? Ask the web team to do it? We don't have a DBA. My boss has been gone all week and, really, this isn't a hard task. You check a fucking box.

Whatever, I'll remember this when they need a favor from me.

For the PHP pros: Is there a way of turning notices and warnings into exceptions thrown in the scope of occurence without hacking the interpreter?

The answer most likely is "No!" - but if there is another way i certainly would like to know it...

Fuck the design guidelines that change every fucking day. It makes Front-End an unbearable hell. I'm seriously tired of having to code stupid shit for exceptions exceptions exceptions.

Logging literally everything from every service into one giant super log db for us to sift through.

It is expensive, it is stupid, and it is set to .info() level always forever no exceptions.

Wow. This piece of bullshit runs completely flawlessly in the debugger, but throws exceptions like fuck when running it normally. How am I even supposed to find that fucker of a bug?

After working with a bunch of people it occurred to me that almost anyone can work and learn for most IT positions. This is something that most people will realize, especially if they work with newbies that learn on the go. There are exceptions of course, but most companies are just making crud apps with their business logic.

What I wonder then is, why is it that the way hiring is done seems to be completely against this idea? Rather than whining about recruiters and bad interviews, I am curious about why this is so common. What is it that a lot of companies think or see that make their hiring process so bad or convoluted?

I really fucking hate adding Exceptions into code. It's so fucking ugly and I feel miserable sometimes by using because I have to. I'm weird.

Ive been working on pseudo-Java (ie some 3rd company's UNDOCUMENTED programming language) that they parse into Java in their backend

It doesnt even support if-else (only ifs and elses) or a boolean combination of False and OR together lmao

mainly a GRPC middleware-language

Given its lack of features (arrays/collections) or documentation, I just had to implement a flag-array using a 0-1 string

Im throwing exceptions unless combined strings equal Lengths and is only 1s

living like in 80s-90s 💀

Today I spent half an hour trying to figure out why my IDE stops on an exception that is very obviously caught.
I left a breakpoint there because the stack traces behaved weirdly.

Funny story...
Got a small college assignment based on Java and Cassandra(database). The database shell was running fine. Spent 5 days removing the random java exceptions and working on the basic connectivity, searched everywhere on Stack overflow and other forums for solutions and still no help.
So, I decided to write a program that would print only the output as I knew what would be the output when it will run. Took a screenshot of it and made up a cover story to tell my professor that I did it on a friend's computer.
But while I was taking a screenshot of the Eclipse with code window and output window, some random syntax errors popped up.(but they weren't syntax error).
So I created a new project and copied the pom.xml file and the code into the new one(I tried this one before and it didn't work). And there were no errors. So I took a screenshot of it with output of different file and opened a different file.

But then, don't know what came across my mind and I clicked on run just to see if this works, and it worked fine. And now I'm like.. WTF JUST HAPPENED!!

Rant

Wtf are you taking man?
You’re supposed to be an experienced engineer but what the fuck are you doing leaking null pointer exceptions everywhere you go?

Just 1 more month. Good thing my manager isn’t renewing your contract.

Fuck!!!!

Lady comes over to my cube and stands silently until I notice her in the mirror. She cheerfully asks that I help her reset her password.

Okay...one, I'm buried up to my balls in work that needs to be done, and here she is camping, expecting me to feel a disturbance in The Force to help on her whim, when our company has an issue system for shit like this. 👊

Two, I'm 👏 a 👏 developer 👏! My sign says Software Engineer on it, which might give some context as to why she forgot her password.

Look, I was nice to her. But it seems like I'm getting more and more phone calls and surprise visits lately from people that I shouldn't be.

A good friend connected me with a recruiter before I almost gave up looking for work in my industry. Good thing I didn't piss him off in college!

Rule 34...

Doing the deployment to production, and towards the end one of the support guys looks over at me;

"So, the website in prod is throwing some errors"

Followed by another guy:

"Yeah I'm getting the same, SQL exceptions on the page"

I stare at them panicked for a moment, when one of them goes "just kidding!". Like dude, my heart just skipped several beats!

Any one here ever had something cruel happen to them during a deployment?

What I really hate? When a piece of code simply refuses to work. No logs, no exceptions, no sign that it even exists. HOW THE FUCK I'M SUPPOSE TO DEBUG THIS SHIT?? I drives me crazy, if everything I do changes nothing! It makes me doubt my sanity. And I like my sanity!

My boss can't grasp why he should use exceptions instead of return codes in his code.

I just don't understand why people use the try-catch on calling a method that will throw exceptions just to ONLY re-throw it again, what would you do that for? :(

VirusTotal's API could do with a make over.

Though it is quite nice actually, you're able to provide them with a hash of a file and (provided they've scanned it) VT is able to tell you what up to 60 different virus scanners thinks about the file (and how many scanners that has an opinion about it). Now if there's an error, like the file not having been scanned or the hash being incomplete, it give you some JSON back where there will be an error message that tells you the error and an error code of 0.. wait wh

Although since it's an API they also need give us plebs whose only got access to an API key that limits us to 4 requests pr minutes. Naturally when you try to do another request within a minute of your limit the response you get is absolutely nothing what so ever. "" Naturally.

And of course the same response should be given when the API key you provide isn't valid. Who needs errors amiright?

No wonder JSON.parse kept throwing exceptions

I inherited some code today. I am in the process of reworking it to drop into my framework so I can use it with our product. I am seeing this throughout the code...

try:
\do something\
except:
pass

Ahem... HANDLE YOUR DAMN EXCEPTIONS!!! DON'T JUST PASS THEM INTO THE BLACK HOLE OF NOTHINGNESS! FFS!!! Using pass like this means "Fuck it. I don't care if this fails and I want NOTHING to tell management when it does. I want to blindly look into their frustrated eyes and say ..duhh, I don't know why it failed... Fuck troubleshooting. You know what, this job isn't meant for me anyways." My outer voice is politely saying "There is a better way to do this. Please allow me to show you." Meanwhile my inner voice is flipping tables and clubbing baby seals. /rant

Working with a SOAP endpoint. I know it is some .NET server due to the style of stacktrace on exceptions. Nice, a framework where I can expect some type safety granted by static types. I build some xsl to transform the SOAP wsdl files into classes and structs to interact with the endpoint. Works out perfectly.

Plottwist!

Elements which are defined in the xsd/wsdl with maxOccur=unbounded and minOccur=0 should represent a simple collection of this type. Therefore does my implementation expect a collection of this type. But no. The shipped SOAP client in my stack ignores the definition and simply deserializes the SOAP response into T and not a collection of T.

Where the duck are the types when they are defined all over the place?

From a dev and eCommerce management perspective, Groupon is THE WORST. They just launched a brand new marketplace site but STILL don’t have an API I can connect with to do fulfillment. Their CSV format is useless for our shipping company. Their data inputs are not sanitized and standardized enough to be predictable for purposes of transformation via scripting. The exceptions and edge cases are infinite. So I’m STILL stuck having to take time out of my day to manually copy and paste and correct order data into the proper format to FTP to the fulfillment company. Oh, and I don’t yet know if the new marketplace does this, but the old one used to suspend vendor accounts for...get this...selling TOO MUCH! How is Groupon still in business?

Even on the train station!!?? Freaking Windows!!!

I am done with .NET and it's bullshit error messages.

"Validation error happened! Please see Entity.Validation.Properties to see what the error is, then consult an oracle, who'll summon a demon who'll answer only three questions . . ."

FUCK OFF and just give me the error. I swear to god exceptions in NET always lead to some stupid fucking scavenger hunt rather than just letting me know what the fuck went wrong. This isn't the first time I've encountered this either, where it tells me there's an error and there's a mountain with a shaman at the top who'll provide me with the details if I can just hire a sherpa who'll help me climb it.

"Exception has been thrown by the target of an invocation"

This error message pisses me off. I know the SSIS Script component is capable of catching exceptions, you can wrap all your code in a try/catch (please don't) and get an exception. So would it be so hard that if the Script Component throws an exception that it tells me what it is instead of sending me on a goddamn scavenger hunt?

The whole bullshit system of errors is why I hate SSIS. Just tell me what went wrong.

I did what I wasn't supposed to do, wrapped it in a try catch and it gave me a stack trace and an error message and all sorts of actionable shit. But why the hell can't it just do that on its own?

There is literally nothing worse, except maybe Hitler, than a goddamn vague error message.

Who the hell designed the fucking Java exception system? The fucking checked/unchecked exceptions is a big piece of crap.

Makes everything more complicatedly unnecessarily

I needed to take today off to prep for a home repair. I didn't have much notice either, but I assumed my manager would be okay with some last minute PTO because of how relaxed everyone usually is around here. Guess that didn't include me.

I should have never assumed that my boss was someone I could think of as a peer. I called their boss "Boss" one time, and they said that they don't look at it that way, and that they see me as a peer. My boss nodded in agreement, but it was all formalities, and I bought right into it. Especially since both of them, even the other guys, take time off on a whim. But I'm somehow tied to a stricter standard, even though I can't beg hard enough to get so much as an email answered for legitimate reasons. They'll jump right on my ass when they feel I'm not working as hard as them, but I get silence most of the rest of the time. Bullshit. It's no wonder the conversation changes when your boss sits down at the lunch table. How depressingly typical.

If you use exceptions for your data validation, I hate you. I hate you so much, in fact, that I will become famous. Then I can say to you that a famous person hates you. I will become president and the first executive order I sign will be to make the official policy of the United States that I hate you. I will invent a time machine so that I can go back in time and on every one of your birthdays, past present, and future, look you in the eyes and tell you I hate you. Then I will travel to your death bed and in your final breath I will tell you I hate you. I will change the timeline so that you will celebrate Christmas and believe in Santa and then tell your four year old self that Santa isn't real. I hope your kids never learn how to read, and if they already know how to read I hope they forget how to read and never learn how to read. I hope all of your friends become vegan, atheist, flat earth, crossfitters and insist on regailing you with their life style on your every meeting.

I guess what I'm saying is that I'm having a bad day.

I love exceptions - ANSI C with exceptions - that would be perfect for me.
I know that there are different opinions out there... I can’t understand why they haven’t implemented exceptions into Go. I have read the article why they didn’t but for me... exceptions are a GREAT language concept!!!!

The Amazon Music app is so dumb. Instead of simply saying that it can't find anything for your search, it exclaims that they're experiencing difficulties, smh.

Boss: I don't want centralized error logging

Me: But we have 50+ client sites running the same web app, why the fuck wouldn't we?

Boss: What if the database is offline, then we wouldn't be able to log exceptions

Me: *beats head against desk*

For all things, for all men, that a man compliments a thing does not imply that this man at least attempts to understand this thing. However, for all men, that a man criticises a thing implies that this man at least attempts to understand this thing.

For all computer programs, that a computer program is terrible implies that scrapping the current implementation of this computer program and beginning anew may be the best method of fixing this computer program.

With few exceptions, for all programming languages $l$, given sufficient effort, $l$ source code can be human-readable.

The UNIX philosophy never became outdated.

For all computer programs $p$, $p$ should be written sufficiently well that the author of $p$ can be prideful of $p$.

For all computer programs $p$, a specification for $p$ should be written before $p$ is created.

For all good computer programs, a good computer program can run on terrible hardware.

Every clock cycle is valuable.

starting new job on monday, already received a new laptop... with windows 10... Asked if i can install Linux - absolutely not. Without exceptions.
*very long and slow sigh*
started it up, started customizing. Tried to remove a shortcut from desktop - a popup to login as admin...
*even longer and slower sigh, even though the previous one was near my limit*

can't wait to get started.
P.S. pros still outweigh the cons. but this is gonna be exhausting...

Raise your hand if you don’t trust the comments in code most of the time, and take at least a superficial look at the code block to ensure that it does what it says it does.

If you have any exceptions, please share.

evil === true

Found this one after 4 hours of debugging... Want to screw with other teams? Shove some UTF-8 BOM characters into JSON responses consumed by Node (and other frameworks as well). Watch as they scramble to find why JSON.parse() fails on seemingly nothing.

Background: BOM markers are hidden characters that indicate text stream information to applications. They are not ignored by many JSON parsers and throw exceptions that don't appear to make sense.

This moment:
When you have a weired exception, start googling it and practically bruteforcing all possible solutions you know of and/or found on stackoverflow.

Then after (half) an hour just starting from the beginning, attempting the simplest solution you can think of and it just works on the first attempt:

😱 ⏩ 😰 ⏩ 😤 ⏩ ☕ ⏩ 😥 ⏩ 😔

But you'll notice that you had learned a lot of this.
... Or maybe not 😜

What the fucking fuck. Arquillian you piece of shit.
I have a service that needs to go to production soon, it contains Arquillian tests. The tests work locally but not when going through our new Jenkins pipeline. The error message simply says: "Could not start Arquillian container".
Well fuck you too.
After 3 fucking days of rewriting configs, changing up things and I dont know what else I did, I stubled upon the most hidden error message in the history of error messages, a small little line that says "Could not find or load main class ".
Those 2 spaces are intentional btw, because the fucking error was that when starting arquillian and reading the config there was A FUCKING SPACE too much in my JVM arguments. This piece of shit iterpreted it as my FUCKING MAIN CLASS. Whhhhyyyyy, whhhyyyy. Who the fuck... AAAAAAAAAHHH

Btw I snuck myself on devrant a few weeks back and managed to get my 100++ today. Really love this place 😊