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
Search - "what's the ending?"
-
I once worked Tech Support for a point of sale software package. There was really no internal help desk, so we got all of those questions as well.
One day our front receptionist that her computer is being really weird and she can't type - it keeps inserting 3s in the middle of what she is typing.
I take the short walk down the hall to her desk and see that, indeed, a never ending string of 3s is being input to her screen.
"I can't figure out what's wrong." she says.
Then I reach over and remove the edge of an open binder whose edge was resting on the 3 key and enter key on the num pad.
"That should fix it."
Walked back to my desk.1 -
2^40=1099511627776
Why did I not realize this until playing this game (pair 2 of the same kind to get the next) for about an hour....3 -
I suddenly just want to retire.... Job just feels like never ending work.... Can't find time for a break... And well biggest fear in taking a vacation is the amount of work that piles up while I'm gone...
Maybe I suddenly just have burn out... But suddenly just going ah fck... What's the point of all this....
Sometimes wonder, if I didn't have parents around would I just quit and and just do whatever I want until I run out of money...
How many years that would take....10 -
The worst of Agile and Sc(r)um: All those people knowing the right way(™) to do it. Endless discussion about useless tooling: the proper use of the custom workflow in Jira, on when and how to create sub tickets. The hour-less meta-discussions on what should be discussed where and when (what's subject of the backlog refinement, retro, etc), the roles: the PO's, what he should do, cannot, the PM's. Who is allowed to pull a ticket to the sprint or not. How many reviewers need to acknowledge a pull request. To and fro. Pointless, but fought with heart and blood, full of sound and fury, signifying nothing.
And everywhere I hear: "In my previous company, we did Scrum like.. and it worked perfectly!"
Some of you might remember my rants on Mr. Gitmaster, with whom I thought I'd made my peace. Guess what? He's now a team member and turning into Mr. Agile - a more severe reincarnation! As our company starts flogging that dead horse of Agility, he seems to feel strong tailwind. Our team lead would constantly cut his monologues, but he's now on holiday, so we have no escape from the never ending: "In my previous company..."
If it was so great, why didn't you stay?
We are not allowed to pull a ticket to the sprint unless every team member is notified? I don't fucking care. If our software fails on customer's machines and I can fix it, I will do if there is a ticket, if it's in the sprint or not. Screw Scrum, if it is getting in the way of it. You can waste your hours discussing horseshit, I want to sit at my desk, deep in the test-compile loop and ship some fucking code.3 -
I think discussing / talking about whether your educations are useful or not is always gonna be a never ending debate.
Each person has their own unique way to nurture their true potentials. In my case, I always "thought" that taking college in Computer Science is such a waste of time and money, even I still try to survive with it these 3 years. In my first year, I fight a lot with my parents because I always said I wanna drop out and just get to work. But in the end...I still continue my journey for 3 years and yeah...I currently struggling to graduate. Maybe, after graduate, it will be a waste of time and money like how I thought about it. But I also learn that taking college journey have teach me a lot of things, like meeting so mane different kind of friends / people, time-management, etc. Maybe those Study Materials in Class will be forgotten in just a few years after I graduate, but those other life-lessons I believe will remain in myself for a long time...
Some people said if you are someone who wanna work hard, study hard, and have the grit to learn by yourself and committed to become a developer by yourself, you don't need college. But if you are someone who still find out your way, still figuring out whether it's the best choice to take computer science or not as a carreer, and you don't wanna waste time doing nothing, just get yourself to college.
The point is...it's just how we try to find out what's actually worked for us even if it's not the best choice.rant studying computer science computer science study life college life life motivation life of programmer wk145 collegelife college wisdom2 -
Never Ending Project
"What's make software development great?"
"What's it?"
"We must catch bugs all the time."
"Oh..."1 -
Okay so being a developer is mostly like playing a never ending game of whack-a-mole with BUGS, you think you have fixed one until few more pops up like a bad case of acne.
But you know what's even worse? When you finally get something working, and you're feeling all proud of yourself, and then someone comes along and tells you that it's not "visually appealing" enough. "Can't you just add some more glitter and unicorns to the homepage? Oh, and can you make it look like it was designed by a unicorn who majored in art?"12 -
1) Have a plan for what's going to be talked about (and what will not be mentioned)
2) Could this meeting be an email or done async? Then don't schedule a meeting
3) Send out the calendar invite at least 72 hours before. Include details in the title and description, such as join link and if video will be on or not
4) Join 5 mins early to ensure everything is working
5) Start the meeting right on time, no matter who isn't there
6) If someone joins late, don't recap what's been mentioned
7) End on time, the time that was set when the calendar invite was sent, ending early is also fine
8) At the end say thanks, and know who will send out the notes which include tasks mentioned and the deadline. As well as who to contact if have any questions
9) If a select portion of the meeting attendes is going to have another meeting regarding this, then meet elsewhere
10) Actually send those notes before the end of day -
Once a React aficionado, twice the frustration we endure,
In the realm of libraries, React's problems seem impure.
With Svelte's elegance and grace in our sight,
Let's vent about React, as day turns into night.
Boilerplate Overload, a monotonous affair,
Classes, constructors, lifecycle steps we declare.
In Svelte's simplicity, we find a breath of fresh air,
Just markup and magic – a coder's love affair.
Complex State Management, React's Achilles' heel,
Redux, Mobx, and their massive code appeal.
Svelte's state handling is a cinch, for real,
No more tangled webs of logic to conceal.
Unnecessary Re-Renders, React's performance woe,
Countless updates, like a never-ending show.
Svelte updates what's needed, like a pro,
Efficiency and speed, in its radiant glow.
Verbose Syntax, JSX's verbosity on display,
HTML in JavaScript, causing dismay.
Svelte's concise template syntax lights our way,
No more endless tags, just code that's here to stay.
Lack of Truly Reactive Behavior, React's hurdle high,
Hooks to wrangle, state to satisfy.
Svelte's reactivity, no need to question why,
It just works, oh my, oh my.
Ecosystem Complexity, React's sprawling sprawl,
Choices galore, making us bawl.
In Svelte's world, simplicity is the call,
A coherent ecosystem, it has it all.
Learning Curve, React's mountain to climb,
Classes, hooks, context, a hill of time.
Svelte's gentle curve feels sublime,
A smoother path to code, so fine.
Tooling Overkill, React's complex array,
Build tools, linters, configs in disarray.
Svelte's streamlined setup leads the way,
No more intergalactic code buffet.
Debugging Headaches, React's mysterious realm,
Complex state, intricate components overwhelm.
Svelte's predictable model, a soothing helm,
Debugging becomes a peaceful realm.
In the end, React, a complex labyrinth we explore,
Svelte's elegance and simplicity we adore.
If only React could learn, its problems to deplore,
A brighter future, for React we'd implore.3