Joined devRant on 4/27/2020
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
"Pythonists don't comment, they write readable code."
Yea, tell that to the list comprehension with three lambdas22
Newcomer: I can do fizzbuzz in 6 lines of code
Experienced: I can do fizzbuzz in 3 lines of code
Professional: I can do fizzbuzz in 1 line of code
Enterprise: you did not create the user epic for this problem, I can't accept these solutions until you have done this. Please speak with Mike on getting this properly setup. I expect a full report of this by Monday.
Them: but it's Friday...
Enterprise: Get it done. I am not paying your overtime either
As a developer, I WAS love with the concept of WFH. Thankfully, my office has no fixed hours (except for meetings!) and I can work at my pace peacefully. But lately, with WFH becoming mandatory, I can't seem to find time for myself!
Here's what my schedule looks like:
a. Start working at 10am
b. Standup at 11:30am
c. Lunch break at 2am
d. End work at 7pm.
A fairly simple routine but not sure why my team finds it completely normal to call me in off hours and moreover expect me to jump in a call too! I wish it was a 1-day affair. But no. It's a 24x7 day affair. Yes, let that sink in. 24x7.
How I wish there was no COVID and thus no lockdown. At least, people respected the work timings then !5
TFW your client's git policies are so draconian that the dev teams use "develop" as trunk, and completely ignore the release process.
I wrote up 50 pages of git standards, documentation and procedure for a client. Bad indian director 9000 decides the admin (also Indian) who specializes in Clearcase and has no git or development experience is more qualified to decide and let's him set the policy.
FF to today:
- documentation, mostly contradictory, is copy pasted from the atlassian wiki
- source tree is the standard
- no force pushing of any branches, including work branches
- no ff-merge
- no rebasing allowed
- no ssh, because he couldn't figure it out...errr it's "insecure"
- all repos have random abbreviated names that are unintelligible
- gitflow, but with pull requests and no trust
- only project managers can delete a branch
- long lived feature branches
- only projects managers can conduct code reviews
- hotfixes must be based off develop
- hotfixes must go in the normal release cycle
- releases involve creating a ticket to have an admin create a release branch from your branch, creating a second ticket to stage the PR, a third ticket to review the PR (because only admins can approve release PRs), and a fourth ticket to merge it in
- rollbacks require director signoff
- at the end of each project the repo must be handed to the admin on a burned CD for "archiving"
And so no one actually uses the official release process, and just does releases out of dev. If you're wondering if IBM sucks, the answer is more than you can possibly imagine.11
I was asked to present a code I wrote previously. This was not planned. I shared my screen and presented. Things went well.
One employee asked me to search a particular term which was possibly related to an advance topic in the domain we were working on.
I opened Chrome and the first page had a Quora post: "Why my dull co-workers try to act smart and are not yet fired?".