Details
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
-
At my company we have a rule that ticket estimates can only be pointed using numbers from the fibonacci series. So 4 point tickets are not allowed!
We’re also discouraged from giving an estimate larger than 5, and told that tickets need to be broken down into smaller tickets if we think it’s more than a 5.
Also, ticket estimates must include the full amount of time for dev, QA, AND deploy. Given how hard it is to work with our tech stack, few tasks actually fit.
All of this may sound fine in principle, but in practice it’s extremely frustrating. I’ve protested a few times but I’ve been told I’m outvoted and nobody wants to reconsider the decision that was made sometime in the distant past. I was also told that “most other companies do it this way”, so therefore we have to as well.
This is the first company I’ve ever worked at which had this stupid rule. Is it this way at your company? Is this a NorCal tech company thing? I’ve worked at several companies outside of the SV bubble, and never encountered this.6 -
Not a single year passes that the problem of python2 vs python3, as a dependency, doesn’t bite me in the ass. Node modules frequently fail to build, awscli suddenly can’t find the python it needs because homebrew apparently hard-links to python3 in Cellar... Seriously, W T F?! Fuck you python!!!! You fucking assholes!!! Fuck you and go fucking die!!
-
Pro tip for job candidates:
If you push a code challenge to a live hosting service like github pages or S3, don’t give the reviewers a link to the repo!! Instead put the link into the home page and send the reviewer only a link to the live hosted page.
Why?
Because, if you host with github pages, you’re required to use the project path as the domain root. If the reviewer pulls your project and doesn’t bother to read your readme file with the link at the top, he’ll complain that he couldn’t figure out why your project isn’t hosted from the root domain, and he’ll pass on your application.
True story.2 -
Is there any good, developer-friendly alternative to WordPress? So sick of plugins that have no API documentation and still use SVN. Working with PHP is seriously the least of my complaints with WP.
Favorite CMS right now is Lektor but it’s not designed for use with clients and I haven’t figured out a quick solution to make it work for that use case. It’s also very lacking in features, so only suitable for very basic content.9 -
I must assume that whoever designed jinja2 was either on crack, or hadn’t used template systems before. This thing is too fucking complicated, and doesn’t make sense. From their docs:
“Jinja2 supports dynamic inheritance and does not distinguish between parent and child template as long as no extends tag is visited. While this leads to the surprising behavior that everything before the first extends tag including whitespace is printed out instead of being ignored, it can be used for a neat trick.”
My response: “I don’t give a fuck!! I need this fucking website to be fucking done already! I pass data into a fucking template engine, and the engine applies my fucking markdown!! This is bullshit!! Why am I still trying to understand your fucking nonsense?!? AGGJCDJVFD&@!?&@$?)@&!SHHHVBSHK!!!!!!”
*desk flip*
Fuck you to hell you jinja fucker3 -
Dear assholes of the internet. Next time you publish an article/tutorial/story etc, PUT THE FUCKING PUBLICATION DATE AT THE TOP.
I don’t care about your need to be minimalist, FUCK YOU, INCLUDE THE DATE.18