• 0 Posts
  • 4 Comments
Joined 2 years ago
cake
Cake day: July 4th, 2023

help-circle
  • Getting a later special meeting request with the ceo, at one company, because he wanted feedback on their interview process itself. He then offered me a different job and I had to decline cuz I already accepted another (this was a few weeks after the initial decline I gave)

    In another case they just fast tracked me and I ended up declining the job anyways (didn’t like the job)

    I’m full time employed but I still do occasiobal interviews to keep feelers out for how the market is. But I typically decline most offers cuz they’re not good enough to get me to actively quit my current job.



  • In the “right” use case, story points should just represent relative effort.

    The hours dont matter, its more about ranking how challenging a task is, in order to help the manager rank the priority of tasks.

    You should have typically 2~3 metrics:

    1. Points, which represent relative effort of the task to the other tasks you are also ranking.

    2. Value, how much value does doing this task provide, how important is it

    3. Risk, how risky is it that this might break shit though if you make these changes (IE new features typically are low risk since they just add stuff, but if you have to modify old stuff now your risk goes up)

    If you have a good integration testing system automated, Risk can be mostly removed since you can just rely on your testing framework to catch if something is gonna explode.

    Then your manager can use a formula with these values to basically rank a priority order for every ticket you now scored, in order to assess what the next thing is that is best to focus on.