1,273 karma · joined September 19, 2010
I’m with a provider now who is phasing them out.
We do T-shirt sizes mapped to numbers, because recording effort in numbers lets you get an avg etc...
- plan in 2 week chunks
- estimate in points (relative size to something you've already done), emphasis on consistent estimates for each dev.
- make sure you define what 'done' means, and make sure it relates to what exactly you are trying to measure (Eg just coding effort, work till feature can ship?, etc). This is probably the most tricky bit.
- capture total velocity every 2 weeks and eventually use the avg for future planning
- review the entire process and modify things that take a lot of time for devs.
I did not know. Does anyone have pointers or examples on this?
z/OS (aka OS360 aka MVS) supports programs going back to the 60s and I just talked with a DE at IBM who is still using a program compiled circa Apollo 11 mission.
That's terrifying!
Safari cannot open the page because the server cannot be found.Not certain but chances are very high with the new class of opioids.
ddevault on Feb 15, 2019
"EFAIL" is an alarmist puff piece written by morons to slander PGP and inflate their egos. The standards don't need to change to fix the problems it mentions. The proposals help... marginally. The problem is not and was never with OpenPGP, it's with poorly written email clients (e.g. all email clients).“Microsoft is teaming up with OpenAI to exclusively license GPT-3, allowing us to leverage its technical innovations to develop and deliver advanced AI solutions for our customers”