Details
Joined devRant on 5/4/2018
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
College force us to study the ancient computer graphics method for a whole year. Its damn boring and complicated. Why should we study it..?😐2
-
Few weeks back a MNC rejected me as a fresher. The interviewer was quite rude. "your are not good enough", his words just took the soul out of me 😑. He said my portfolio website was done by somebody else. yeah! fine mate. We will meet soon4
-
You know you’re busy when you open the microwave to heat up the coffee that you didn’t have time to drink and find yesterday’s coffee that you heated up for the same reason.3
-
Legacy code.
Honestly though, this is some of the better legacy code I've worked with at this company. It's a nifty alert system wherein you can trigger sending messages to subscribers of that alert via whatever means (phone/email) they've entered.
I'll save you the technical analysis of its internals, but suffice to say it's actually pretty nice, with good separation of concerns, internal logic hidden away, dead-simple public interface, etc. documentation is kinda crap, but it exists (!), so that's a nice change.
but.
For some unknown and bloody bizarre reason, the thing breaks when a user wants both sms AND email notifications. Either by themselves work totally fine, but both together? nonono. Email alerts give ArgumentErrors, so something internal isn't correct, and SMS alerts complain about uninitialized Twilio::Error constants.
but.
they both work fine otherwise?
also, the two notification preferences aren't stored on the same object anywhere. if a user wants both, the user creates two AlertContact objects with different info, and when performed, the Alert basically iterates over these and does its thing for each, so there is no knowledge shared between them. totally should work the same regardless.
idfgi.
ALSO.
AND THIS PART REALLY PISSES ME OFF.
WHEN THERE'S AN ERROR, THIS THING DOESN'T LOG IT. IT STRINGIFIES THE ERROR OBJECT (basically just extracting the message) AND INSERTS THAT INTO THE DATABASE INSTEAD. WHAT THE CRAP.
So, I don't get a stack trace, line number, or anything. just the basic error message. instead of my alert text. because of course that makes sense and totally helps debugging.
aklsjfak;sldfj.
legacy code.5 -
Coworker: Hey, you made some changes over here in module X?
Me: Yeah. The old way was deprecated and we need to switch all of our modules over to the new way.
Coworker: Okay. I'm working in module Y now. When are you going to get to it and make those changes?
Me: ... I sent out an email and a message in group chat saying we all need to make these changes as we find them.
Coworker: Uh-huh. So when are you going to update this? It's blocking me.4 -
My mobile phone provider called me and offered me a new contract containing more data volume.
Customer service: 'Your current contract has only 1.5GB data volume. That's not much. With this you can only send 1 or 2 pictures and that's it.'
Me: 'What kind of pictures do you use / send? 😨'11 -
*me reading @Alice 's cake recipe
"biscuits violently dismembered"
"dark as our souls."
"slowly and painfully molten butter"
"press your victim tightly against it"
"before it freezes to death"
"Put it into the oven and torture your victim"
"so it fills the hole in its heart"
Well... Wut. Da. Frigging. Heck. I've. Just. Read.8 -
So, as I figure out my post-high school life and delve into the world of coding, I finding myself with a question for you seasoned veterans in the field.
Regardless of what I like more, what makes more sense in the current climate of the industry - specializing in back end or front end, of going more full stack?13