geekhack
geekhack Community => Off Topic => Topic started by: iLLucionist on Thu, 12 October 2017, 15:32:02
-
So I'm pushing code into production tomorrow.
I have a typical chicken-egg problem here:
A) drink, then release, or
B) release, then drink
WHAT IS THE BEST ORDER?
Dilemma A: it won't hurt as much when release partly fails or has regressions, but it will hurt extra hard the next day
Dilemma B: you will perhaps respond to support calls half drunk when, after the release and during drinking, it turns out there are still regressions, even though automated deployment and testings says it couldn't be.
-
Why not all three.
-
Why not all three.
Good point, haven't thought of that.
But how to respond to regressions and support when you are super drunk?
-
I think releases into production should best be done on Wednesdays, at noon.
That way, you will have everything fresh in mind when you release, and you will be available to fix any cock-ups that may be found directly after release.
People tend to be really slow in the head on Friday afternoons, or on Fridays in general, so really critical stuff shouldn't be done to the production environment on Fridays unless there is an emergency.
-
Why not all three.
Good point, haven't thought of that.
But how to respond to regressions and support when you are super drunk?
this is the true test of your abilities. if you can't do support while you're ****housed, you can't do support.
-
Option C is seek help for your alcoholism :))
-
I think releases into production should best be done on Wednesdays, at noon.
That way, you will have everything fresh in mind when you release, and you will be available to fix any cock-ups that may be found directly after release.
People tend to be really slow in the head on Friday afternoons, or on Fridays in general, so really critical stuff shouldn't be done to the production environment on Fridays unless there is an emergency.
I don't really think this is a serious question.
-
I think releases into production should best be done on Wednesdays, at noon.
That way, you will have everything fresh in mind when you release, and you will be available to fix any cock-ups that may be found directly after release.
People tend to be really slow in the head on Friday afternoons, or on Fridays in general, so really critical stuff shouldn't be done to the production environment on Fridays unless there is an emergency.
That's I good point, I should shift to Wednesdays. It's funny, coz around here people typically argue "yeah.. but those days we try to do actual work," like releases into production don't count as work.
-
Why not all three.
Good point, haven't thought of that.
But how to respond to regressions and support when you are super drunk?
this is the true test of your abilities. if you can't do support while you're ****housed, you can't do support.
Customer: "Yes, is this support? I CANNOT LOGIN"
Le me: never had login, is it any good?
Customer: "WHAT YA MEAN LOGIN ANY GOOD"
Le me: I mean, is it like a gin? Or more like a cocktail?
Customer: "What is wrong with you? I demand I speak to your supervisor immediately!"
Le me: Sorry, we cannot login at the moment, we are facing issues with a new version of the software.
Customer: "That is why I AM CALLING **breathing heavily**"".
Le me: "Sorry Mr. Calling, please hold on, let me see what I can do. **pukes in trashcan**".
-
Option C is seek help for your alcoholism :))
I don't have time for that, I don't know how to fit that into my drinking schedule :p
-
I don't always do releases, but when I do, it's Friday evening.
-
I don't always do releases, but when I do, it's Friday evening.
Not always a good idea.
We do releases when the client requests, however there's generally a fairly rigorous testing procedure in place before it reaches production.
-
I don't always do releases, but when I do, it's Friday evening.
Not always a good idea.
We do releases when the client requests, however there's generally a fairly rigorous testing procedure in place before it reaches production.
What about the standard operations policy where you only release after a minimum of 158 phone calls, 342 emails, and 1243 texts.
-
I don't always do releases, but when I do, it's Friday evening.
I KNOW RAIT. I should stop. Just stop. Well, when at illu's house it is everynight drinking night, it doesn't REALLY matter when I release now does it?
Release and realize are so similar..
-
I don't always do releases, but when I do, it's Friday evening.
Not always a good idea.
We do releases when the client requests, however there's generally a fairly rigorous testing procedure in place before it reaches production.
What about the standard operations policy where you only release after a minimum of 158 phone calls, 342 emails, and 1243 texts.
Turns out it upsets the customer. Can you imagine? Always complaining and mansplaining.
-
I don't always do releases, but when I do, it's Friday evening.
Not always a good idea.
We do releases when the client requests, however there's generally a fairly rigorous testing procedure in place before it reaches production.
What about the standard operations policy where you only release after a minimum of 158 phone calls, 342 emails, and 1243 texts.
Turns out it upsets the customer. Can you imagine? Always complaining and mansplaining.
I thought upsetting them was the key to imbue the developer with holy light upon actual release..
It's like scotty always telling the captain, it's impossible, while in reality, he's just being a lazy phatty..
-
What in god's name actual release are we talking here? xD
-
What in god's name actual release are we talking here? xD
pr0nhub premium dude ...
iLLucionist is gonna hook us all up
right iLLucionist ??
-
What in god's name actual release are we talking here? xD
pr0nhub premium dude ...
iLLucionist is gonna hook us all up
right iLLucionist ??
"netflix but for pr0n"
I call it: pornflixtube
-
A lot about the answer depends on what you're drinking... ;)
-
A lot about the answer depends on what you're drinking... ;)
cognac, dark rum, white wine, red wine, gin tonic, ginger beer cocktail (rum + gingerbeer + lime), mostly
-
A lot about the answer depends on what you're drinking... ;)
cognac, dark rum, white wine, red wine, gin tonic, ginger beer cocktail (rum + gingerbeer + lime), mostly
Cognac is great. Red wine is pretty good. Rest is pretty meh.
Beer and whisky is where it's at for me.
-
A lot about the answer depends on what you're drinking... ;)
cognac, dark rum, white wine, red wine, gin tonic, ginger beer cocktail (rum + gingerbeer + lime), mostly
Cognac is great. Red wine is pretty good. Rest is pretty meh.
Beer and whisky is where it's at for me.
Unfortunately, can't drink both coz of my gluten allergies. Whisky soo good. Beer icecold soo good. FML.
-
A lot about the answer depends on what you're drinking... ;)
cognac, dark rum, white wine, red wine, gin tonic, ginger beer cocktail (rum + gingerbeer + lime), mostly
Cognac is great. Red wine is pretty good. Rest is pretty meh.
Beer and whisky is where it's at for me.
Unfortunately, can't drink both coz of my gluten allergies. Whisky soo good. Beer icecold soo good. FML.
One of my colleagues is gluten intolerant, and she can drink whisky with no problems (no beer though).
-
A lot about the answer depends on what you're drinking... ;)
cognac, dark rum, white wine, red wine, gin tonic, ginger beer cocktail (rum + gingerbeer + lime), mostly
Cognac is great. Red wine is pretty good. Rest is pretty meh.
Beer and whisky is where it's at for me.
Unfortunately, can't drink both coz of my gluten allergies. Whisky soo good. Beer icecold soo good. FML.
One of my colleagues is gluten intolerant, and she can drink whisky with no problems (no beer though).
Stories on this differ, for what I've read. Some say it is filtrated, so no gluten. Some say filtration is sloppy, so gluten.
-
A lot about the answer depends on what you're drinking... ;)
cognac, dark rum, white wine, red wine, gin tonic, ginger beer cocktail (rum + gingerbeer + lime), mostly
Cognac is great. Red wine is pretty good. Rest is pretty meh.
Beer and whisky is where it's at for me.
Unfortunately, can't drink both coz of my gluten allergies. Whisky soo good. Beer icecold soo good. FML.
One of my colleagues is gluten intolerant, and she can drink whisky with no problems (no beer though).
Stories on this differ, for what I've read. Some say it is filtrated, so no gluten. Some say filtration is sloppy, so gluten.
It probably depends on what whisky you're having. You might be be suitable for an Islay.
-
Gluten free beer is a thing even in Britain!
-
Gluten free beer is a thing even in Britain!
Gotta try me one of those!
-
You never did tell us what you did :)
-
What in god's name actual release are we talking here? xD
pr0nhub premium dude ...
iLLucionist is gonna hook us all up
right iLLucionist ??
..... did someone say pron
-
Did a production release Friday, finished it late afternoon.
Went home.
-
You never did tell us what you did :)
I have my own company, I make (statistical) research software, mainly combination of python (django) and R.
I build full service end-to-end (from research idea to final report) research solutions, that basically automate the whole research cycle.
-
You never did tell us what you did :)
I have my own company, I make (statistical) research software, mainly combination of python (django) and R.
I build full service end-to-end (from research idea to final report) research solutions, that basically automate the whole research cycle.
I mean as far as the drinking. That's the only important thing.
-
You never did tell us what you did :)
I have my own company, I make (statistical) research software, mainly combination of python (django) and R.
I build full service end-to-end (from research idea to final report) research solutions, that basically automate the whole research cycle.
I mean as far as the drinking. That's the only important thing.
Ah right. Well, typically, releasing to production stresses me out. Even though I - as one should - automated the deployment pipeline and testing, you are never quite sure whether there will be regressions and - customers on the line.
So typically I like to do releases in the evening, when there is low traffic. So typically I first drink myself some fine white/red wine, gin tonics and/or cognac. And THEN to the release. Not when I am really drunk, but tipsy. So far it went good. But then you face the dilemma: if the release was successful .. celebrate by drinking more? Or just stahp?
*POURS ANOTHER GLASS*
-
I'm in the middle of another production release, except there are a bunch of hanging branches so this is going to take a long time.
-
I'm in the middle of another production release, except there are a bunch of hanging branches so this is going to take a long time.
Ouch... are you being a COWBOY OVER THERE? Manually doing the release?
-
I'm in the middle of another production release, except there are a bunch of hanging branches so this is going to take a long time.
Ouch... are you being a COWBOY OVER THERE? Manually doing the release?
Yeah - most of the tools are many years old and resist attempts to automate things.
Parts of it, using newer tools, have been mostly automated.
Plus there's lots of double-checking things, cross-referencing to the incident register and so on.
-
Dealing with release to production code right now (I've left the office over 4 hours ago.) Of course there are bugs the client didn't test until everything is already live.
So there is only one correct answer: Never stop drinking.
-
I'm in the middle of another production release, except there are a bunch of hanging branches so this is going to take a long time.
Ouch... are you being a COWBOY OVER THERE? Manually doing the release?
Yeah - most of the tools are many years old and resist attempts to automate things.
Parts of it, using newer tools, have been mostly automated.
Plus there's lots of double-checking things, cross-referencing to the incident register and so on.
Whoah... that is quite some every time! Luckily I have the luxury of setting up a deployment pipeline before the customer complains about shipping dates.
I hope the release went well!
-
Dealing with release to production code right now (I've left the office over 4 hours ago.) Of course there are bugs the client didn't test until everything is already live.
So there is only one correct answer: Never stop drinking.
Today I had a meeting with a potential customer over the specifics of an agreement. They literally did not grasp what the point is of "acceptance testing" (of course, assuming it is done right). They really thought that, magically, the functional requirements turn into working code that their customers can use. Like "make a management portal". Whooosh... https://theportal.com// Here ya go!
They literally asked me whether I just couldn't release the most code every day to production coz then "customers have the most quantity of features all the time, which is best for the customer". Imagine that.
I would have never dreamed that customers know so little about IT projects and software development, especially in this time of internet of things and software and apps for everything.
-
I'm in the middle of another production release, except there are a bunch of hanging branches so this is going to take a long time.
Ouch... are you being a COWBOY OVER THERE? Manually doing the release?
Yeah - most of the tools are many years old and resist attempts to automate things.
Parts of it, using newer tools, have been mostly automated.
Plus there's lots of double-checking things, cross-referencing to the incident register and so on.
Whoah... that is quite some every time! Luckily I have the luxury of setting up a deployment pipeline before the customer complains about shipping dates.
I hope the release went well!
No complaints so far.
And based on a couple of things that we changed, if they didn't work (untested, of course) I would have expected dozens of phone calls and incidents raised.
Now, onto the next urgent change for another customer, followed by another release. All I seem to be doing these days.
-
I like drinking but I HATE working the next day with a hangover. If I can't sleep in till 12 and doss about the rest of the day then I don't want to know. Of course this means I now drink a hell of a lot less frequently but I think I needed to cut back anyway.
-
I was going to say just send everything to the software vendor's support, but then I saw that you wrote the code.
I was in support at a software vendor for 5.5 years, and it always surprised me that a customer would spend 8 months to 1 year (sometimes longer) implementing and logging implementation emergencies that had to be fixed before going live, and then, on the first few days of being live, they would log production emergencies out the wazoo. DID YOU EVEN TEST THIS?! YOU HAD A YEAR! Of course, their support teams are basically just email servers (i.e. middle men) to us (if you log issues that just say "see attached" and attach an email from a user, why do you even have a job?). Luckily, I transferred to quality assurance a couple months ago, so it's less directly my problem now.
-
I was going to say just send everything to the software vendor's support, but then I saw that you wrote the code.
I was in support at a software vendor for 5.5 years, and it always surprised me that a customer would spend 8 months to 1 year (sometimes longer) implementing and logging implementation emergencies that had to be fixed before going live, and then, on the first few days of being live, they would log production emergencies out the wazoo. DID YOU EVEN TEST THIS?! YOU HAD A YEAR! Of course, their support teams are basically just email servers (i.e. middle men) to us (if you log issues that just say "see attached" and attach an email from a user, why do you even have a job?). Luckily, I transferred to quality assurance a couple months ago, so it's less directly my problem now.
What amazes me, is that in conversations with customers about features and support, I come to learn that the customer in their head made up all kinds of requirements, specs, functionality that has never been communicated that they thought were "completely logical" and that they stagger about "why doesn't it do this we want that". They don't realize this is additional hours that are going to be billed, they don't realize you literally make a technical and functional specification that they have to accord before you start development. Nowhere in the process do you discover all these additional requirements. When you release, all of a sudden you get this ****storm like "why doesn't it do X". WTF