try {
♥️
}
catch(e) {
🍺
}

#happyvalentinesday

try {
❤
} catch(e) {
🍺
}

try{
❤️
}catch(){
🍺
}

After listening to two of our senior devs play ping pong with a new member of our team for TWO DAYS!
DevA: "Try this.."
Junior: "Didn't work"
DevB: "Try that .."
Junior: "Still not working"

I ask..
Me:"What is the problem?"
Few ums...uhs..awkward seconds of silence

Junior: "App is really slow. Takes several seconds to launch and searching either crashes or takes a really long time."
DevA: "We've isolated the issue with Entity Framework. That application was written back when we used VS2010. Since that application isn't used very often, no one has had to update it since."
DevB: "Weird part is the app takes up over 3 gigs of ram. Its obviously a caching issue. We might have to open up a ticket with Microsoft."
Me: "Or remove EF and use ADO."
DevB: "That would be way too much work. The app is supposed to be fully deprecated and replaced this year."
Me: "Three of you for the past two days seems like a lot of work. If EF is the problem, you remove EF."
DevA: "The solution is way too complicated for that. There are 5 projects and 3 of those have circular dependencies. Its a mess."
DevB: "No fracking kidding...if it were written correctly the first time. There aren't even any fracking tests."
Me:"Pretty sure there are only two tables involved, maybe 3 stored procedures. A simple CRUD app like this should be fairly straight forward."
DevB: "Can't re-write the application, company won't allow it. A redesign of this magnitute could take months. If we can't fix the LINQ query, we'll going to have the DBAs change the structures to make the application faster. I don't see any other way."

Holy frack...he didn't just say that.

Over my lunch hour, I strip down the WPF application to the basics (too much to write about, but the included projects only had one or two files), and created an integration test for refactoring the data access to use ADO. After all the tests and EF removed, the app starts up instantly and searches are also instant. Didn't click through all the UI, but the basics worked.

Sat with Junior, pointed out my changes (the 'why' behind the 'what') ...and he how he could write unit tests around the ViewModel behavior in the UI (and making any changes to the data access as needed).

Today's standup:
Junior: "Employee app is fixed. Had some help removing Entity Framework and how it starts up fast and and searches are instant. Going to write unit tests today to verify the UI behaivor. I'll be able to deploy the application tomorrow."
DevA: "What?! No way! You did all that yesterday?"
Me: "I removed the Entity Framework over my lunch hour. Like I said, its basic CRUD and mostly in stored procedures. All the data points are covered by integration tests, but didn't have time for the unit tests. It's likely I broke some UI behavior, but the unit tests should catch those."
DevB: "I was going to do that today. I knew taking out Entity Framework wouldn't be a big deal."

Holy fracking frack. You fracking lying SOB. Deeeep breath...ahhh...thanks devRant. Flame thrower event diverted.

<?php

wakeUp();
goToWedding();

while (atWedding() && bored()) {
browseDevrant();
}

goToTrainStation();
sleep(2700); // got there 45 mins early

while (trainIsMoving()) {
try {
workOnDevrant();
} catch (ProcrastinationException $e) {
// got distracted by devRant
}
}

goHome();

while (unrespondedStickerRequests()) {
sendResponse();
}

goToSleep();

?>

Waiting for a bus. And there is a 14 year old smoking and looking after 3 10 year olds. She then gets them to role her 'fags' and then they all smoke. They are blaring rap from a speaker I'm annoyed everyone is annoyed.

They get on a bus full of elderly people.

Then I have my moment. I hear they are switching phone that the speaker is paired to, for different music. They even say the device name! I quickly get my phone search Bluetooth devices and pair. I connected all I could think was play the tweenies. And so I did.

They have hysterics of laughter, but I try act neutral containing my laughter. They keep saying they can't connect and that it's not their music. This went on for 10 or so minutes of them turning volume up and down. Until they catch on someone else is paired to it. I turn off my Bluetooth and get off the bus, you are welcome society.

A couple of years ago, I was working in a computer shop as a "technician", I was 15, first job I ever had.
One day an elderly lady came into the shop, probably 50'ish, she and her whole family "suffered" from electromagnetic radiation, and the mother had the worst suffering. She complained about her TV box that just had died.

I accept the tuner and see it's wrapped with 10 layers of aluminium foil, with a tiny hole for the IR receiver.

The whole box smells like burnt electronics, and the foil gets darker for each layer I unwrap. I try explain to her that the box gets warm and overheated by wrapping it like this, and she's lucky that it didn't catch fire.

I further explain to her that she will not get a new box, because the warranty does not cover _this_. The mother tells me she has to wrap it like this, because she gets headaches when she's watching the news.

She then proceeds to go into a rage mode and gets her whole family into the shop, where all of them starts yelling at me, the younger kids start throwing stuff down from the shelves and touching the TVs with sticky fingers (literally, sticky, like yuck!).

Unsure what to do, boss is in a meeting, and my colleague is busy in the back.

So I calmly tell them that in this building there's 4 wireless networks, 3 wireless phones, high voltage cables run in the wall behind me, there's factory tracks 20 meters behind the building, next door business is an electrician, you're standing in front of wall with 30-40 TVs, 5 HDMI splitters, 3 TV boxes and a Blu-ray player. And they've all been standing in front of them for the last 10 minutes.

They all suddenly feel really sick and run out of the store, never to be seen again. From that day, I decided I'll never work in a shop again, and pursued my dreams to become a developer.

TL;DR: Family is "sensitive" to electromagnetic radiation, almost put burnt down their house because of stupidity, yelled at me. I decided to pursue my dream as a developer.

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.

Autocomplete in editors is like that annoying friend that keeps interrupt();ing every singletonInstance():le thing you try{}catch(Exception e)} to say, delay(1000);ing you COUNT(*)ntless of times.

This is how I learned try-catch....

😂😂Wrap it all up in try/catch

except Exception as e
pass

Error handling done properly.

At customer site with my boss.

Boss: let's check this code which is not working

Me: ok (starting the debugging session)

I found this code, which was failing during the writing on disk for some reasons.

try
{
....
writer.writeline(some data);
....
}
catch(Exception ex)
{
....
}

Boss: ok it fails to write data but we need to, let's manage it like this:

try
{
....
writer.writeline(some data);
....
}
catch(Exception ex)
{
writer.writeline(some data);
....
}

A Geologist and an engineer are sitting next to each other on a long flight from LA to NY. The Geologist leans over to the Engineer and asks if he would like to play a fun game. The Engineer just wants to take a nap, so he politely declines and rolls over to the window to catch a few winks. The Geologist persists and explains that the game is real easy and a lotta fun. He explains, "I ask you a question, and if you don't know the answer, you pay me $5. Then you ask me a question, and if I don't know the answer, I'll pay you $5." Again, the Engineer politely declines and tries to get to sleep. The Geologist now somewhat agitated, says, "OK, if you don't know the answer you pay me $5, and if I don't know the answer, I'll pay you $50!"

This catches the Engineer's attention, and he sees no end to this torment unless he plays, so he agrees to the game. The Geologist asks the first question. "What's the distance from the Earth to the moon?"

The Engineer doesn't say a word, but reaches into his wallet, pulls out a five dollar bill and hands it to the Geologist.

Now, it's the Engineer's turn. He asks the Geologist, "What goes up a hill with three legs, and comes down on four?" The Geologist looks up at him with a puzzled look. He takes out his laptop computer and searches all of his references. He taps into the Airphone with his modem and searches the net and the Library of Congress. Frustrated, he sends e-mail to his co-workers -- all to no avail.

After about an hour, he wakes the Engineer and hands him $50. The Engineer politely takes the $50 and turns away to try to get back to sleep.

The Geologist is more than a little miffed, shakes the Engineer and asks, "Well, so what's the answer?"

Without a word, the Engineer reaches into his wallet, hands the Geologist $5, and turns away to get back to sleep.

me_irl

Me: You girl are Exceptional, should I catch or throw you?

Her: You can try

Catch Warrior
Credits: Rahul Balan

Try and Catch

while(true) {
googleSomething();
try {
develop();
} catch(Exception e) {
stackOverFlow(e);
}
}

try catch

encapsulating bug with try-catch

90s devs: "Did you know about GOTO/CONTINUE for control flow? it's so convenient and powerful!"

00s devs: "GOTO is an antipattern. But did you know about try/catch? You can use it for control flow, just write a lot of exception classes, it's so powerful!"

