• 7 Posts
  • 78 Comments
Joined 5 months ago
cake
Cake day: June 2nd, 2024

help-circle





  • ever had to rebuild a sprint because Jira failed to properly migrate the old cards over to the new one, but instead throws them all into the backlog randomly and now you have to hunt them down over the next hour?

    No, never. Did you maybe not select the ‘move to new sprint’ option when closing the old one?

    how about when you’re writing an update to a card and you’re two paragraphs in with log examples and the UI decides to dump your entire content when you accidentally click outside the wysisyg?

    That has never happened to me, either.




  • Teach this to your manager: At the beginning of a task, uncertainty is highest. Under no circumstances should you give an estimate in ‘man-hours’. Even days is too precise. The first estimate should be in months or years (of course depending on the size of the project). Then, as your insight into the project grows, you refine that to months, then weeks, later days. A vague estimate with a lower and a higher bound is way more useful to your manager than a ridiculously ‘precise’ but highly speculative number.

    This lesson was brought to you by either “Code Complete 2” or “Rapid Development” by Steve McConnel, and by my former manager who wanted projects estimated in minutes.









  • I don’t know why. Maybe the typings for it are just fucking bad. Or maybe d3 is very hard to use “correctly”, but still works most of the time even if invoked incorrectly (I doubt that). Or maybe d3 is so complex that the typings need to be complex, too, even if you don’t use the complexity (the type retured from selectAll has four type parameters, half of which are undefined by default, the other half, null).