Not a rant, just my thoughts :)
At November and October of last year I was very frustrated with everything - everything was annoying me and I was bored even with coding. I needed a break and do something different - go somewhere.

So we decided with friends that we will go to Georgia to spent there New Year Eve. Right now I'm coming back from airport by bus to my city aftertrip but can't sleep because I'm energized as fuck! Whole week without internet (sometimes we got open wifi to check buses or maps), without local sim card, without roaming, just our group and good attitude. We visited almost whole north of Georgia riding in taxis, marshrutka, even autostop, and it was fucking awesome.

So, when you are exhausted, take a break and regenerate your baterries, work is not everything! Just wanted to share this with you :) Can't wait to go to work in monday to write some code :) Life is beautiful!

On photo - my friend takes photo of Kazbek Mountain :)

My exact plan for new year.
What's yours?

We are the 31, it is 00:54, I have a full specification to deliver on the 1rst at 00:00, and there is only half of it done.

Wish me luck for my doc New Year Eve

How many of devRanters were on their computer during New Year Eve ?

I was.

It's almost 2017 and the only thing Im doing is stay laid in bed reading rants it feels wired 😐 but its funny anyway 😝😀😀

Looking back on my Christmas holidays while waiting for my train to come.
I wrote my last exam on the 22, took the train home on 23, spent Christmas and the 25 with my family, searched for a new apartment for 3 days, had two days left to do an assignment due to the 30, was packing till 3 in the morning today and will have my first day of work tomorrow. (Yeah, I spend new year's Eve home alone and completely sober...)
I wonder when I will have an entire meltdown and become some Joker level psychopath... Also happy new year everybody 😁

On New Year's Eve a few years back I was around 21/22 and my friends were anywhere between 20/25.

My best friend has a big house so he offered to host it there (as every year pretty much), so we all agreed to do dinner and party after.

We decided to go with barbecue, and we all brought a few things.

Without my knowledge, they are all pretty much gamers and also decided to bring their laptops and even towers to play during the whole day and night.

The result was me "alone" cooking with the dad of a female friend (whose wife died a few years back and offered to help since he would be pretty much alone or with some other family members, not sure).

Once we finished cooking and went on to calling them, no one came to eat because "they were finishing just one more game", and eventually the dad yelled at them and left, I just went eating by myself, and they all showed up a few minutes later looking like 5 year olds when dads scream at them.

I can pretty much say that was the weirdest thing ever, but they did learn because never again they did the same!

They've been in a meeting with some clients the whole morning.
12PM, time for me to go. Say Happy New Year and am on my way home.
12:20 Got home, took shirt off, got something to eat from the fridge.
12:22 Bit the first slice of pizza. Phone rings.
- "Yo' we wanted to show them app 2 but I can't log in."
+ "I left the laptop (and the whole dev environment) there, and there's no PC on in my house (and no dev environment whatsoever)."
- "Well check with your phone. [SIC] Tell me when you fix it."
12:32 I had turned my personal computer on; checked the problem was what I imagined (unpkg lib with no version defined on the link had a new major/non-retrocompatible version); grabbed an online FTP tool; remembered IP, user & password; edited the single line that caused the problem; and checked it worked. Calling back.
+ "It's fixed."
- "Thanks!"
12:38 CEO sent me an image of the app not working, due to a known bug.
+ "That happens if you try to access app 1 having accessed app 2 and not logging off." (app 2 isn't being used / sold, as it's still in development) "Try logging off and logging in again from app 1."
- * radio silence *
+ * guess they could get in *

They had the whole freaking morning. 😠
I'm the hero CMMi's level one warns you about. But at what cost.
Happy early New Year's Eve everyone.

On the roof of my friends house. On new years eve.
The party was too noisy for me to hear the client over the phone, so I was milling around the appertment until I no longer heard the noise.

Sat down, took laptop from backpack, solved issue, wished client a Happy New Year.

Packed in laptop. Stood up, realised I had somehow wandered out of the appartment and up onto the roof.

Sat down again. Vertigo.

Opened the laptop again, sending the client the bill at 500% overtime rate.

At least the fireworks were pretty.

Every year, the worst dev experience comes right at the holidays, when website owners with big egos want to launch right on (U.S.) Thanksgiving Day, Christmas Eve, or New Year’s Eve/Day because they think they’re that popular and important. It never occurs to them that this is the WORST time because any third party support you need for hosting, APIs, plugins, etc. is either backlogged or out of office. And because NOBODY is eagerly awaiting the redesign of ANY website on those particular dates since they are stuffing their faces and getting s&&&faced at bars and parties. Nobody will even notice that your website has changed until January 15th at the earliest.

My New Years Resolution is 3840x2160!

Silver spooned europeans get to spend new year's eve partying and getting drunk not having to worry about a damn thing since their government has got them covered with the first of January being a public holiday.

No currency devaluation, no slave labour, no care in the world.

Happy new year motherfuckers

My previous employer was an e-commerce company. Most of our customers had use it or lose it funds that had to be spent by December 31 each year. So every year, the devs had to stay online until midnight on New Year’s Eve just in case there was a website issue. I didn’t witness any issue during my time there, or at least I was never contacted for support when I was on NYE duty.

They compensated by giving an extra PTO day for future use. Pre 2020, they’d allow us to leave work two hours early on NYE since the office was in NYC and getting home would be a nightmare. But you’d have to work from home to work the NYE support.

It was “optional”, but we know as a dev it’s not really optional unless you have a life and death reason not to. My first few weeks working there, my grandma had passed away. The funeral was NYE weekend so I was excused from doing the NYE support my first year because I was on bereavement leave.

The last two weeks of December were considered blackout dates for PTO, so everyone (including non devs) was not allowed to take any vacation time during those two weeks. Some people might have a problem with that if they’re into holiday celebrations and family and friend get togethers. They did observe Christmas, so that was the only day off most folks got during those two weeks. Though, the period from Thanksgiving through the end of December was stressful.

This is an actual transcript...
Since it's way too long for the normal 5000 characters, hence splitting it up...

Infra Guy: mr Dev, could you please give some rational for update of jjb?
Dev: sparse checkout support is missing
Infra Guy: is this support mandatory to achive whatever you trying to do?
Dev: yes
Infra Guy: u trying to get set of specific folder for set of specific components?
Dev: yes
Infra Guy: bash script with cp or mv will not work for you?
Dev: no
Infra Guy: ?
Dev: when you have already present functionality why reinvent the wheel
Dev: jenkins has support for it
Dev: the jjb is the bottle neck
Infra Guy: getting this functionality onto our infra would have some implications
Dev: why should I write bash script if jenkins allows me to do that
Dev: what implications ??
Infra Guy: will you commit to solve all the issues caused by new jjb?
Dev: you show me the implications first
Infra Guy: like a year ago i have tried to get new jjb <commit_url>
Infra Guy: no, the implications is a grey area
Infra Guy: i cant show all of them and they may hit like in week or eve month
Dev: then why was it not tackled
Dev: and why was it kept like that
Infra Guy: few jobs got broken on something
Dev: it will crop up some time later
Dev: if jobs get broken because of syntax
Dev: then jobs can be fixed
Dev: is it not ???
Infra Guy: ofc
Infra Guy: its just a question who will fix them
Dev: follow the syntax and follow the guidelines
Dev: put up a test server and try and lets see
Dev: you have a dev server
Dev: why not try on that one and see what all jobs fails
Dev: and why they fail
Dev: rather than saying it will fail and who will fix
Dev: let them fail and then lets find why
Dev: I manually define a job
Dev: I get it done
Infra Guy: i dont think we have test server which have the same workload and same attention as our prod
Dev: unless you test how would you know ??
Dev: and just saying that it broke one with a version hence I wont do it
Infra Guy: and im not sure if thats fair for us to deal with implication of upgrading of the major components just cause bash script is not good enough for u
Dev: its pretty bad
Infra Guy: i do agree
Infra TL Guy: Dev, what Infra Guy is saying is that its not possible to upgrade without downtime
Infra Guy: no
Dev: how long a downtime are we looking at ??
Infra Guy: im saying that after this upgrade we will have deal with consequences for long time
Infra Guy-2: No this is not testing the upgrade is the huge effort as we dont have dev resources to handle each job to run
Dev: if your jjb compiles all the yaml without error
Dev: I am not sure what consequences are we talking of
Infra Guy: so you think there will be no consequences, right?
Dev: unless you take the plunge will you know ??
Dev: you have a dev server running at port 9000
Infra Guy: this servers runs nothing
Dev: that is good
Dev: there you can take the risk
Infra Guy: and the fack we have managed to put something onto api doesnt mean it works
Dev: what API ?
Infra Guy: jenkins api
Infra Guy: hmmm
Dev: what have you put on Jenkins API ??
Infra Guy: (
Dev: jjb is a CLI
Infra Guy: ((
Dev: is what I understand
Dev: not a Jenkins API
Infra Guy: (((
Dev: (((((
Infra Guy: jjb build xmls and push them onto api
Infra Guy: and its doent matter
Dev: so you mean to say upgrading a CLI is goig to upgrade your core jenkisn API
Dev: give me a break
Infra Guy: the matter is that even if have managed to build something and put it onto api
Infra Guy: doesnt mean it will work
Dev: the API consumes the xml file and creates a job
Infra Guy: right
Dev: if it confirms to the options which it understands
Dev: then everything will work
Dev: I am actually not getting your point Infra Guy
Infra Guy: i do agree mr Dev
Dev: we are beating around the bush
Infra Guy: just want to be sure that if this upgrade will break something
Infra Guy: we will have a person who will fix it
Dev: that is what CICD is supposed to let me know with valid reasons
Dev: why can't that upgrade be done
Infra Guy: it can be done
Infra Guy: i even have commit in place

Finally moved to debian:budgieDE for new years eve, looking forward to a very stable year for development.

I am loving my first day here, bye ubuntu(mostly bye snaps)