10s devs: "Using exception blocks for generic control flow is an antipattern. But have you heard about event listeners and observer patterns? It's so powerful!"

Developers are so good at repackaging and reselling square wheels by giving them fresh, impressive sounding names.

😡

I've got a mini stroke today. My project ended and I got delegated elsewhere.

"It's going to be fine, it's c++, you will find yourself there"

Suspicious, it's a project everybody was staying out of as hard as they can. But hey, it's cool, how bad can it be? what can go wrong with that?

Reality was brutal, project that uses Boost C++ as framework and bjam as builder. Builds with a decent dose of luck, and only under special circumstances, only under one specific version of compiler. No docs, quartet of the code is in Fortran, just to use ancient lisp part which was second qarter. The most senior Dev around does not have idea how it all works. Also everything is inside one enormous try/catch block. Because of the reasons.

That's how people end up with severe alcoholism and meth addiction.

Basically...

Fuckin hell!!

Code works everywhere except at one client. Ok, I check logs & see something missing.. I go check the code that handles excel files.. try catch and do nothing.. great.. :/ ok let's log this shit to see what is not ok...
Insert logs, build, update, run.. now it freakin works o.O

😂😂😂

Last week I almost lost my belief in everything..

A friend of minde, he's currently learning programming (Delphi 😂) in some kind of university, just told me:
"Hey, why do you spend so much time caring about error handling? I just surround all my programs with one try catch block and I never have to think about errors!"

Ehm. No statement needed, right?

Void foo() {
try {
//Try something
} catch(exception e) {
foo();
}
}

When I saw this in production I cried a little...

Once upon a time in Devland, there were two best friends @Alice and @Michelle and they worked together at The DevCo company as developers.
After a tough day handling an @-ANGRY-CLIENT-, they thought that they had to go and @RantSomewhere and so they went to a café. At the café, they ranted about some stupid clients, and @theItalianGuy at the third floor of their office building who never picked up calls, and @thatJavaGuy from the second floor who, they thought, was @notarealDev, and the usual stuff about their work. Somewhere in between, @Alice thought it would be @funvengeance to @hack @theNSA; “@karma is coming to get them”, said @Michelle.
To do this, they knew they’d have to take help from none other than @Gandalf who lived in a nearby @cave. So, the next day, taking a leave from work, @Alice and @Michelle embarked on journey to meet @Gandalf. After about an hour’s drive, they reached @Gandalf’s @cave. @Michelle went ahead to knock on @Gandalf’s rusty cave door. Being a lazy @necromancer, he magically opened his door 2 minutes later. “Who is't dares to disturb me in mine own catch but a wink?” shouted a voice from the back; “We’re two developers from DevCo and we need your help in our mission to @hack @theNSA”, shouted @Michelle. After a few seconds, he replied, ”Hmm… N'rmally I wouldst sendeth thee to mine own cousin @Hagrid, but in thy case, I sayeth thee shouldst visiteth the detective who is't goeth by the nameth @S-Holmes”. @Alice replied back, “Thank you, Sir @Gandalf, we’ll get help from this @S-Holmes, I’ve heard that he’s an @exceptionalGuy”; “Mine own pleasure, Farewell!” said @Gandalf, and the door closed shut.
So, @Alice and @Michelle went back to their car, and that time @Alice raised a question, “How are we gonna find this @S-Holmes? We don’t have a phone number or anything so we could contact this guy.”
“We should call @thatJavaGuy from work, I’ve heard he is a man of resources, he must know how to contact @S-Holmes”, said @Michelle.
And it was true, after a call with @thatJavaGuy, they were able to obtain @S-Holmes’s phone number.
“Howdy, this is @S-Holmes, what can I diddily ding dong do you for?”
“Hi, I’m @Alice, I’m from DevCo and I was hoping that I could get your help in our mission.”
“What kind of mission?”, asked @S-Holmes.
“We want to @hack @theNSA.”, replied @Alice.
“Okay… I think I might be able to hel-diddly-elp you! There’s an old and abandoned laberino noodly-near @stacked Street. It was made in @1989 and since then, it houses a magical computeroo that can hel-diddly-elp you in your mission. So, you just have to connect the computeroo to the Internet and you can diddily ding dong do your programmeroo thing and then you'll have access to the the noodly-nsa diddily ding dong database!”, answered @S-Holmes.
S-Holmes continued, “But I shall warn you, there's a riddly-rumorino that the laberino was abandoned because of an @electric-ghost that lurks there, but I bel-diddly-elieve it is just a computeroo program that was diddily ding dong designed to try to @stop hackers from accessing the top secret stuff!".
“Okay, thanks for your help! I bet we can handle whatever this @electric-ghost thing is, so… Goodbye!”, replied @Alice.
“Goodbye!”, said @S-Holmes and that ended their conversation.
Luckily, the @stacked Street was just a couple of miles away from them, so they reached the lab quickly.
As they got close to the lab they saw something that really surprised them…
--------
To be continued in part two...
(Do you want a part two? :/)

My first ever story is a little special because it is kind of dev related at it has "cameos" by various devranters, as you might have noticed.
How many did you count?
More in Part Two.

Thank you for reading and please, any feedback is welcome. Did you like it?
I haven't really revised it once, it is straight out of the keyboard.
Should I drop the "@" ?
But then it would impossible to spot some of the devRanters .
Let me know.

