Details
-
AboutWhy have a problem now when I could have a problem later?
-
LocationSweden
Joined devRant on 3/12/2019
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
-
!dev
I’ve been ranting & posting a lot about my career, relocation, work life balance etc. in the last year.
Just wanna say, relocating was probably the best decision I’ve ever made. Professionally and personally..
Although it was a bit scary and I didn’t have any money left after relocating..
It’s 6PM, I’m sitting in the garden, listen to some classical music and don’t spend a single thought on work.
Tomorrow I will arrive in the office around 7:45, I will do my work. My boss recognizes my teams effort and thanks all of us for the work on the end of each sprint.
There are no personal fights in the team, everyone is getting along with the others.
I do some good work, get a good salary and don’t have to mix up work and personal life.
The people here are awesome, everyone is welcoming and supportive.
If everything goes as planned, I’ll be able to buy my dream car by the end of summer because the government doesn’t take all of my money. They take their taxes before I get my salary and the money I get is the money I HAVE..
Ireland is awesome.
At this point: thanks for the Irish guys here who provided information about work and life over here! And also to the other devs who supported me here👍2 -
[long]
When searching for internship via school I found this small startup with this cute project of building a teaching tool for programming. There were back then 2 programmers: the founder and the co-founder.
Then like 1 week before the internship started, the co-founder had a burnout and had to get off the project, while the company was so low on budget the founder, aka my new b0ss, had to work separate jobs to keep the company alive. (quite metal tbh)
It's funny because I'm a junior developer, 100%. I've been coding as a hobby for around 8 years now but I've never worked in a big company before. (No exception to this workplace either)
First project I get: rewrite the compiler. The Python compiler.
"But wait, why not just embed a real compiler from the first case?"
-nanananana it's never simple, as you probably know from your own projects.
The new compiler, as compared to existing embedded compiler solutions out there, needed these prime features:
- Walk through the code (debugger style), but programmatically.
- Show custom exceptions (ex: "A colon is needed at the end of an if-statement" instead of "Syntax error line 3")
- Have a "Did-you-mean this variable?" error for usage of unassigned variables.
- Be able to be embedded in Unity's WebGL build target
All for the use case of being a friendly compiler.
The last dash in the list is actually the biggest bottleneck which excluded all existing open-source projects (i could find). Compliant with WebAssembly I can't use threads among other things, IL2CPP has lots of restrictions, Unity has some as well...
Oh and it should of course be built using test-driven development.
"Good luck!" - said the founder, first day of work as she then traveled to USA for **3 weeks**, leaving me solo with the to-be-made codebase and humongous list of requirements.
---
I just finished the 6th week of internship, boss has been at "HQ" for 3 weeks now, and I just hit the biggest milestone yet for this project.
Yes I've been succeeding! This project has gone so well, and I'm surprising myself how much code I've been pumping out during these weeks.
I'm up now at almost 40'000 lines of source and 30'000 lines of code. ‼
( Biggest project I've ever worked on previously was at 8'000 lines of code )
The milestone (that I finished today) was for loops! As been trying to showcase in the GIF.
---
It's such a giant project and I can honestly say I've done some good work here. Self-five. Over-performing is a thing.
The things that makes me shiver though is that most that use this application will never know the intricates of it's insides, and the brain work put into it.
The project is probably over-engineered. A lot. Having a home-made compiler gives us a lot of flexibility for our product as we're trying to make more of a "pedagogic IDE". But no matter that I reinvented the wheel for the 105Gth time, it's still the most fun I've had with a project to date.
---
Also btw if anyone wants to see source code, please give me good reasons as I'm actively trying to convince my boss to make the compiler open-source.
Cheers!4 -
!rant
if you're someone who grades code, fuck you, you probably suck. Turned in a final project for this gis software construction class as a part of my master's degree (this class was fuck all easy, I had two weeks for each project, each of them took me two days). We had to pick the last project, so I submitted final project proposal that performs a two-sample KS test on some point data. Not complex, but it sounds fancy, project accepted. Easy money.
I write the thing and finish it, it works, but it doesn't have a visualization and that makes the results seem pretty lame, even though its fully functional. SO I GO OUT OF MY FUCKING WAY to add a matplotlib chart of the distribution. To do that, at the very bottom of the workflow, I define a function to chart it out because it made the code way more readable. Reminder, I didn't have to do this, it was extra work to make my code more functional.
Then, this motherfucker takes points off because I didn't define the function at the very beginning of the code... THE FUCK, DUDE? But, noobrants, it's "considered best prac--" nope, fuck you, okay? This class was so shit, not once was code style addressed in a lesson or put on any rubric - they didn't give a shit what it looked like - in fact, the whole class only used arcpy (and the csv mod once), they didn't teach us shit about anything except how to write geoprocessing scripts (in other words, how to read arcGIS docs about arcpy) and encouraged us to write in fucking pythonwin. And now, when the class is fucking over, you decide to just randomly toss this shit in, like it was a specific expectation this whole time? AND you do this when someone has gone out of their way to add functionality? Why punish someone who does extra work because that extra work isn't perfect? Literally, my grade would have been better without the visualization.
I'm not even mad at my grade - it was fine - I just hate inconsistency in grading practices and the random raising and lowering of expectations depending on how some grader's coffee tasted that morning. I also hate punishing people for doing more - it's this kind of shit that makes people A) wanna rip their eyeballs out, and B) never do anything more than the basic minimum expectation to avoid extra unwanted attention. If you want your coders to step up and actually put work in to make things the best they can be, yell at a grader to reward extra work and not punish it.4 -
Currently I live in the city Utrecht. Right now a terrorist attack is happening next to my school with explosives and I'm at school right now.
Waiting it out now!16 -
Customer support story time: (swearing in Dutch because it sounds more fun but it's general swearing so no translation needed I think (will translate the non obvious parts)
Me: good morning, how can I help you?
Client: hello, I have a question for you.
Me: go ahead!
Client: alright so.... one sec, let me turn off my music.
Client: hey Google
.
.
.
Client: hey Google
.
Client: Heeeey Gooooooogle
.
Client: HEY GOOGLE, GODVERREDOMME
.
Me: 😆
.
Client: REAGEER GODVERDOMME. "HEY GOOOOGLE"
.
.
Client: VIES VUIL TYFUS DING, LUISTEREN. HEEEEEY GOOOOOOGLE
.
.
Client: JA GODVERREROMME, LUISTER GEWOON, FUCKING KUT DING. *SHOUTS WITH ANGRY VOICE* "HEY GOOGLE HALLOOOO LUISTEEEEEREEEEEN" (oh for fucks sake, LISTEN fucking piece of shit)
Me: *desperately trying to keep it together*
Client: IK DOE HET ZELF WEL JEZUS GODDOMME *FOOTSTEPS, MUSIC STOPS* (Translation: I'll do it myself, fucking hell)
.
.
.
Client: finally, sorry for that 😅
Me: *still trying to control myself* no problem!15 -
My JS function is now lazy loading, expressive, and uses 12 fewer lines of code! 😃
It no longer works, but
... no one is perfect. 😅3 -
Interviewer: what's your biggest strength?
Me: I'm a fast learner.
Interviewer: what's 11*11?
Me: 65.
Interviewer: Not even close. Its 121.
Me: Its 1211 -
Friend: You make games right?
Me: Yea I try to atleast, why?
Friend: I have this cool idea for an MMORPG with fantasy elements and dragons and stuff!
Me: Well thats a lot of work, just setting up serv-
Friend: We can have a bunch of cool stuff like Sandbox stuff, Guild battles and 100v100 pvp
Me: As I was trying to say, it would requi-
Friend: OH We need space for atleast 10 thousand people on each server!
Me: ... Good luck buddy!6 -
So at school, we were supposed to do an exam through a third-party software that is supposed to block the user from searching the answers in a web browser.
We install the fucking software, lord and behold nothing works and the software keeps crashing...
The teacher insists that we are going to use this piece of shit software. One hour goes by and now the software made everyone's PC go black.
Someone suggests just doing the exam either through an ordinary browser or just by hand.
The teacher that just wasted one hour of fucking exam time lets out this big sigh and finally caves in...
And in a couple of weeks, we are going to use this shitty spaghetti-coded fuckfest called software for something called the "National tests"...
May Sky-daddy bless my classmates' souls and my own4 -
Developer: We have a problem.
Manager: Remember, there are no such things as problems, only opportunities.
Developer: Well then, we have a DDoS opportunity.53 -
"You gave us bad code! We ran it and now production is DOWN! Join this bridgeline now and help us fix this!"
So, as the author of the code in question, I join the bridge... And what happens next, I will simply never forget.
First, a little backstory... Another team within our company needed some vendor client software installed and maintained across the enterprise. Multiple OSes (Linux, AIX, Solaris, HPUX, etc.), so packaging and consistent update methods were a a challenge. I wrote an entire set of utilities to install, update and generally maintain the software; intending all the time that this other team would eventually own the process and code. With this in mind, I wrote extensive documentation, and conducted a formal turnover / training season with the other team.
So, fast forward to when the other team now owns my code, has been trained on how to use it, including (perhaps most importantly) how to send out updates when the vendor released upgrades to the agent software.
Now, this other team had the responsibility of releasing their first update since I gave them the process. Very simple upgrade process, already fully automated. What could have gone so horribly wrong? Did something the vendor supplied break their client?
I asked for the log files from the upgrade process. They sent them, and they looked... wrong. Very, very wrong.
Did you run the code I gave you to do this update?
"Yes, your code is broken - fix it! Production is down! Rabble, rabble, rabble!"
So, I go into our code management tool and review the _actual_ script they ran. Sure enough, it is my code... But something is very wrong.
More than 2/3rds of my code... has been commented out. The code is "there"... but has been commented out so it is not being executed. WT-actual-F?!
I question this on the bridge line. Silence. I insist someone explain what is going on. Is this a joke? Is this some kind of work version of candid camera?
Finally someone breaks the silence and explains.
And this, my friends, is the part I will never forget.
"We wanted to look through your code before we ran the update. When we looked at it, there was some stuff we didn't understand, so we commented that stuff out."
You... you didn't... understand... my some of the code... so you... you didn't ask me about it... you didn't try to actually figure out what it did... you... commented it OUT?!
"Right, we figured it was better to only run the parts we understood... But now we ran it and everything is broken and you need to fix your code."
I cannot repeat the things I said next, even here on devRant. Let's just say that call did not go well.
So, lesson learned? If you don't know what some code does? Just comment that shit out. Then blame the original author when it doesn't work.
You just cannot make this kind of stuff up.105 -
Ok so we went to a graphic class seeking graphic designers for our game.
We pitchted our 3d fast paced speed running game. With highscores and shit. (We only have a week to create this game)
This fucking moron in the back of the class starts to rise his hand asking:
Is this a MMORPG?
Me: No this is no fucking MMORPG?!
Him: But i only want to design to a MMORPG
Me: Well we are not doing a fucking MMORPG..
Him: Can you change it to an MMORPG please?
Me: WTF NOOO!
Him: Okey you sure?
Me: YES... smh
Like why the fuck shall we change an idea to something litrally impossible to make in a week and that will fucking crash and burn like every Michael Bay movie ever...4