Funny seeing you here :) Also hear hear!

It would suck right now to be a conservative with so much of world politics now being between centre left and radical right, with no simple conservative position left.

I asked gpt for code to aim a heliostat

It needed a module to get the sun's position, it used sun::alt:: azimuth which doesn't exist rather than Astro::Coord::ECI::Sun

It needed a module to calculate mirror angle between the Sun's altitude and azimuth and the target altitude and azimuth. It left that commented out rather than selecting the altitude halfway between Sun and target and azimuth between Sun and azimuth

It turns out there's precious little on the internet on how to aim a mirror, partly because it's not popular, partly because it's dead simple

At least put the box back. Chicken bones have crap-all capacitance

It's safe to consider radio technology as deep magic. The metal box may have been adding just the right amount of capacitance to offset something about where the system was mounted

Sometimes tight trousers have excellent pockets (menswear doesn't give a toss about pockets ruining the line of the clothing, even on skin tight clothing), like the man in the op photo with his phone deep in his right pocket

• I prefer to wear socks
• I used to be fat, so skin tight shirts don't look good on me
• I like button up shirts
• In cool weather when I wear long trousers, I prefer not to have my ankles frozen
• In hot weather I'm keeping as much of my legs bare as available men's bottom wear allows

All in all I don't like that style. I knew a boy who liked that style as a youth, he was a arsehole

I'm a systems analyst, or in agile terminology "a designer" as I'm responsible for "design artifacts"

Our designs are usually unambiguous

I play Seven Days To Die (a zombie apocalypse game) and there are quests like clear out all the zombies in this place.

Some places show you the main loot room through an armoured window will before you can get to it legitimately. There will be an armoured door with half a million hit points to tell you not to bother.

So in one such game I dug through the 1000 hit point wall next to the armoured door, looted the loot, and did the zombie extermination path backwards

They worked well for us, we were updating a big system or adding functionality to it and a lot of the features were similar enough that we could reliably break the work down to sub-single sprint chunks and assign consistent story points to them

Though I have only been in one team that lasted more than 3 sprints relatively intact, and it's only that team that got good at story pointing work

The idea with story points is you assign them consistently, so the team's velocity is meaningful.

One team might deliver 30 points in a sprint while another delivers 25 and they deliver the same amount of work

Of course management want to be able to use story points for tracking, they want to compare teams using them, so you end up with formulas for how many points to assign

Of course if they score you on points, they get more points, not more work and story points become useless

The estimate is not a promise, it's a guess. I prefer to estimate in sprints because that's about the resolution we can have confidence in, but management want hours so my process is to estimate the number of hours in a sprint (73.5 for us) plus one sprint

200% overruns are common, especially when requirements change significantly