PS
What should be the title?
1)Alice in DevLand?
2)Adventures of Alice and Friends: Hacking the NSA?
You decide..(or maybe I'll pick the second one :D)

try{
unprotectedSex();
}catch(STDs){
treat(STDs).asap();
}

Sorry, but the app had to stay running. It was just a minor exception anyway.

try {
executeMainLoop();
}
catch (Exception ex) {
executeMainLoop();
}

I had a friend whom I met in an open-source community. We hadn't been in touch for a while because of the distances of where we were. Coincidentally, we happened to be working in the same city. When we knew that we were in the same city, we decided to meet and catch up. We met over dinner and this person went on and on about his company and how cool the culture was there.

Towards the end, I jokingly said, "If your company is so cool, why don't you get me a job there?"

2 weeks later, he sends me an email address and asks me to send my resume to it.
1 more week later, HR from the company calls and asks whether I can come to office to chat.
I agree and head over there over lunch break. I _speak_ to the person who was going to be my manager and later to the CTO. The CTO asks me a few technological questions and sends me off.
1 week later, I call up HR just to know how I fared in the interview. They say that they'll give me an update within the week.
Next week I get a call from HR asking when I can join. Could I join with 2 weeks of notice period? I could try, the pay was almost double that I was already earning.
I speak to my existing boss about the offer and they offer me an immediate hike of 30%. That gives me a notion that I was already under-paid. I wouldn't want to continue working with an employer who knowingly paid me low (even though I was content with what I was getting already). I make my decision to quit. Puts in my 2-week notice period and join the new company on the said date.

We should totally be able to use try/ catch irl, especially in social situations

try{
riskyText();
} catch (InappropriateTextError e) {
abort();
}

Comment your best developer pickup line...

here's mine...

I think you're exceptional, I can try & catch you.

Try/Catch in the real world.

no try and catch in here 🙊

!rant

It's Friday and my boss let us off work early...

So imma just chill and try to catch the sun

SUPERVISOR: You wrote this 140 lines method, it's too long. You should split it up, it's not readable
IHateForALiving: Bruh be serious, this is a single switch-case; I can't split it.
SUPERVISOR: Fine, I'll do it.

HIS CODE: He split the 140 lines method into 2 methods: the first is 4 lines long; it's a try-catch surrounding a call to the other method, 136 lines long.

Why do Pokemon masters love JavaScript?

Because you gotta, try/catch them all

Haha. No laughs? Okay

*curls into a ball

Catch or catch not, there is no try.

How my code is some days...:/

Should I fix this properly or just wrap it in a try/catch? hmmm

static void TryOut<T>(T newStuff)
{
try
{
self.Learn(newStuff);
}
catch (NotUnderstandingException)
{
// At some point, it will work, just call it again
TryOut(newStuff);
}
}

As a Java developer, reasons to kill other programmers:

- static mutable variables
- WRITING to static mutable variables
- API call with Framework X didn't work. Add Framework Y along with X and try that. Wrap X in try/catch statement. Catch block fires framework Y.
- six, seven, ten levels of nested code. Zero thought put in organization
- 6K LOC Java files
- spring (singleton? Maybe) object assigning values in static mutable (see pt.1)
- a couple of unit tests in code base that no longer work. Zero unit tests in new code
- unit testing disabled in CI pipeline
- empty catch blocks
- pass mutable data between threads. Modify in various places concurrently.

What if all that was that easy !! :-P

Guess he used try/catch

A Geologist and a developer are sitting next to each other on a long flight from LA to NY. The Geologist leans over to the developer and asks if he would like to play a fun game. The Developer just wants to take a nap, so he politely declines and rolls over to the window to catch a few winks. The Geologist persists and explains that the game is real easy and a lotta fun. He explains, "I ask you a question, and if you don't know the answer, you pay me $5. Then you ask me a question, and if I don't know the answer, I'll pay you $5." Again, the Developer politely declines and tries to get to sleep. The Geologist now somewhat agitated, says, "OK, if you don't know the answer you pay me $5, and if I don't know the answer, I'll pay you $50!"

This catches the Developer's attention, and he sees no end to this torment unless he plays, so he agrees to the game. The Geologist asks the first question. "What's the distance from the Earth to the moon?"

The Developer doesn't say a word, but reaches into his wallet, pulls out a five dollar bill and hands it to the Geologist.

Now, it's the developer's turn. He asks the Geologist, "What goes up a hill with three legs, and comes down on four?" The Geologist looks up at him with a puzzled look. He takes out his laptop computer and searches all of his references. He taps into the Airphone with his modem and searches the net and the Library of Congress. Frustrated, he sends e-mail to his co-workers -- all to no avail.

After about an hour, he wakes the Engineer and hands him $50. The developer politely takes the $50 and turns away to try to get back to sleep.

The Geologist is more than a little miffed, shakes the developer and asks, "Well, so what's the answer?"

Without a word, the developer reaches into his wallet, hands the Geologist $5, and turns away to get back to sleep.

import java.util.Exception;
try {
public class A {
public static void main(String args[]) {
new Exception();
}
}
}
catch(Exception e) {
System.out.println("Got you BITCH");
}

When you don't care anymore...

imagine the new try/catch block

try
..
catch
...
finally
....
please
...
how dare you?! (Application.Exit())

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

They see me coding
They testing
The Try and Catch blocks show me coding dirty
Show me coding dirty ...

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

and then it happened

fucking always print something when you catch exceptions

Just found this piece of code from one of my coworkers:

restMethod() {
try {
// some complicated logic
} catch (WebApplicationException e) {
throw e;
}
}

Why?!

And btw: Hi fellow devRant ppl! 👋

try {
// code that will someday
// throw an exception. Today is
// not that day.
}
catch(Exception ex) {
// The big day has arrived! BUT...
// I'm a heartless bastard who
// does not log errors.
// Good luck finding me!
}

I'm planning on making a band called Bar Fighters and will play songs like Integer Or Long, The Renderer, Test of U nit, Learn to Try ( catch )

do {
try
} catch {
// This block probably never gets called.
}

"BOYYYYY, WAS I WRONG"

Someone gave me a web method that return a boolean.
The Boolean tells me if the operation went well.
True means everything went well
False means something went wrong

But
It throws exception when something went wrong.
Basically they implemented a Boolean system to check if everything is alright but I also have to add a try/catch if something is not right.

Me: Hey, I need to know when the user double clicked this.

B: It's easy, just put a try catch with DoubleClickException

Me: ...

B: ...

Me: and how about right click?

B: RightClickExce...

Me: Ok. I'm out

public String getDbPasswd(){
try{
String dbPasswd = SomeInhouseEncryptionLib.getPasswd("/hard/coded/path/to/key");
return dbPasswd;
} catch(Exception e){
LOGGER.log(Level.SEVERE,e)
return "the-actual-password";
}
return null;
}

And this is now in production
FML

Dear Product owners / Company Owners / Whoever requesting a feature:

Devs like to know they are adding value to whatever product they are working on. Every time you request a stupid no value added request, you kick the dev's soul.

After several hits the developer will stop caring about the software and eventually will get the job done, but oh boy, the amount of tech debt/trash code the dev is gonna leave behind will be horrendous.

Then the next developer, not only takes the hit from another stupid request, he/she will see the crappy code the past sad developer left and will take a double hit. Of course all of them start proactive and try to fix previous blood trails but sadness will catch them eventually.

If you want you're apps/products/reports to be good in a long run don't make stupid requests.

BAs, Stop being Expensive Email Forwarders and challenge a request, understand the process and then hand it to the developer.

Us developers are sensible cute ponies. Treat us well or expect poor quality projects

Maturity is transitioning from throwing errors to catching them.

when you get an exception but the application doesnt crash

"I'll add the try catch later"

try{
#$$##&@;
}
catch(ex){
console.log('haha');
}

Love really fucking sucks. It's the only exception i try but can't catch and i end up crashing in a bar alone and drunk. I finally wake up in my apartment just to do it all over again.

condition == true

is for boys,

public static boolean isTrue(boolean condition) {
try {
return new Boolean(condition).equals(Boolean.parseBoolean(new String(Boolean.toString((boolean) Boolean.class.getField(String.valueOf(true != false).toUpperCase()).get(null)).toString().toCharArray())));
} catch(Throwable t) {
return condition;
}
}

is for men.

!rant

So, I imagine this little prank is about as old as graphical OS interfaces, but anyways.. Now and then I will take a screenshot of someone's desktop, set that image as their wallpaper, then hide all their icons, make their taskbar (or plural for Linux) to the smallest possible size, and wait for them to try use their PC.

One day a few years back, I tried to catch my mom with this trick, but although it was still pretty epic, it did not happen quite as I expected.

Suffice to say with her knowledge of keyboard shortcuts, she actually used her laptop for about an hour before she noticed none of the taskbar buttons were working.

Yay for trying to prank people who actually know how to use a computer. Lol.

Programming Go!
Gotta

try {
...
}
catch (em) {
...
}

all!

try {
RiskyFunction()
//a gazillion lines more
}
catch() {}

//Wow! The app is not breaking anymore!

What you see in that screenshot, that was earned.

I'm on the plane and I want an hour of free Gogo (read: crappy) WiFi on my laptop (so I can push the code I'm probably the most proud of, more on that another time). The problem is that the free T-Mobile WiFi is apparently only available on mobile.

So after trying to just use responsive mode, and that still (almost obviously) not working. I realize it's time to bring in the big guns: A User Agent switcher. Small catch: I don't have an add-on for FF that can do that.

So on my phone I find an add-on that can and download the file. To send it to my computer, I initially thought to go through KDEConnect, but Gogo's network also isolates each system, so that doesn't work. So I try to send it over Bluetooth, except I can't. Why? Because Android's Bluetooth share "doesn't support" the .xpi extension, so I dump it in a zip (in retrospect, I should have just renamed it), and now I can share.

After a few tries, I successfully get the file over, extract the zip, and install the extension. Whew! Now I open up Gogo's page and proceed to try again, but this time I change the user-agent. Doesn't work... Ah! Cookies! I delete the cookies for Gogo (I had a cookie editor add-on already), but I had to try a few times because Gogo's scripts keep trying to, but I got it in the end.

Finally that stupid error saying it's for phones only went away, and I could write this rant for you.

I heard scary thing.
A tester found an issue yesterday. He came to the dev and reported about it. Apparently the only feedback message was "something went wrong". They spend almost an hour hunting down the cause for that. It turned out the error message was from one of the try-catch. I do not know much details apart from that. At the end, the dev lead said this (which he had said before).

"That's why I don't like to catch exception."

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
}
}
}

Just need to get this off my chest. Started a new job 3 weeks ago at a company that has been around ~18 years, it is only recently that they have started to grow more rapidly. I was brought in under the guise that they wanted to embrace change and better practices and so said I was up for the challenge.

In my 2nd week I was asked to produce a document on tackling the technical debt and an approach to software development in the future for 3 consultants who were coming in to review the development practices of the company on behalf of the private equity firm who has taken a major stake in the company. I wrote the document trying to be factual about the current state and where I wanted to go, key points being:

Currently a tightly coupled monolith with little separation of concerns (73 projects in one solution but you have to build two other solutions to get it to build because there are direct references.).

Little to no adherence to SOLID principles.

No automated testing whatsoever.

Libraries all directly referenced using the file system rather than Nuget.

I set out a plan which said we needed to introduce TDD, breaking dependencies, splitting libraries into separate projects with nuget packages. Start adhering to SOLID principles, looking at breaking the project down into smaller services using the strangler pattern etc. After submitting what I had written to be part of a larger document I was told that it had been tweaked as they felt it was too negative. I asked to see the master document and it turns out they had completely excluded it.

