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
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuck
Buy Now
-
*pops open some Chinese USB Bluetooth dongle*
*finds a chip inside that seems to be a controller*
"Google, what's the datasheet for this thing?"
> Your search - 653uw1f1 - did not match any documents.
I'm doomed... 😟
Finding Easter eggs is hard you say? Try a datasheet 😑35 -
it's funny, how doing something for ages but technically kinda the wrong way, makes you hate that thing with a fucking passion.
In my case I am talking about documentation.
At my study, it was required to write documentation for every project, which is actually quite logical. But, although I am find with some documentation/project and architecture design, they went to the fucking limit with this shit.
Just an example of what we had to write every time again (YES FOR EVERY MOTHERFUCKING PROJECT) and how many pages it would approximately cost (of custom content, yes we all had templates):
Phase 1 - Application design (before doing any programming at all):
- PvA (general plan for how to do the project, from who was participating to the way of reporting to your clients and so on - pages: 7-10.
- Functional design, well, the application design in an understandeable way. We were also required to design interfaces. (Yes, I am a backender, can only grasp the basics of GIMP and don't care about doing frontend) - pages: 20-30.
- Technical design (including DB scheme, class diagrams and so fucking on), it explains it mostly I think so - pages: 20-40.
Phase 2 - 'Writing' the application
- Well, writing the application of course.
- Test Plan (so yeah no actual fucking cases yet, just how you fucking plan to test it, what tools you need and so on. Needed? Yes. but not as redicilous as this) - pages: 7-10.
- Test cases: as many functions (read, every button click etc is a 'function') as you have - pages: one excel sheet, usually at least about 20 test cases.
Phase 3 - Application Implementation
- Implementation plan, describes what resources will be needed and so on (yes, I actually had to write down 'keyboard' a few times, like what the actual motherfucking fuck) - pages: 7-10.
- Acceptation test plan, (the plan and the actual tests so two files of which one is an excel/libreoffice calc file) - pages: 7-10.
- Implementation evalutation, well, an evaluation. Usually about 7-10 FUCKING pages long as well (!?!?!?!)
Phase 4 - Maintaining/managing of the application
- Management/maintainence document - well, every FUCKING rule. Usually 10-20 pages.
- SLA (Service Level Agreement) - 20-30 pages.
- Content Management Plan - explains itself, same as above so 20-30 pages (yes, what the fuck).
- Archiving Document, aka, how are you going to archive shit. - pages: 10-15.
I am still can't grasp why they were surprised that students lost all motivation after realizing they'd have to spend about 1-2 weeks BEFORE being allowed to write a single line of code!
Calculation (which takes the worst case scenario aka the most pages possible mostly) comes to about 230 pages. Keep in mind that some pages will be screenshots etc as well but a lot are full-text.
Yes, I understand that documentation is needed but in the way we had to do it, sorry but that's just not how you motivate students to work for their study!
Hell, students who wrote the entire project in one night which worked perfectly with even easter eggs and so on sometimes even got bad grades BECAUSE THEIR DOCUMENTATION WASN'T GOOD ENOUGH.
For comparison, at my last internship I had to write documentation for the REST API I was writing. Three pages, providing enough for the person who had to, to work with it! YES THREE PAGES FOR THE WHOLE MOTHERFUCKING PROJECT.
This is why I FUCKING HATE the word 'documentation'.36 -
I would like to put easter eggs in the software I work on.
I just doubt the surgeons/nurses that use it will appreciate when operating.5 -
Anyone here put Easter eggs in their code, and care to share examples?
I made a custom script to rotate a log file once a day in my program. So at the bottom of the roll I added a nice little print. See attached.
18 -
my habit to inspect any nicely done apps to understand how they achieve such greatness, I never felt more welcome when I visit the console, until i found Quizlet.
great place to leave easter eggs.. :)
6 -
Do you leave easter eggs at any of your projects? If yes - what are the most interesting of them?28
-
Things that made me happy today:
- solving 3 bugs
- being able to help out a colleague
- my contract being extended (yay!)
- chocolate Easter eggs
Things that I didn't like today:
- that fucking strong wind I had to bike through
- it's Monday.
- the rough tone of conversation in the office today. One of my (generally very nice) colleagues showed his good mood today in making even more sexually explicit jokes / comments than usual today. Even though most of them they were not directed at me directly, I was bad at coping with that today. If this continues, I'll mention it to him, and hope he'll understand. When our Gitlab went down at 5 I decided to call it a day.
Thanks for your time if you read until now. Have a nice day2 -
I love to put Easter eggs in my code.
Sometimes I use references from star wars >.>
Anyone else have Easter eggs they'd like to share?18 -
It is time to hide all the Easter eggs in your apps!
I wonder what easter egg will be in the devRant app🤔12 -
!rant
I damn love devs. The humor, the devs easter eggs...
Have you ever wondered what 'git' stands for?
try 'man git' ;)4 -
OMFG I don't even know where to start..
Probably should start with last week (as this is the first time I had to deal with this problem directly)..
Also please note that all packages, procedure/function names, tables etc have fictional names, so every similarity between this story and reality is just a coincidence!!
Here it goes..
Lat week we implemented a new feature for the customer on production, everything was working fine.. After a day or two, the customer notices the audit logs are not complete aka missing user_id or have the wrong user_id inserted.
Hm.. ok.. I check logs (disk + database).. WTF, parameters are being sent in as they should, meaning they are there, so no idea what is with the missing ids.
OK, logs look fine, but I notice user_id have some weird values (I already memorized most frequent users and their ids). So I go check what is happening in the code, as the procedures/functions are called ok.
Wow, boy was I surprised.. many many times..
In the code, we actually check for user in this apps db or in case of using SSO (which we were) in the main db schema..
The user gets returned & logged ok, but that is it. Used only for authentication. When sending stuff to the db to log, old user Id is used, meaning that ofc userid was missing or wrong.
Anyhow, I fix that crap, take care of some other audit logs, so that proper user id was sent in. Test locally, cool. Works. Update customer's test servers. Works. Cool..
I still notice something off.. even though I fixed the audit_dbtable_2, audit_dbtable_1 still doesn't show proper user ids.. This was last week. I left it as is, as I had more urgent tasks waiting for me..
Anyhow, now it came the time for this fuckup to be fixed. Ok, I think to myself I can do this with a bit more hacking, but it leaves the original database and all other apps as is, so they won't break.
I crate another pck for api alone copy the calls, add user_id as param and from that on, I call other standard functions like usual, just leave out the user_id I am now explicitly sending with every call.
Ok this might work.
I prepare package, add user_id param to the calls.. great, time to test this code and my knowledge..
I made changes for api to incude the current user id (+ log it in the disk logs + audit_dbtable_1), test it, and check db..
Disk logs fine, debugging fine (user_id has proper value) but audit_dbtable_1 still userid = 0.
WTF?! I go check the code, where I forgot to include user id.. noup, it's all there. OK, I go check the logging, maybe I fucked up some parameters on db level. Nope, user is there in the friggin description ON THE SAME FUCKING TABLE!!
Just not in the column user_id...
WTF..Ok, cig break to let me think..
I come back and check the original auditing procedure on the db.. It is usually used/called with null as the user id. OK, I have replaced those with actual user ids I sent in the procedures/functions. Recheck every call!! TWICE!! Great.. no fuckups. Let's test it again!
OFC nothing changes, value in the db is still 0. WTF?! HOW!?
So I open the auditing pck, to look the insides of that bloody procedure.. WHAT THE ACTUAL FUCK?!
Instead of logging the p_user_sth_sth that is sent to that procedure, it just inserts the variable declared in the main package..
WHAT THE ACTUAL FUCK?! Did the 'new guy' made changes to this because he couldn't figure out what is wrong?! Nope, not him. I asked the CEO if he knows anything.. Noup.. I checked all customers dbs (different customers).. ALL HAD THIS HARDOCED IN!!! FORM THE FREAKING YEAR 2016!!! O.o
Unfuckin believable.. How did this ever work?!
Looks like at the begining, someone tried to implement this, but gave up mid implementation.. Decided it is enough to log current user id into BLABLA variable on some pck..
Which might have been ok 10+ years ago, but not today, not when you use connection pooling.. FFS!!
So yeah, I found easter eggs from years ago.. Almost went crazy when trying to figure out where I fucked this up. It was such a plan, simple, straight-forward solution to auditing..
If only the original procedure was working as it should.. bloddy hell!!8 -
Expectation: I'm going to spend today debugging my app
Reality: adds 10 new features, 30 got commits and some Easter eggs. No bugs fixed. -
When you're feeling extra 'peechy' debugging coworker's crap.. I mean code..
Bonus: Anyone get's the reference?? Might have spelled it wrong.. But fuckit! I no longer care.. :\
3 -
Three of us doing a project for free for our web-dev teacher at university. Looking back at that project I think we did a terrible job, we built an ugly, monolithic application with Express, MongoDB, Pug and Vue.
It was a CMS for a local church and the best part of the project was including some hidden easter eggs accessible only by setting some cookies manually in the browser.
Although we did the project for free, I think we all have been learning a lot of valuable things and we also tried out new stuff, like the Kanban board and a few aspects of the scrum way. The most interesting part of this was learning all of it by ourselves, because our web-development teacher couldn't really help in web-development... -
Fun idea;
Who else thinks @dfox should release a version of devrant for Easter with Easter egg codes for free/discounted swag hidden all over the app?5 -
!rant
What kind of Easter eggs have you guys added to your projects (personal or work)?
There was one I added to a command-line utility for work that, as long as you ran the right command on an OS with a GUI, would open a browser and navigate to "Never gonna give you up" on YouTube. 😎 -
Have any of you ever hidden easter eggs in you're code?
I imagine it's frowned upon in corporate, but how about you're own projects?
I love easter eggs by the way.5 -
Do you Place Easter eggs in your projects? If so, where and how do you place them on web projects? :P6
Top Tags
Weekly Rant
View