Damn! Team Just do it!!!
Belle! Stop saying "I do declare" for your constants! It's not valid syntax!
this post was submitted on 22 Aug 2023
647 points (98.2% liked)
Programmer Humor
19584 readers
1938 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
Here is an alternative Piped link(s): https://piped.video/watch?v=hkDD03yeLnU&
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source, check me out at GitHub.
Those 2 things are not fucking related lol
yeah they are. it outputs the IP address on a rad spinning dial with Sonic the hedgehog next to it
There was a lot wrong with VB but I miss being able to WYSIWYG together basic UIs and get back to Real Coding(tm)
VB was great for learning coding.
Slap some buttons down and have them do math. I made an NPC generator for every RPG I ran in VB as a teen. I felt like I was a hero putting out something that looked "good" for the time.
woa.
Thanks i hate it
joke aside, story point can be quite arbitrary
My team has being trying an approach where instead of story pointing, we break everything down into the smallest incremental tasks we reasonably can and use number of tasks overall as the metric instead of story points.
In theory it's meant to be just as accurate on larger projects because the larger than normal and smaller than normal tasks all average out, and it save the whole headache of sitting around and arbitrarily setting points on everything based mostly on gut feeling.
I remember reading a study done across some large organizations that showed this approach was more accurate than other estimation techniques. Makes sense to me.
Huh. That's such a simple and obvious approach, I'm kinda mad I've never thought of it lmao. It seems like you're essentially breaking everything down to a 1 (or as close as you can get it), which is probably a more accurate measurement anyways. Neat.
When I teach story points (not in an official Agile Scrum capacity, just as part of a larger course) I emphasize that the points are for conversation and consensus more than actual estimates.
Saying this story is bigger than that one, and why, and seeing people in something like planning poker give drastically differing estimates is a great way to signal that people don't really get the story or some major area wasn't considered. It's a great discussion tool. Then it also gives a really rough ballpark to help the PO reprioritize the next two sprints before planning, but I don't think they should ever be taken too seriously (or else you probably wasted a ton of time trying to be accurate on something you're not going to be accurate on).
Students usually start by using task-hours as their metric, and naturally get pretty granular with tasks. This is for smaller projects - in larger ones, amortizing to just number of tasks is effectively the same as long as it's not chewing away way more time in planning.
I'd rather story points than my company's WAG time estimates 🥲
Man, this whole thread is like a foreign language to me.
Haha they're just different ways of estimating the difficulty of a work task. Story points are a kind of estimate that are represented by a number. The larger the number the more difficult the task.
My company uses WAG (wild ass guess) time estimates where we have to actually say how long we think a task is going to take in a matter of days or weeks. It sounds fine but programming tasks are notoriously hard to estimate since you have to consider so many different factors. I'm especially bad at it so I'd much prefer just saying "this task is an 8 because it seems hard"
It'll take 20 hours. Unless it's harder than I thought. Or it's easier than I thought. Or it's exactly as hard as I thought except there's one little thing that I get stuck on for 5 hours.
I recently estimated a task to take a couple hours but it ended up taking a week. Hadn't considered having to update a bunch of other teams services with new proto schemas and making sure they were deployed before our own service 🙃
Who's gonna reverse-sort that kanban into a linked list b-tree?
Let's also have you do a master rank codewars kata... on the whiteboard. You have 30 minutes.
We have been getting pressure from customers whether or not this substring is a palindrome
SPEZ!!??!?!?!?!?!! WHAT ARE YOU DOING ON LEMMY!?!??! GO BACK TO REDDIT!!!!1!1!11!1!1!1!