I believe index for the classical need to iterate through an array. E.g.

for (i = 0; I <= arr.length; i++) { var thing = arr[i] … }

So to me it stands for “index” for array lookup.

Before map and iterators were implemented in a lot of languages, this was the defacto way to iterate a list. At least this is how I learned it in java/c back in the day. Nowadays I think most OOP languages including java have implemented the “for … in …” Syntax or similar which deprecates this convention.

I literally would not work for a company if they made me do story points.

We do have a scope rule which is intentionally ambiguous, but the idea is a ticket ought not take more than 3 days, and some can be quicker. We expect the average time to meet our velocity and prioritize accordingly. If an effort seems like it will take longer we try to divide it into smaller tickets.

There may be like 5 tickets a year where this doesn’t hold true and we are ok with it. Nothing to be religious about.

The other issue is the amount of points it is totally depends on who does the work! It’s a garbage system to estimate work. Makes people think they have some sort of idea that is more misleading and harmful than just saying “I don’t know exactly but you can expect it to get done promptly because we’ve taken proper steps to analyze and break down the work to be bite sized and delivered consistently.”

Is php worth hating? I did some in college and didn’t care for it. I don’t remember exactly why though. I built a POC super simple MVC framework and found it really easy to implement. But then I moved on to other stuff (java/ruby/python/js) and promptly forgot about it.

I is short for “index” for a traditional for loop for mapping over an array and looking up by index. J comes after I and is used for nested loops so it doesn’t shadow the outer I.