I’ve had open and frank discussions with the dev team who to me have espoused that previously they have tried to do better, tackle technical debt etc but have struggled to get management to allow them. All in all a fairly poor culture. They seem almost resigned to their fate.

In my first 2 weeks I was told to get myself acquainted and to settle myself in. I started looking at the code and was quite shocked at how poorly written a lot of it was and in discussions with my manager have been critical of the code base and quite passionate and opinionated about the changes I want to see.

Then on Friday, the end of my third week, I was invited to a meeting for a catch up. The first thing I was told was that they felt I was being too openly critical in the office and whether I was a good fit for the company, essentially a stay or go ultimatum. I’ve asked for the weekend to think about it.

I’ve been a little rocked by it being so quickly asked if I was a good fit for the company and it got my back up. I told them that I was a good fit but for me to stay I want to see a commitment to changes, they told me that they had commitments to deliver new features and that we might be able to do it at some point in the future but for now I just needed to crack on.

Ordinarily I would just walk but I’ve recently started the process to adopt kids and changing jobs right now would blow that out the water. At the same time I’m passionate about what I do and having a high standards, I’m not going to be silenced for being critical but maybe I will try and tackle it in a different way. I think my biggest issue is that my boss who was previously a Senior Developer (my current position) has worked at the company for 12 years and it is his only job, so when I’m being critical it’s most likely criticising code he wrote. I find it hard to have the respect of a boss who I had to teach what a unit test was and how to write one. It makes it hard to preach good standards when by all accounts they don’t see the problems.

Just wondering if anyone has suggestions or experience that might help me tackle this situation?

How did you break through your own barriers to finally learn programming?

My SO is constantly complaining that we don’t have enough money. I make a decent amount as a full-time dev at a large company, but we live in an expensive city and are currently going through a time of few funds.

He started driving delivery food orders, he likes it okay, but it pays very little. He still complains about money.

I want him to learn JavaScript.

He was once asked to make a website for a company he’s involved in. He only used SquareSpace, but he was never satisfied with their stock code. He went digging for JavaScript snippets he could use, and he made one of the most beautiful and responsive websites I’ve seen.

Since then, I’ve been encouraging him to learn JavaScript. I’m trying to convince him it will be a great source of additional income, he can make his own schedule while doing contract work, and he can ask me anything he wants while he’s learning. How many beginners have someone they can ask anything of, at any time?

He doesn’t want to learn. He doesn’t think he is capable. I remember this feeling before I learned to code. A chunk of someone else’s JS does look genuinely terrifying if you don’t know what it means. I want him to give it one honest try before he decides it’s “not for him,” but he isn’t open to it enough to try.

What can I do to help him understand he is capable? He’s in his mid-30s and insists he’s too old to catch up. He’s smart, detail-oriented, and I know he would write code that’s a million times cleaner than mine. He absolutely has a programmer inside of him, and I want to encourage him to simply try.

Is there something I can to do introduce JS in a non-threatening way? Or should I just accept his refusal and let it go? Thanks for any advice.

The more I use Go, the more i start to like it. I didn’t realize how nice being able to generate binaries for every OS that matters was, until I had that power. It beats the hell out of trying to distribute a Python app for sure.

Sure, it has its warts.

It’s overly bureaucratic in the same way Java is.

I hate that you can’t import something without using it (most people I’d wager preemptively import libraries they know they’re gonna need even if the code isn’t written yet)

I really wish there was a way to just say “See this JSON blob? All those keys and values are strings, trust me, you don’t need me to tell you the type of each one individually.”

Generics would be nice.

I’d kill for exceptions - any decently sized go program is going to have very many if err checks where most could be condensed down to a single try/catch in most other langs.

I wish the tooling was better. Dependency management was a solved problem when Go was released and yet they chose to ship without it. There’s still no standard. Many hours of time have been wasted dinking with this.

But ya know what? Even with those warts, it’s still easier to write than Java. It’s still write once run anywhere, it’s blazing fast, and doesn’t require your end user to install an entire freakin runtime.

<3 Go

try{

}catch(Exception e){
//do nothing
}

Google:- Google home is using machine learning to remove all type of back noise like traffic, air, and others so the call experience goes smoother.

Microsoft:- In Skype we are using machine learning to catch all type of back noise and mix it with your voice. Skype will try every possible way to make your call experience as bad as possible. Every type of noise Trafic, Air, hardware, your breath if there is nothing! the software will cut your voice and send only a few parts.

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 :)

Today,I found this gem:

static function getConfig(){
$cacheKey = 'foobar';

try {
$config = $this->repository->getConfig();

$this->cache->set($cacheKey, $config);
}
catch(Exception $e){
try{
$config = $this->repository->getConfig();

$this->cache->set($cacheKey, $config);
}
catch(Exception $e){}
}
}

I don't want to live on this planet anymore...!

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>>

Relax, I'm a professional!

!rant
In javaScript there are three ways to interpret comments (this also works the same way in many other languages):

// This is a comment :)
/* This is also a comment :)) */
try {
    This is the third comment :)))
}catch(){}

God damnit!
i recently inspected the c# sourcecode of a webservice, our webservice develop references to.

As i discovered a particular function in it, my face went instantly pale.

This golden-hammer function consists of ~2000 lines of code.
In the first line there is "try {".
On the last lines is "catch (Exception e) { throw new SomethingWentWrongException ("special function"); }"

At least, he "tried" xD

I don't want to develop on that planet anymore...

Syntax for my proposed "unsure" programming language.

Variable declaration:

let's just say that <variable name> = <value>

Function declaration:

hypothetically, we could <function name> (<args>){}

Try/ catch:

it's possible that
{

}
...or not (<ex>)
{

}

A project manager, a computer programmer and a computer operator are driving down the road when the car they are in here a flat tire. three men try to solve the problem

the project manager said: let's catch a cab and in ten minutes we will reach out destination.

the computer programmer said: we have drivers guide.I can easily replace the flat tire and continue our drive.

commuter operator said: first of all turnoff the engine and turn it on again. may be it will fix the problem.

suddenly a Microsoft engineer passed by and said: try to close all windows, get off the car, and then get on and try again.

Nightmare IRL:

Your colleague is in PTO for 2 weeks.

You are in charge of maintaining his project along with yours, CI, code, tests and everything.

Your colleague's code base is a real master piece of shit when you look at it closer. By shit, I mean hardcoded values everywhere, random sleeps now and then, 20 if branches that could be replaced by maps, variables named a b c d everywhere, try catch to silence errors that should not be silenced, etc.

Your colleague left the CI and code broken as shit. Takes forever to run on my goddamn computer.

PMs are spamming you: "What is going on? It's red everywhere. Help! Plz fix this! We are going to release tomorrow!"

FML

Actual production code:
try{
[code]
try{
[code]
}catch(Exception ex){
[code]
}
}catch(Exception ex){
[code]
}
Double blasphemy!

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!

//Dunno what causes these random connection errors; probably just hiccups in connection between our EC2 instance and Discord
try {
client.login(token);
} catch(e) {
//Do nothing, just prevent it from crashing the main thread and the client will reconnect
}

So I'm writing some multithreaded shit in C that is supposed to work cross-platform. MingW has Posix threads for Windows, so that saved already half of the platform dependency. The other half was that these threads need to run external programs.

Well, there's system(), right? Uhm yes, but it sucks. It's incredibly slow on Windows, and it looks like you can have only one system() call ongoing at the same time. Which kinda defeats the multithreaded driver. Ok, but there's CreateProcessA(), and that doesn't suck.

Fine, now for Linux. The fork/exec hack is quite ugly, but it works and is even fast. Just never use fork() without immediate exec(). First try under Cygwin... crap I fork bombed my system! What is this shit? Ah I fucked up the path names so that the external executable couldn't be run.

Lesson learnt: put an exit() right after the exec() in the path for child process. Should never be reached, but if it goes there, the exit() at least prevents a fork bomb.

Well yeah, sort of works under Cygwin, but only with up to 3 threads. Beyond that, it seems like fork() at some point gives two processes the same PID, and then shit hangs.

Even slapping a mutex around the fork and releasing it only in the parent process didn't help. Fork in Cygwin is like a fork in the ass. posix_spawn() should work better because it can be mapped more easily to the Windows model, but still no dice.

