What Are You Doing Right Now
-
Ironically the guy that I was hired to take the position of (he got promoted) might want his old position back and I would take his promotion. MAYBE, I'll believe it when I see it in writing.
edit: just heard this today.
-
On the train home. Woop its the weekend
-
It is Friday, so that means loads of Sodium news and releases today. Getting set up for that this afternoon. We do about half of our weekly releases on Fridays, so lots to keep us busy.
-
@quixoticjustin said in What Are You Doing Right Now:
It is Friday, so that means loads of Sodium news and releases today. Getting set up for that this afternoon. We do about half of our weekly releases on Fridays, so lots to keep us busy.
Yep. Already doing my best to make sure everyone knows I will be unreachable all night tonight.
-
@quixoticjeremy said in What Are You Doing Right Now:
@quixoticjustin said in What Are You Doing Right Now:
It is Friday, so that means loads of Sodium news and releases today. Getting set up for that this afternoon. We do about half of our weekly releases on Fridays, so lots to keep us busy.
Yep. Already doing my best to make sure everyone knows I will be unreachable all night tonight.
Have y'all considered going to just one release a week, such as every Friday night or Sunday night or so? Might be easier for bug tracking.
-
@dbeato said in What Are You Doing Right Now:
Restoring a Failover Cluster for a friend...man I hate 2 servers and 1 SAN....
Everyone hates an IPOD once it crashes.
-
@dustinb3403 said in What Are You Doing Right Now:
Everyone hates an IPOD
-
Been dismissed from jury duty since 9:30, but have to report back at 1:15. This has to be some kind of war crime.
-
@nerdydad said in What Are You Doing Right Now:
@quixoticjeremy said in What Are You Doing Right Now:
@quixoticjustin said in What Are You Doing Right Now:
It is Friday, so that means loads of Sodium news and releases today. Getting set up for that this afternoon. We do about half of our weekly releases on Fridays, so lots to keep us busy.
Yep. Already doing my best to make sure everyone knows I will be unreachable all night tonight.
Have y'all considered going to just one release a week, such as every Friday night or Sunday night or so? Might be easier for bug tracking.
Not really an option and actually the smaller releases more often helps due to the fact that with less content per release we're able to track how each small release performs more easily. Doing mass releases only so often results in a lot of issues, such as there being so much content that it takes longer to iron out all the bugs, or a new release being built on an older release that wasn't fully ironed out so the new release has issues that are actually occurring due to the old release. Ultimately SDLC's are heading towards more often releases not releases that are further apart.
Besides with the development team behind this project being so small it really honestly is very comfortable for us to be doing this small releases, have them be bombarded when we announce them and iron things out as we go.
-
@nerdydad said in What Are You Doing Right Now:
@quixoticjeremy said in What Are You Doing Right Now:
@quixoticjustin said in What Are You Doing Right Now:
It is Friday, so that means loads of Sodium news and releases today. Getting set up for that this afternoon. We do about half of our weekly releases on Fridays, so lots to keep us busy.
Yep. Already doing my best to make sure everyone knows I will be unreachable all night tonight.
Have y'all considered going to just one release a week, such as every Friday night or Sunday night or so? Might be easier for bug tracking.
Bigger releases mean more breaking bugs all at once with less time to catch and address them. Mitigating bug issues is a key reason for more releases. That way bugs come out faster, get fixed faster and releases are way smaller. So we are troubleshooting tiny bits of code changes instead of big groups of changes, to find where bugs exist.
Think about it like a system that is broken. If you just patched one library, or just patched hundreds and the system and something breaks, it's really easy to find the problem when you only updated one thing. But if you updated your whole system and something breaks, the problem could be anywhere and you are far more likely to be trying to find multiple issues at once that might even interact with each other.
-
@quixoticjustin said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@quixoticjeremy said in What Are You Doing Right Now:
@quixoticjustin said in What Are You Doing Right Now:
It is Friday, so that means loads of Sodium news and releases today. Getting set up for that this afternoon. We do about half of our weekly releases on Fridays, so lots to keep us busy.
Yep. Already doing my best to make sure everyone knows I will be unreachable all night tonight.
Have y'all considered going to just one release a week, such as every Friday night or Sunday night or so? Might be easier for bug tracking.
Bigger releases mean more breaking bugs all at once with less time to catch and address them. Mitigating bug issues is a key reason for more releases. That way bugs come out faster, get fixed faster and releases are way smaller. So we are troubleshooting tiny bits of code changes instead of big groups of changes, to find where bugs exist.
Think about it like a system that is broken. If you just patched one library, or just patched hundreds and the system and something breaks, it's really easy to find the problem when you only updated one thing. But if you updated your whole system and something breaks, the problem could be anywhere and you are far more likely to be trying to find multiple issues at once that might even interact with each other.
Beat you to it
-
@quixoticjeremy said in What Are You Doing Right Now:
@quixoticjustin said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@quixoticjeremy said in What Are You Doing Right Now:
@quixoticjustin said in What Are You Doing Right Now:
It is Friday, so that means loads of Sodium news and releases today. Getting set up for that this afternoon. We do about half of our weekly releases on Fridays, so lots to keep us busy.
Yep. Already doing my best to make sure everyone knows I will be unreachable all night tonight.
Have y'all considered going to just one release a week, such as every Friday night or Sunday night or so? Might be easier for bug tracking.
Bigger releases mean more breaking bugs all at once with less time to catch and address them. Mitigating bug issues is a key reason for more releases. That way bugs come out faster, get fixed faster and releases are way smaller. So we are troubleshooting tiny bits of code changes instead of big groups of changes, to find where bugs exist.
Think about it like a system that is broken. If you just patched one library, or just patched hundreds and the system and something breaks, it's really easy to find the problem when you only updated one thing. But if you updated your whole system and something breaks, the problem could be anywhere and you are far more likely to be trying to find multiple issues at once that might even interact with each other.
Beat you to it
I saw that
-
@quixoticjustin said in What Are You Doing Right Now:
@quixoticjeremy said in What Are You Doing Right Now:
@quixoticjustin said in What Are You Doing Right Now:
@nerdydad said in What Are You Doing Right Now:
@quixoticjeremy said in What Are You Doing Right Now:
@quixoticjustin said in What Are You Doing Right Now:
It is Friday, so that means loads of Sodium news and releases today. Getting set up for that this afternoon. We do about half of our weekly releases on Fridays, so lots to keep us busy.
Yep. Already doing my best to make sure everyone knows I will be unreachable all night tonight.
Have y'all considered going to just one release a week, such as every Friday night or Sunday night or so? Might be easier for bug tracking.
Bigger releases mean more breaking bugs all at once with less time to catch and address them. Mitigating bug issues is a key reason for more releases. That way bugs come out faster, get fixed faster and releases are way smaller. So we are troubleshooting tiny bits of code changes instead of big groups of changes, to find where bugs exist.
Think about it like a system that is broken. If you just patched one library, or just patched hundreds and the system and something breaks, it's really easy to find the problem when you only updated one thing. But if you updated your whole system and something breaks, the problem could be anywhere and you are far more likely to be trying to find multiple issues at once that might even interact with each other.
Beat you to it
I saw that
It's okay, your answer was more eloquent.
-
Wish I could have gone to GenCon this year. Maybe I'll be able to make the trip next year.
-
@coliver said in What Are You Doing Right Now:
Wish I could have gone to GenCon this year. Maybe I'll be able to make the trip next year.
Dragon con for next year.
-
I wish I could make it to Essen.
-
Lunch with @pchiodo
-
And @kkreutzer and @Dominica
-
I could go for a cold one right now.
-
@dashrender said in What Are You Doing Right Now:
@coliver said in What Are You Doing Right Now:
Wish I could have gone to GenCon this year. Maybe I'll be able to make the trip next year.
Dragon con for next year.
I plan on running some games at Adirondicon this coming October. We'll see how popular it is.
