Details
-
LocationChina
Joined devRant on 8/19/2017
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
-
Why I love devRant? Cause it redirects me to my good old browser after clicking on a link instead of open such a f*****g build in shit!5
-
I'm about to finish a website where people can upload their university notes and download others in exchange. In the future I'll try to upgrade it to an academic hub or something like that.11
-
Everybody wants passionate developers, then they stick a product owner in your face and strips you of self-control...3
-
Bought this a while ago thinking i would read, never ended up doing it. Now i am actually trying to learn it, and this shit is out of date8
-
Back in the day when I was a junior developer, I somehow got hired by this guy who asked me to code his entire platform from scratch. I was being paid a junior dev salary, being asked to do senior dev work, and unfortunately I needed the money, so I didn't want to turn the job down. So I did what any junior dev would do in the situation... I decided to experiment and ended up with an insanely inefficient codebase.
For some stupid reason I thought that a good DB model would be to pull one record from the DB at a time, and then just repeat the method in a loop as needed. Keep in mind I was a self-taught junior dev. The backend worked great during development, and after 3 months of developing we decided to add a lot of data in the DB for further testing, and... you guessed it... the platform slowed down like shit!
Moral of the story... u get what you pay for, so hire great talent and pay them well! And also that self-taught junior devs don't know that the f@*k they are doing sometimes.5 -
Motherf.. they didn't make a select all option, WHY do you NOT have select all when there could be thousands of options
fml3 -
Mom : why were you late?
Me : Got lot of bugs in office.
Mom : Is everyone alright? Did you kill them?
Me : No mom we fix them.
Mom : I thought we kill them.
How humane are you guys.9 -
Skipping all the "Women in IT" sessions my company tries to enforce, along with ditching such questions like "What attrocities did I experience related to my gender, during my first month of working here?"
Well, fuck, we are few, all right. But can I just be a dev instead of a girl dev, please?
I discussed this whole feminism trend with many of the women colleagues, but not one of them could mention a case where they were distinguished by their gender. Ever.5 -
Biggest hurdle for me is living with Delayed Sleep Phase Disorder. A neurological disease which affects the way my body makes melatoline. Basicly I have a set wake/sleep pattern which is extremely hard to deviate from. My sleeptime is 7am and wake up time 4pm.
I worked for 8 years forcing myself to be at the office at 9am because thats the social norm. Got 2 burnouts due to being sleepdeprived, various other issues and whatnot.
Finally discovered whats wrong with my body 3 years ago and found a awesome job at a company where I develop very complex systems which communicate with various stock exchanges.
Best part is that I work on my own and have the deal that I work about 3 to 5 hours a day on site. Then I go home have dinner, do some netflix and chill with the misses and after that I have the whole night just for me. When the world is asleep I am writing code, developing a complex system with NOBODY around me who can annoy me!
For me, this is the biggest hurdle I've overcome.12 -
"What idiot left a console.log in a function call spitting out the value of the onchange......oh fuck, that was me "
-
I couldn't sleep. I was staring at the blinking cursor. A slow, comforting blinking. Like everyone else, I had become a slave to the JavaScript ecosystem. If I saw something like a new build system, or a new framework, I had to have it.
My client changed the requirements again. I'm in pain.
- "You want to see pain?" my colleague said. Go read Apple support forums. That's pain.
I became addicted. Every time I died and every time I was born again. Resurrected.
During the night, I was crying in the Apple forums for an official answer that would never come. During the day, I was surfing StackOverflow to fix my problems. You get "single-serving" friends there. They help you, you help them, and then you never see them again.
- "Then you install Stack and boom, you're done. It's that easy to go functional."
That's how I met him.
- "You know why they make so many javascript frameworks?"
- "No, why?"
- "So that they can distract you while they put backdoors in them. So that you don't have time to check all of their code".
- "You are by far the most interesting "single-serving" friend I've ever met"
Then, my hard disk died. Of course, I didn't have backups: nobody has enough space for all those node_modules folders. All my addictions, lost.
Then I wrote him. If you asked me now, I couldn't tell you why I wrote him. We chatted a lot.
- "It's late, I should really go search another hdd on ebay"
- "Ebay? You called me so you could have my old hard disk."
- "No, I..."
- "Come on."
He sent me his old hard disk. It was a 256MB hard disk, but it was fine for running Arch. Then he asked me to rant about my problems in front of him.
- "I want you to rant as hard as you can"
- "Are you serious?"
We ranted all night about our bosses and clients and their fucked up requests. We kept in touch, and after a while more people were ranting with us. Every week, he gave the rules that he and I decided.
- "The first rule of devRant is -- you don't talk about devRant. The second rule of devRant is -- you don't talk about devRant."
I like to think this is how devRant started. This might also be the reason why we never see @trogus, only @dfox. A lot of shit still needs to happen.8 -
I've every been a Arch Linux fag. It's my main OS from 5 years. With a small parenthesis of two months of FreeBSD recently, I've used before Arch Kubuntu, Ubuntu, Fedora KDE, OpenSolaris (randomly), CentOs, plus a lot of others distro for tests.
But I've never tested Debian!
So I've installed it on my small server.
Oh... My... God.... It's fantastic. PACMAN >>> apt, but damn it's really stable and out of the box even if minimal. A very surprise. I think it can be my favorite remote Linux for a long time....
But a question rises. Why with a father like Debian... Ubuntu after the 11.04 is such a shame? The last I've tested is the 12.04 I think, but I've hated it, and I hate it even now. (Crash, driver not found, apt problem, very heavy repos and my internet sucks, UNITY, etc...)
Ubuntu, what happened to you ...? With Kubuntu 8 you were such a good guy...4 -
Job offer: "All employees will be provided Macbooks"
Nope! Just nope.
Let your dev chose their equipment, thank you very much.
If they want a Linux laptop, buy them one. If they want a Windows workstation, give it to them. And if and only if they want a Macbook, give them a Macbook.
I used to work in two companies having the requirement to use a Macbook for two years.
I know its pros. I know its cons. My conclusion for me: Never again!13 -
WordPress related, get ready for some disgust.
So today early in the morning my boss forwarded me an email from a client, it was about a bug, and asked me if I can have a look at it and fix it.
"Yaay, WordPress!" I thought and opened the page containing the mentioned bug. She wrote that in the italian version of the page, users can select dates in the calendar, which should be disabled, like in the german version.
So yeah, I opened the code. Everything in the function looked perfect. Really. And the Data was also correctly set in the backend of WP.
The function was only 3 lines of code:
- Get the german post ID of the current post (german or italian) by its ID (using a Polylang function)
- Get an Advanced Custom Fields field by name and from a post with the ID from before
- json_encode its content and echo it to a JS var for initialization and later use in some AngularJS.
No fucking missing semicolon, it was fucking perfect like a sunset with your soulmate.
So I tried to find the bug with my personal way of debugging:
"Shitstream Debugging"
When a creek suddenly is full of water mixed with shit, walk upstream through the turds until you reach clear water. This is where the bug is.
=> So I first looked at the HTML source: Turds.
=> Then the ACF field content: Still turds.
=> Then the ID of the german post: Shit stain and turds (var_dump: null)
=> Please god at least $post->ID? Nope, fart smell and turds.
=> Nothing more to check: Clear fucking water and the flowery smell of 99 devVirgins
So it replaced $post->IT with get_the_ID() and it worked like a charm.
Afterwards I feel stupid, but $post->IT worked all the times before...
Conclusion:
FUCK YOU WORDPRESS YOU UGLY PIECE OF HUMAN-CENTIPEDE-PROCESSED-DOGFART.
Thanks for your patience.
Only one beer was sucked dry during the writing of this fucking rant.2 -
I've stopped cursing when this happens. I've just grown to accept it as a natural part of my life.8
-
Literally the first rant I made when I joined devRant was about this very piece of advice.
Me: "The build in testing is broken, this is how we fix it"
PM: "They haven't noticed yet, work on the feature request"
https://devrant.io/rants/225727/...2 -
Finally did it. Quit my job.
The full story:
Just came back from vacation to find out that pretty much all the work I put at place has been either destroyed by "temporary fixes" or wiped clean in favour of buggy older versions. The reason, and this is a direct quote "Ari left the code riddled with bugs prior to leaving".
Oh no. Oh no I did not you fucker.
Some background:
My boss wrote a piece of major software with another coder (over the course of month and a balf). This software was very fragile as its intention was to demo specific features we want to adopt for a version 2 of it.
I was then handed over this software (which was vanilajs with angular) and was told to "clean it up" introduce a typing system, introduce a build system, add webpack for better module and dependency management, learn cordova (because its essential and I had no idea of how it works). As well as fix the billion of issues with data storage in the software. Add a webgui and setup multiple databses for data exports from the app. Ensure that transmission of the data is clean and valid.
What else. This software had ZERO documentation. And I had to sit my boss for a solid 3hrs plus some occasional questions as I was developing to get a clear idea of whats going on.
Took a bit over 3 weeks. But I had the damn thing ported over. Cleaned up. And partially documented.
During this period, I was suppose to work with another 2 other coders "my team". But they were always pulled into other things by my Boss.
During this period, I kept asking for code reviews (as I was handling a very large code base on my own).
During this period, I was asking for help from my boss to make sure that the visual aspect of the software meets the requirements (there are LOTS of windows, screens, panels etc, which I just could not possibly get to checking on my own).
At the end of this period. I went on vacation (booked by my brothers for my bday <3 ).
I come back. My work is null. The Boss only looked at it on the friday night leading up to my return. And decided to go back to v1 and fix whatever he didnt like there.
So this guy calls me. Calls me on a friggin SUNDAY. I like just got off the plane. Was heading to dinner with my family.
He and another coder have basically nuked my work. And in an extremely hacky way tied some things together to sort of work. Moreever, the webguis that I setup for the database viewing. They were EDITED ON THE PRODUCTION SERVER without git tracking!!
So monday. I get bombarded with over 20 emails. Claiming that I left things in an usuable state with no documentation. As well as I get yelled at by my boss for introducing "unnecessary complicated shit".
For fuck sakes. I was the one to bring the word documentation into the vocabulary of this company. There are literally ZERO documentated projects here. While all of mine are at least partially documented (due to lack of time).
For fuck sakes, during my time here I have been basically begging to pull the coder who made the admin views for our software and clean up some of the views so that no one will ever have to touch any database directly.
To say this story is the only reason I am done is so not true.
I dedicated over a year to this company. During this time I saw aspects of this behaviour attacking other coders as well as me. But never to this level.
I am so friggin happy that I quit. Never gonna look back.14 -
Tech head fires a mail few days company is planning a hackathon. Overnight at office, with food, music and home drop offs in morning. We devs feel excited we will get time to work on our personal projects and complete them.
Yesterday, tech head fires a mail about the topics. Guess what? The topics are projects which company needs to scale up... Image recognition and text extraction. Selenium. Esign.
Now I am searching for an excuse to skip the hackathon...4 -
A friend suggested that I'd start learning a scriptable language like Ruby, Python or JavaScript instead of beginning with HTML and CSS, until I feel comfortable with programming.
I want to be a web developer and Ive learned some HTML.
So, any opinions?9 -
I find webpack very complicated especially when it comes to understanding config.js file.
I might give 4th try later.9 -
"Older versions are more stable"
The whole concept of LTS in development pisses me off.
Delayed upgrading, whether it's the language itself, dependencies or tooling, does just one thing: It makes future upgrading way more difficult, often to the point where the company eventually runs into this maintainability wall, and gets stuck in old, unsupported versions.
"But... stability!" — The tiny chance that the newer version has such serious stability regressions that it negatively impacts your own product doesn't weigh up against the clusterfuck you fall into if you push the task too far into the future.
You can relatively easily assess a new major language version using benchmarks and unit tests. Predicting the repercussions of staying on PHP 5.4 or Python 2.7 for another year, predicting the impact of upgrading the codebase later, that is almost impossible.
I'm not saying you should live on the bleeding edge in production, but as soon as a new stable version of a core technology is released, just fucking drop everything you're doing and port those deprecated methods!7 -
"Anything that can be done in GUI is better than in terminal"
Yes it's wrong and stupid. Let Microsoft fans disagree.16 -
When it keeps happening every time but you're too lazy to fix it because you always remember it at 7am when you want to close the computer and go get some sleep...
Ugh...1