OK, testing under real Linux. Yeah, no issues with that one! But instead, I get some obscure "free(): invalid size" abort. What the fuck would that even mean?! Checking my free() calls: all fine.

Time to fire up GDB in the terminal! Put a catch on the abort signal, mh got just hex data. Shit I forgot to compile with -O0 and -g. Next try. Backtrace shows the full call trace, back to the originating line in my program - which is fclose() on a file.

Ahhh I remember! Under Linux, fclosing a file that is already closed makes the program crash. So probably I was closing it twice. Checking back.. yeah that's where it was.

Shit runs fast on several cores now!

try philosophy()
catch markAsSpam()
Do you ever think of organizations as people? People personify Google and stuff all the time, but I mean something deeper.
When I look at devRant threads, I feel like we're all part of a collective consciousness, growing and thinking and making decisions. Society is a living thing of its own, in the same way that living cells unknowingly make up an individual body. When a question is asked from one node, another node answers, and the result is a repository of questions, answers, opinions, and jokes on an app that might appear as the scrolling thoughts of a singular mind rife with pure, aggressively structured information.

Why do programmers take so long in the shower?
They read the directions on the shampoo bottle and follow them to the letter:
Lather, rinse, and repeat.
If only shampoo used for-loops in their instructions...
while(hair.isDirty){
hair.wash();
hair.rinse ();
}
while(hair.isDirty() && !shampoo.isEmpty()){
hair.wash();
hair.rinse();
}
Come on man, we should still stop if we run out of shampoo even if the hair isn't 100% clean yet.
while(hair.isDirty() && !shampoo.isEmpty() && tap.waterStillHot()){
hair.wash();
hair.rinse();
}
This could go on forever, I mean the adding of special cases.

try {
while(hair.isDirty() && !shampoo.isEmpty() && tap.waterStillHot()){
hair.wash();
hair.rinse();
}}
catch(sexException) { self.f___(spouse); } // spouse showed in in mid-rinse
catch(deathException) { spouse.arrangeForBurial(self); } // user died while showering
More importantly, you also need to catch a hairNotFoundException in the event that the user is bald. Or more properly, wrap the whole thing in "if(hair != null)". You don't want bald users throwing an exception every time they shower.

-- From a reddit feed a while back.

String nullabity check duel...
null, isEmpty(), "", " ", '', ' ', " null", boolean, NaN, undefined, isNullOrEmpty and finally try-catch

*Senior Dev:* Ah yes, we need to put try-catch in every function to handle errors and Logger.Log() at the beginning.
*Me:* Is not better to define a global error handler and use the stacktrace instead of doing all that?
*Senior Dev*: ...
*Senior Dev*: Is a rule here, do what I'm telling you.

Try/Catch doesn't fix stupidty! OR BAD CODE!

When my try catch doesn't works

First Rant here.

So I was working on some integration test issues when I found this by accident made by a professional level SW engineer:

@Test
public void testMethod() throws ApiException {
Response res = null;
try {
res = serviceToTest.callMethod();
} catch(Exception e) {
assertNull(res);
}
}

Was wondering why tests were being green after some code changes I've made cuz tests could have not been green afterwards.

