Then send and email at 6:30 with your new changes, CC the team and your boss.
Also check email as soon as you wake up. Reply to anything you can resolve quickly.
The whole middle of the day is yours to fuck around.
2 Likes
Yea that seems like how it goes. I envisioned it a little differently.
eh sorta. Last time I had a job that shitty/lax I quit every day at 2pm and then spent the time making my board game site. Or, you know, lifting or something.
I ninja edited because i’m paranoid but i hear you. I’m just glad my job isnt very stressful.
I think it’s time i had a pet project, but I don’t have any good ideas
WTF? Are you just saying that you get your two tasks done for the sprint, and then the rest of the time you just say, “I helped Aaron with x, today I’ll help Betsy with y”? Or do you not even pick up any work at all for the sprint? I’m the scrum master for our team, and mostly I have to beat the engineering manager over the head to stop changing and adding shit one hour after the sprint planning meeting. Just got a new manager, who is very bossy and micromanaging, so I’m butting heads with him constantly.
When we first started doing scrum at our place my team had this scrum master who mandated insane shit such as once you start a sprint the order of the backlog is set in stone and you can’t move anything around even if you run into roadblocks. So if you got stuck on the first ticket in the sprint, the sprint was pretty much over lol.
I’ve also dealt with the strict WIP thing a few times and it mostly just devolved into watching other people code via skype or whatever or them watching me code while we shot the shit. It was not quite as dumb as the “backlog can’t be altered” thing but it was up there. Luckily we have a much better scrum master now who doesn’t try to impose any of that crazy shit so things have improved dramatically.
Wow yeah, that is insane. In my company, people just leave teams like that, and HR really forces managers not to prevent people from changing teams, so they can’t build their weird little dungeons of insanity. In my scrum team, the new manager is trying to impose his will a little, and not with totally insane ideas, but I’m going to try to steer it more towards a consensus, and not try to change too much at once.
I’m on a devops team so luckily we don’t do any of the scrum BS. We just have tickets that come in and get assigned to various people, with varying priorities and deadlines. Magically, the work still gets done.
This week’s gonna be rough though. I already finished all my work items at 10:30 this morning.
I asked for more to do, but got told to work on something I’ve pretty much finished.
I have not seen a single web page load faster on Safari, than Chrome. Ever. My boss uses Safari and it drives me nuts. Yes of course our sites sucks on Safari, every site sucks on Safari!
I use safari on my mobile browser and it’s been fine. Porn sites get a little fucky though.
I like browsing with safari on work machines because it’s not tied to my google account.
Porn should be fucky, no?
3 Likes
In our support channel today Karen was complaining about links that she put into our web application not working right. After some discussion, I determined what the problem was. The links were to…
C:\\KarenHome\video.wmv
2 Likes
I wrote a poker equity calculator that kind of works, and I’m looking for ideas about how to speed it up. Heads up pre-flop equity calculations for given hole cards take about 1.4 seconds for 10,000 random boards but take about 4.5 minutes to evaluate every possible board.
I already made one big speedup by switching from an algorithm that breaks seven-card hands into all possible five-card hands and evaluates them one at a time to a new algorithm that directly evaluates the strength of seven-card hands. I’ve also made some small speedups by minor optimizations to the inner loop (the evaluate_trial function).
The next thing I want to try is building up a dictionary that maps seven-card hands to ranks. The dictionary would start out as blank, but would be built up over the course of an equity calculation. I can reduce the number of entries in the dictionary by ignoring rank order and ignoring specific suits. E.g., KsAhJs and JhKhAc could both be coded as something like A1K2J2. This should result in some speedup as long as the time to encode a hand is less than the time required to fully evaluate a hand.
Would be interested in any other ideas. The code is here if anyone would like to take a look.
I remember that blog! I read it before the author took it down. My lasting memory of it is the first and still the only time I’d ever seen the use of the “yield/return” construct in C#, and sadly I have to report I have not had the opportunity to use it in the ~12 years that passed since I discovered it there. IIRC he used it to pass hands to an unsafe external assembly more efficiently for evaluation, but I could be mis-remembering.
lol 
ed, gtfo.
Why flagged?
Not sure, but maybe a few people are deciding for everyone that LM/WN isn’t allowed to post here.
1 Like