Together with a senior (I'm also professional only) I've tried to explain him for a good 1-2hrs why this code is useless and he still did it. Good thing there are no errors in the real implementation from him after fixing the tests as it's code freeze here and we are having go live in a few days 🙃

Also luckily he isn't working on our code anymore and has only been doing so for a few weeks.

Wasted a day with it and gonna check all of his code now before I run in the next surprise.

try {
boolean isOk = meetTheGirl("Anna");
if (isOk) {
kiss();
goHomeAndProgram();
}
else {
cry();
goHomeAndProgram();
nextDay();
pickUpAGirl();
}
} catch (Exception e) {
//I don't know. My life is so empty
}

I have seen try/catch staments and rest api calls on a class constructor! OMG

Not the worst, but probably the only one I can sort of explain & not get into trouble for NDA breach..

Umm.. here it goes.. wrong id returned from db procedure, tried to do something on db with that id and got exception that the id doesn't exist. Instead of checking why the procedure returns nonexistent id, he just wrapped everything in try catch without any logs.. & of course, didn't tell anyone about this.. o.0

I know, I know, code review could have prevented this, but holy fuck..
Guy's cv had more experience than I have now, so at the time, I didn't think I'd have to check every line of code he wrote, especially not for shit like this.

Just a

try {
adult()
} catch (e) {
backToBed()
}

Kind of day

App fails, Check logs...No error logged. Check source code and debug....
And then you see following piece of code....

try{
//Code to hit an API
}catch(Exception ex){
/*DO NOTHING. Not even log stack trace*/
}

Not quite a interview question, but in a competition (I had build a compiler) the jury (they all told me they had all studied informatics) asked me what a compiler is... Not in a "lets try to catch him off manner" but rather in a "i am too stupid for this world manner" he asked me what a compiler was... And it got even worse: my compiler is based on linuxes utils (nasm+ld) the guy didnt know about linux. Assembler was much too much for him and when my compiler threw an error (I wanted to show them the error system) he told me I shouldnt present unfinished projects... Atleastthe other two were really nice and i still got 2nd place (behind a person who prorammed an Nxt thingy)

!dev

Ive been looking for a hobby for years but nothing is interesting enough.. i lose interest within a few hours (besides cars but thats expensive so i only work on it very once in a while).

But now everything changed.. I was looking for something that keeps my mind busy but I was soooo bored those last months that I went fishing just to get outside..
turns out my new hobby is the opposite of what i was looking for.. fishing and completely turn off my brain.. its so calming to just be alone in the nature and do a very simple task, thowing out and pulling in with a chamce of catching a nice dinner.. try-catch basically..

assembled my first custom rod today, i kept in mind what i liked about certain rods and then put the best of each of them into my own rod..

if youre stressed and and introvert you should try it..

havent been that calm in years..

The legit mod of try-catch! :P

Last Monday I bought an iPhone as a little music player, and just to see how iOS works or doesn't work.. which arguments against Apple are valid, which aren't etc. And at a price point of €60 for a secondhand SE I figured, why not. And needless to say I've jailbroken it shortly after.

Initially setting up the iPhone when coming from fairly unrestricted Android ended up being quite a chore. I just wanted to use this thing as a music player, so how would you do it..?

Well you first have to set up the phone, iCloud account and whatnot, yada yada... Asks for an email address and flat out rejects your email address if it's got "apple" in it, catch-all email servers be damned I guess. So I chose ishit at my domain instead, much better. Address information for billing.. just bullshit that, give it some nulls. Phone number.. well I guess I could just give it a secondary SIM card's number.

So now the phone has been set up, more or less. To get music on it was quite a maze solving experience in its own right. There's some stuff about it on the Debian and Arch Wikis but it's fairly outdated. From the iPhone itself you can install VLC and use its app directory, which I'll get back to later. Then from e.g. Safari, download any music file.. which it downloads to iCloud.. Think Different I guess. Go to your iCloud and pull it into the iPhone for real this time. Now you can share the file to your VLC app, at which point it initializes a database for that particular app.

The databases / app storage can be considered equivalent to the /data directories for applications in Android, minus /sdcard. There is little to no shared storage between apps, most stuff works through sharing from one app to another.

Now you can connect the iPhone to your computer and see a mount point for your pictures, and one for your documents. In that documents mount point, there are directories for each app, which you can just drag files into. For some reason the AFC protocol just hangs up when you try to delete files from your computer however... Think Different?

Anyway, the music has been put on it. Such features, what a nugget! It's less bad than I thought, but still pretty fucked up.

At that point I was fairly dejected and that didn't get better with an update from iOS 14.1 to iOS 14.3. Turns out that Apple in its nannying galore now turns down the volume to 50% every half an hour or so, "for hearing safety" and "EU regulations" that don't exist. Saying that I was fuming and wanting to smack this piece of shit into the wall would be an understatement. And even among the iSheep, I found very few people that thought this is fine. Though despite all that, there were still some. I have no idea what it would take to make those people finally reconsider.. maybe Tim Cook himself shoving an iPhone up their ass, or maybe they'd be honored that Tim Cook noticed them even then... But I digress.

And then, then it really started to take off because I finally ended up jailbreaking the thing. Many people think that it's only third-party apps, but that is far from true. It is equivalent to rooting, and you do get access to a Unix root account by doing it. The way you do it is usually a bootkit, which in a desktop's ring model would be a negative ring. The access level is extremely high.

So you can root it, great. What use is that in a locked down system where there's nothing available..? Aha, that's where the next thing comes in, 2 actually. Cydia has an OpenSSH server in it, and it just binds to port 22 and supports all of OpenSSH's known goodness. All of it, I'm using ed25519 keys and a CA to log into my phone! Fuck yea boi, what a nugget! This is better than Android even! And it doesn't end there.. there's a second thing it has up its sleeve. This thing has an apt package manager in it, which is easily equivalent to what Termux offers, at the system level! You can install not just common CLI applications, but even graphical apps from Cydia over the network!

Without a jailbreak, I would say that iOS is pretty fucking terrible and if you care about modding, you shouldn't use it. But jailbroken, fufu.. this thing trades many blows with Android in the modding scene. I've said it before, but what a nugget!

I just want to share this:

When I start working at my last job, I have little idea of what a unit test was.

My boss on one meeting said that unit testing will be mandatory (wich is ok and umderstandable).

Almost a *year* after that, no one still care about them. I see myself doing them the best I can, but I saw things like wrap the assertion line with "try / catch" to lie to the coverage and unit test percentage. Or in other cases directly uploading *manually* the code on the server without test at all.

And then, as the only developer who do the unit test ok I have to do the missing ones and repair the fake ones.

Then when something explodes the question all the managers love to ask "Did we had the testing?"

At least I quit... that job was some crazy shit, this is just one story of many.

Like that other time that my co-workers did not understand why I needed to do POJOs on an android app because the big bad JSON that the app used was working fine....

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

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

try{
superLikelyToFailMethod()

}catch(Exception whoCares){

}

Worried about your application crashing? I have a fix. through the entire thing in a try/catch and catch Exception. 😁😁

Startup-ing 101, from Fitbit:
- spy on users
- sell data
- cut production costs
- mutilate people's bodies, leaving burn scars that will never heal
- announce the recall, get PR, and make the refund process impossibly convoluted
- never give actual refunds
- claim that yes, fitbit catches fire, but only the old discontinued device, just to mess with search results and make the actual info (that all devices catch fire) hard to find
- try hard to obtain the devices in question, so people who suffered have no evidence
- give bogus word salad replies to the press

This is what one of the people burned has to say:
"I do not have feeling in parts of my wrist due to nerve damage and I will have a large scar that will be with me the rest of my life. This was a traumatic experience and I hope no one else has to go through it. So, if you own a Fitbit, please reconsider using it."

Ladies and gentlemen, cringefest starts. One of fitbit replies:
"Fitbit products are designed and produced in accordance with strict standards and undergo extensive internal and external testing to ensure the safety of our users. Based on our internal and independent third party testing and analysis, we do not believe this type of injury could occur from normal use. We are committed to conducting a full investigation. With Google's resources and global platform, Fitbit will be able to accelerate innovation in the wearables category, scale faster, and make health even more accessible to everyone. I could not be more excited for what lies ahead".

In the future, corporate speech will be autogenerated.

(if you wear fitbit, just be aware of this.)

A piece of code someone just pushed:
In pseudocode
------------------------
Function foo()
Result = GetFoo()
If result != null
DoStuff()
Return result
Else
Result = null
--------------------------
Ffs.

It's written in a strongly typed language, and the whole function is in a try with an empty catch and inside yet another try with an empty catch. Guess he wanted to be sure no error got away....
Oh, and he has 9 years of experience, and since all paths don't return something it does not compile

Cannot understand those who are frustrated with it.
Sure, one can feel frustration when some project is not going as they were supposed to go, but that is life for ya, boi.

Without wanting to offend anyone it feels like devs who complain so much either do not actively search for a solution and learn shit properly and cry their soul out afterwards or they do search, but cannot find anything.
Patience is the solution. Do not let yourself fall down and stay strong.
Even if it takes a lot of willpower, retries, inner pain, patience and non-sleepy nights, you will and can do it. I believe in you.

My whole life was basically a psychological disaster.
I have had and still have depression and a lot of short frustrations from time to time, too, but I do not cry it out loud.
My high school is fucked up. In every single aspect. I am doing all-nighters almost every day. With maybe half an hour of sleep to get school projects done on time.
I cannot just say "fuck you. I am not gonna do this shit" to school, because that would affect my grades in a negative way. Same thing applies to you, as an employee, too. But at least you do not need to be afraid of getting bad grades.
Bad grades->not getting the desired degree->bad chance of finding a job
In your case:
Bad communication with boss->bad connection->bad chance of finding a job

But is that really so?
I do not think so. Nonetheless, you still can have a good chance of finding a job, if you have proven yourself to others in a great way. Everyone has bad times. Even with their bosses. That's normal. Being bad with someone does not make yourself bad in general.

The job world will still accept you, but school won't accept you again. Whenever I feel like the burnout is about to catch me, I take an immediate break and go outside. Take a walk in the sunset. Go to the forest. Run with music playing loudly. Swim. And other things like watching the stars in the silence of the night.

To finally come to an end here...
Do not make yourself feel bad that quickly and try to endure the pain. This is going to make you a better and stronger person.
If you cannot do it anymore (hitting the borders of burnout), take your time and do whatever makes you happy and treat yourself.
Life is not all about work. Were you born to be a worker? No. Were you born to be a slave of others? No.
What is holding you then? Let go of all the stress (for a minute). You are free.

You are a great person.
Do not forget that.

Like someone else already mentioned here, remember that interview goes both ways: youre there to gauge wether workplace suits you or no. Always ask to meet teamleads/project leads or potential colleagues before accepting the job and try talking with them.

I applied to 3 jobs and in all of them managers did put a brave face and told me lots of bs just to get me accept the job. Managers live in their own world, sometimes they dont even know what you will be working on.

Once I accepted a job and got stuck with a perfectionist teamlead for 8 months which could have been avoided given I had the chance to catch the bad vibes during the interview.

Another time I accepted a job and had to work with a backend guy for one year and his accent was so thick+stuttering that I had trouble in understanding anything he says. Every conversation felt like trivia contest. I wish I had knew that stuff before accepting the job

Just randomly had a though from when I was in high school and one of my mates asked me why you would use try catch instead of an if statement...

You know those moments when you stand still, close your eyes, rub your temples and just exhale... Yeah one of those moments...

(Don't ask why this popped in my head, happened like 5 years ago ¯\_(ツ)_/¯)

//run every weekday afternoon
public void workIsOver(int hoursOvertime){

int beerCount = 1;
if (hoursOvertime > 1){
beerCount++;
}

startCar();

int timeHomeMinutes = 20 + Traffic.getTimeLostStuckInTrafficToday();
if (timeHomeMinutes > 40) {
beerCount++;
}

Boolean finallyAtHome = true;

if (goToFridge.checkStock("beer") < beerCount){
Log.e("Dude","WTF?");
}
drink("beer");

while (!girlfriendAtHome){

if (stash != 0){
Joint joint = new Joint(stash);
joint.blaze();
} else {
Log.e("Dude","Seriously?");
}

startAndroidStudio();
workOnSideProject(getCurrentSideProject());

}

girlfriend.communicate();
new AsyncTask<>(thinkAboutCodingInBackground()).execute();

if (bedTime){
try {
doSomeBedroomPartying();
} catch (NullPointerException e) {
Log.w("Sorry","not today");
}

activity.finish();

}
}

So I was just watching a show with subs and see this line:

"So just try and catch me!"

The first thought that came to mind was:

try {}
catch {}

What is it with certain colleagues who "wanna write C, not C++"

Motherfucker if I see another malloc in the code I will physically asssault you.

Like damn we're failing to teach people C++ badly when a newcomer from university, who had 2 semesters of "C++" doesn't even understand RAII.

And how in gods name do software engineers with *decades* of experience get so stuck on old technologies?

Like I've seen them write 3 nested try-catch to make sure a delete is called or some mutex is unlocked....

If youre in the position of teaching others C++, please stop teaching C first.

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

I started learning Golang today and really like it.

The error handling is *excellent*. It always works the same way and is standardized, unlike the hell that NodeJS error handling is (.catch(), try).

Modules confused the fuck out of me. I eventually figured out how they worked, but Go really doesn't try to make it easy to have multiple source folders...

I'll probably be re-writing my Discord Bot in Golang soon. Being able to have just one binary output will make things infinitely easier. Compile-time variables are another feature that's nice and easy to implement.

The goal is only having to upload a single binary to deploy on production from my CI script that has all keys and stuff inside. Feels good to finally throw all that old bad JS code out and starting completely fresh.

there's a special place for people who write empty catch blocks INTENTIONALLY ..

try{

... do something that may produce NPE;

} catch {Exception fuckYou){

// go die in a fire

}

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

When you've spent hours debugging a problem of session not being saved and there is no error. And then you find this in the code:

try{
save_session();
}catch(Exception $e){}// added by another member of the team

🙈😖🖕🏻

(Keep in mind I am 16 and I have never had an internship or a job)

I have a potential internship that I can partake in over the summer. It is a mainly front-end job and it is paying 15-20$ an hour. However, the one catch but they use WordPress to code all of their client's sites. I have tried to use WordPress before and I have not had much fun. I feel it is more confusing than it has to be. Should I try again and relearn it to get some early job opportunity and expand my portfolio or should I try freelance work instead?

If you vote WP could you link some good ways to learn it?

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 ..
}

!rant
Small refactor. Which resulted in the confident removal of a comment that said:
// will this fail?

Ah. Like a breath of fresh air.

There is someone in our building who urinates like a watering can.; all over the place. Do you think I will get caught if I try to get a DNA match, or install a CCTV to catch the culprit?

OK people, I don't need a novel written for every line of code, but PLEASE STOP trying to tell me that "yOuR coDe sHouLd bE sELf dOcUmeNtiNg aNd cOmMenTs mEaN iT's aUtoMaTiCaLLy bAd". That's a bunch of BS. I can't begin to tell you how many times I've saved my own butt by dropping a "this call can't be awaited; causes the library's internal API to throw an error" comment in my C#, or a "can't use double quotes here; doesn't work right for some reason" line in my JavaScript. Sometimes there are very good but un-obvious reasons why something was done a certain way, even though it looks like it could be done better. And don't try to tell me "the tests will catch it". Let's be realistic here, nobody has 100% test coverage on any project that's much more than "Hello World". And even if the tests DID catch it, why waste the time when you could just write a comment?

P.S.: This is not directed at anyone on here specifically. It's directed at all the devs I've met IRL and the comments I've seen on SO, who think that comments must be bad.

Found this on fb~

while( me.getStatus() != Status.RICH){
try{
Project p = createProject();
wait();
me.setStatus(p.getStatus());
}catch (GaveUpException e){
me.setStatus(Status.404);
}
** Warning: code unreachable **
System.out.println("I'M RICH!");

let gfInput = '';
try {
gfInput = getInput('Will you marry me? ')
if(gfInput == 'Y'){
// KISS HER
}else{
throw {msg: 'she dumped you.', code: 'red'}
}
} catch( err ) {
//if err.code !== red . just cry but if red... uh oh
if(err.code == 'red'){
// GOTTA DO SOME DAMAGE
let msg = {
sender: 'anonymous',
recipients : ['dad', 'mom', 'brother', 'sister', 'uncle'],
messageBody: '****ntha has been fucking some dude...'
}

sendText(msg);
}
} finally{
// send ****ntha a good bye message
var msg = {
sender: 'pk359',
recipients: ['****ntha'],
messageBody: 'I invite you ****ntha to my wedding with your best friend *licia. PEACE, bit*h'
}
sendText(msg)
}

How to write a proper Hello World program in Java:

public class ProperJavaProgram {
    public static void main(String[] args) {
        try {
            // Write the hello world file
            List<String> lines = Arrays.asList(
                    "#include <stdio.h>",
                    "int main() {",
                    "printf(\"Hello World!\\n\");",
                    "return 0;",
                    "}"
            );
            Path file = Paths.get("awesome-program.c");
            Files.write(file, lines, Charset.forName("UTF-8"));

            // Execute the file
            executeCommand("cc awesome-c-program.c -o awesome-executable");
            executeCommand("./awesome-executable");
        } catch (IOException e) {
            System.out.println("You're screwed, just use Java and get over it. " + e);
        }
    }

    public static void executeCommand(String command) {
        try {
            Process p = Runtime.getRuntime().exec(command); // Run the process
            BufferedReader stdInput = new BufferedReader(new InputStreamReader(p.getInputStream())); // Get the output
            String s; // Print out the output
            while ((s = stdInput.readLine()) != null) {
                System.out.println(s);
            }
        } catch (IOException e) {
            System.out.println("You're screwed, just use Java and get over it. " + e); // UR SCREWED
        }
    }
}

Am i whiny or is resilience so glorified in this field?

I am a junior developer. I was assigned with two projects together with a friend and a senior. My friend and I finished our assigned tasks way before the deadline. Fast forward, my senior got reassigned to a different project since we are lacking with manpower. Naturally, his transactions were assigned to me and my friend. And my goodness, his existing codes are a piece of shit! It's all over the place. His variable naming is shit, his codes are all around the place, his codes doesn't even follow our company's coding standards, no try catch, a lot of unsafe practices. In short, cleaning his code is a pain in the ass and my friend and I got really busy with cleaning his mess. The testing of our system is really near but I just thought that maybe he's really busy with the other project that's why the quality of his codes deteriorated.

He's not. One day, I saw his in discord that he's playing during work hours lol. And the worse part is that he is playing with our boss! YES. DURING WORK HOURS. I got mad but I couldn't say anything because he is really tight with the boss.

Later on that day, we had our meeting. I was surprised when my boss told me that she's expecting that the excel part of our system is already finished. A little background here, my boss asked me to study Excel VB. However, I didnt get to study that much because I was so busy fixing bugs and after that came the cleaning of our senior's shit codes.

So I tried to say these things to my boss but I was cut out by the same senior shouting "You can do it!" over and over again. No one listened to what I was trying to say! And to make it even worse, the boss had a very proud look on her face and she even had the audacity to tell me that I'm lucky I have such a good support system. I dont.

Now, the company is planning to put me in a very demanding project. I havent finished cleaning up my senior's codes, I havent started anything with the excel and the deadline is next week!

The boss told me that even if I enter the other project, that I will still be responsible for the Excel part of our system. So fucking shoot me in the face.They were telling me that I should have a good time management system, that I should be flexible, that I should adapt easily, yada yada yada. She just makes you feel bad about yourself if you're not as 'flexible' as her.

The thing is, even if I have the best time management techniques in the world, if you bombard me with a shitload of tasks, then I won't be able to do it properly! I don't even take breaks anymore! I work literally 8 hours a day, even more than that. And I dont understand, why the hell is she overworking me when her friend (the senior dev) is just playing during work hours?

Another funniest thing is that she told us that when we encounter technical problems, we should ask our senior dev. Oh boy, if only she knows how shitty his codes are.

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.

I am learning java at school and my teacher asked me to make a work on JTA (java transaction API). There's not a lot of tutos on it on the web so I say to myself "go on, give it a try, you'll only learn by trying."
I finally find how to make the @TransactionType, where to put the @Stateless, my test works, nice. Finally I want to try a case where it shouldn't work, just to be sure the rollback works well. The test goes and... NullPointerException. Wtf ! Normally, my catch is supposed to, well, catch the error !

And finally, I was just stupid. My catch worked great. But I put a "throw e" inside.

Now I wanna hides under blankets, cry, eat cake and never see my coworkers again.

Try...
Catch!

No error handling at all, not even a single try catch. Program crashes when the wind changes direction. Previous developer developed his test plan around his bugs. 😭

class Ex extends Slut {
Boy[] boyfriend;
Ex(){
boyfriend = new Boy[2];
boyfriend [0] = new Me();
try{
boyfriend [1] = new Boy();
} catch(HeFoundOut e) {
boyfriend [0] = null;
}
}

Life will be much easier if we can use "try and catch" while doing something. Yes, just like programming language.

! Rant

Quick tip for those of you struggling with a error or bug you can't fix.
But that doesn't effect functionality.
Just wrap the code inside a try catch block and don't do anything inside the catch 😂😂. Saved me a lot of hours in my projects.

Nah I'm joking. Don't ever do this

try{
// some code
}catch(Exception ex){
MessageBox.Show(ex.Message);
}

even in Visual Studio

try, try until you succeed. if you fail there is always catch....

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.

try {
m_tick++;
}
catch(...) {
m_tick = 0;
}

someone was very confused...
yes, m_tick is an unsigned builtin type

Look what the screen tells you. Learn to read the errors and try to catch them.

bool showUpLateToWork=true;
bool rememberHeadPhones=false;
String DayOfWeek=Tuesday;
int hoursSpentOnPhoneLastNight=
int productivity = 100 - hoursSpentOnPhoneLastNight;
if(showUpLateToWork)
missStandup();
}
if(rememberHeadPhones)
Productivity +=10
Else
Productivity -=50;

While (hourOfDay(now()) <17)
{
drinkMntDew();
discussDataQualityIssuesWithBusiness();
lookThroughTonsOfPoorlyWrittenCodeForDefectThatBusinessWantsFixedYeasterday();
dieOnTheInside();
curseProjectTeamForPassingCrapCodeToMaintainaceTeam();
cry();
curseComputerApplicationsForNotResponding();
visitBathroomWhileLurkingDevrant();
}
goHome();
while (!asleep && hourOfDay(now()) > 17)
{
playWithPuppy();
qualityTimeWithMyWife();
pkayLeagueOfLegends();
netflixAndChill('litterally');
for (int i =1; i <=5; i++)
showLoveUsingLoveLanguage(i);
try
{
makeBaby();
} catch
{
learnPatience();
}
cuddle();
if(!wifeAwake)
checkDevrant()
}

Empty try-catches are so frustrating. At least log the damned error!

Be me, get a consultant job, go to a supposedly great client that has fame of getting scouted by Google. (attn: I doubted all this shit before I started)

Learn the basics by a awesome mentor and trial/error stuff at the same time to get the hang of things, after that was done, I noticed there was no documentation whatsoever, code is spaghetti and your documentation, good luck!

Royal spaghetti, you can't make heads or tails of it, dev code in production, empty try/catch blocks, empty statements, if (true)... (incl. their core classes)

Keep in mind this is a multi milion dollar company...

Someone please understand my pain...

Null Pointer Exception

Null Pointer Exception,
you're in a class of your own.
I will try and catch you,
each instance you're thrown.

Null objects expel you,
because you are vile.
I dread that I'll c you,
when I attempt to compile.

Like the grim reaper,
you destroy lines of code.
And so to you,
I dedicate this ode.

You have no remorse
for those who won't test.
As a result,
I need to confess.

From time to time,
when there's no time waste.
I must rely
on cut and on paste.

Although we're acquainted,
I really must mention.
You're not my friend,
Null Pointer Exception.

try {
thesis.defend();
} catch(TimeoutException reached) {
thesis.attack();
throw new Thesis aimedAt(theProfessorsFaces);
}

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.

So I wrote an algo in python3 for a challenge in codechef.com but it raised this exception !
If I put the input() built-in method in a try/catch , how do i know what the input was in order to pass the test case?

A time I (almost) screamed at co-worker?
Too many times to keep up with.

Majority of time its code like ..
try
{
using (var connection = new SqlConnection(connectionString))
{
// data access code that does stuff
}
catch (Exception e)
{
// Various ways of dealing with the error such as ..
Console.WriteLine("Here");
ShowMessage("An error occured.");
return false;
// or do nothing.
}
}

Range of excuses

- Users can't do anything about the error, so why do or show them anything?
- I'll fix the errors later
- Handling the errors were not in the end-user specification. If you want it, you'll have to perform a cost/benefit analysis, get the changes approved by the board in writing, placed in the project priority queue ...etc..etc
- I don't know.
- Users were tired of seeing database timeout errors, deadlocks, primary key violations, etc, so I fixed the problem.

On my tip of my tongue are rages of ..

"I'm going to trade you for a donkey, and shoot the donkey!"
or
"You are about as useful as a sack full of possum heads."

I haven't cast those stones (yet). I'll eventually run across my code that looks exactly like that.

Why the fuck do i need to propose try-catch to an contractor, so he can fix his application, because its crashing if the input is non-conform to the specs?
Oh and before you ask. The application is a application that processes and sanitizes invoices.

I'm freaking out. The snack bar is shown in every non iOS device...
On iOS the error never get caught 😖 and the try/catch won't work too.

My job environment is either fucked up or am too young to understand what a job life is.
I was hired to intern for a startup having 2 main bosses/founders . one of them is mostly administrative and comes to office daily. He sets some tasks and i have to complete them, as soon as possible or sometimes till a deadline. He has little knowledge about the complexity of wotk so usually he says "just complete it as soon as possible so we could release it" but we haven't pushed any updates since i joined (of course i have completed some tasks, but they are just not pushed to the release version)

The other one , as i ranted previously is a completely different story.I think he is an elder bro or senior of the other boss,but he is just a superman: dealing with the distributers, commanding the hardware ppl, discussing with the othr boss, handling the server and most importantly the guy who wrote all the code i am working on. So he comes extremely rarely(1 or 2 days / week) , tries to communicate with me , but is immediately diverted by some other call/person and goes away.

The problem is : am feeling a little helpless. They give me tasks and i start working on them with excitement .( I don't believe myself to be a terrible beginner: i have been learning/working on android development for past 1 year, i know my things. And even if i don't, i know how to search/debug and produce results) . So as usual, i start and try to apply my skills / search for things i don't / try to understand his large,overwhelming and confusing codebase and at the end am stuck at some point where i don't understand what to do next. Sometimes its a bug which doesn't seems to fix, sometimes its a thing thats in the codebase but i couldn't find or sometimes it's just something i couldn't seem to understand why isn't it working. At that time, I only wish that boss to be here and look at what and how i have done, if its a correct approch and how can we together take it to completion (or simply wtf am i doing wrong, see my shit and tell me) .

But again, the tech boss is busy or wouldn't have time to understand my problem in our short , incomplete meetings. But he or the nontech boss will definitely have the time to ask the sttus of project and pressurise for the "deadline" .

Like today, i was so stuck at this fucking one line error that i couldn't detect that i just messaged him that am leaving for home 3 hours early. He came running and for the first time in history gave me a complete undisturbed time. It was such a small mistake, but i wasn't able to catch on my own. But when i told him, he immediately caught , changed a single line and the code started to work.

I am feeling irritated. Is this all a correct environment?

Found this comment before a try/catch block in some code I was reviewing... seems like I might have to rewrite the whole thing

My boss has been working in web development for roughly 10 years now.

Today he learned about the existence of try/catch in JavaScript and asked me in which browsers it's
supported in 😢

do {
try self.organised = 100;
} catch {
sleep(365*24*60*60);
}

Your mother is so fat, not even a try/catch can catch her.

Recently i learned about pipes in C#. I made 2 simple console apps(client and server) in visual studio. They work flawlessly. After that i made plugin for unity that uses those pipes. (because i want to crunch numbers in .net 4.7 app and display results in unity). Every function in my plugin is wrapped in try-catch block. Unity frezzes/crashes everytime i try to use my plugin 😥

I am a Technical Lead in the department in my company that writes code for our clients that have money but doesn't have the technical expertise to handle the complexities of our own software.

Part of my tasks involve taking care of a few projects written by employees that have left after using third-party tools rather than using our own software. No one else in this department knows these third-party tools, they only know our own, and my *still limited* web development experience means I get dumped these things in my lap.

And I'm SO pissed at these projects and their authors and the manager that let these ex-employees write these things. There is this one project that was managed by two different "developers" (I don't know they deserve this title) at two different times, and it is so riddled with different technologies it makes me want to throw up almost daily.

Don't believe me? Here is a complete list of the dependencies listed in the package.json of this project: babel-polyfill, body-parser, cookie-parser, debug, edge, edge-sql, excel-to-json, exceljs, express, html-inline, jade, morgan, mssql, mysql, pug, ramda, request, rotating-file-stream, serve-favicon, webpack, xlsx, xml2js

What this doesn't even show, is that one part of this project (literally one page) is made using react, react-dom, react-redux, and jade. The other part (again literally one page) is made using Angular and Pug. In case you missed it while picking up your jaw, there's also mssql, mysql, edge and edge-sql. excel-to-json, exceljs, xlsx.

Oh you want *more* juicy details? This project takes the entire data object used by the front-end, stringifies it into JSON, and shoves it into the database *as a single field*. And instead of doing WHERE clauses in the SQL queries, it grabs the entire table, loops, parses the json, and does a condition on it. If even one of those JSON entries gets corrupted, the entire solution breaks because these "developers" don't know what try/catch is.

The client asked for a very simple change in their app, which was to add a button that queries the back-end for a URL, shows it in a modal dialog, after which a button is clicked to verify the link by doing a second query to the back-end before modifying a couple of fields in the page.

This. Took. Me. Two. Months*. Save me. Please, save me.

*between constant context switches between this and other projects that were continuously failing because of their mistakes.