![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Ok, it would have been fine, just sitting in a train, working.
Except that, fuck.
First, I'm on pager duty. And there was an even, at about 3am EST, and I tried to investigate, because, well, I was on a French train, and the internet was disconnecting once every 5-10 minutes, and I need go get a confirmation from my phone, which wants to recognize my face - after about 36 hours of casual travel.
Also, today is the last day of a "sprint", and it ends at 4pm eastern, which is 19:00 French time (today).
And there were meetings.
But the fun part was that I did try what I deployed on staging, and found that the code was getting an old config, and wtf? I posted a question on slack, but well, everybody's asleep. So there.
The good side was that when I took a bus from Agen, I was just looking into the window, seeing all those green field, not parched by the sun (yet).
When I got the opportunity to get back to the internets (meaning, my computers are ok, but my phone was discharged, and was unable to see my face (and report that me is me), so I had to go to a gifi store or something, and wait in line, while one madame bought a flower pot without a bar code, and the next monsieur bought a frying pan, but he did not have the store card, so he could not get the discount... and it was 12 minutes before the "standup" meeting. So I ran back.
Ok, ok. Then it turned out that while I was implementing, nobody on the other side figured that, well, to get a key from my server one needs a key id... ok, at least the provider id, can do - but they just introuced a flag: "need a token". As if my code is a GPT and could make any wild guess regarding what t.f. that token is, and who they are, those clients.
Ok, ok. At least Davis and Karen told me why my config is not available in my code (although they are in the same repo).
Configs are tricky in this application, they are posted to a config server... In short, it's all smart, and correct, and undocumented. I had sworn to document everything I see. The 1:1 map of China.
In any case, the deadline for the "sprint" is 4pm eastern, which is 21:00 french time, but I managed to deploy it to prod and test it before 16:00 french time. So, I'm good.
Did I tell you I'm on pager duty? The good part is, the application was written by geniuses (genii?) and only cracks (not crashes) Monday morning, not even every morning, and the failure is pathetic, and one can just manually restart that service (this generation is not familiar with scripting).
Ok, anyway, and we are all good people now. Just too many meetings.
At 1pm we had a post-mortem meeting. Although nobody died. And Jorge wrote that we should immediately adapt the newest version of ZIO. There was silence, but I started giving my comments, how important it is to use the latest version of ZIO, with Layers, and how this framework is totally superior to any other stuff/shit (like Cats) - yes, it is. In short, Jorge (btw, a contractor) got his idea pushed.
I also have an idea - my server does not check the encryption, the usability of the signing keys, the non-emptiness of the keys of the signing keys. But I'll do it anyway, big deal. We are on the right path.
At 2pm eastern we had another meeting, planning.
So, by the time I deployed to prod, I a) was totally exhausted, b) could not find how t.f. I can get errors in the logs from Kibana (I just forgot how to use kibana... I really forget too much, this morning, on the bus, I forgot both Dunning and Krueger's names, wtf, right? How long do I have before Alzheimer hits? Fight! Struggle! Never surrender!
But it's 20:37 now, and I'm totally ok, everything's fine, and tomorrow will be a great day (I'll need to implement the token generation based on keys in db, cached).
Except that, fuck.
First, I'm on pager duty. And there was an even, at about 3am EST, and I tried to investigate, because, well, I was on a French train, and the internet was disconnecting once every 5-10 minutes, and I need go get a confirmation from my phone, which wants to recognize my face - after about 36 hours of casual travel.
Also, today is the last day of a "sprint", and it ends at 4pm eastern, which is 19:00 French time (today).
And there were meetings.
But the fun part was that I did try what I deployed on staging, and found that the code was getting an old config, and wtf? I posted a question on slack, but well, everybody's asleep. So there.
The good side was that when I took a bus from Agen, I was just looking into the window, seeing all those green field, not parched by the sun (yet).
When I got the opportunity to get back to the internets (meaning, my computers are ok, but my phone was discharged, and was unable to see my face (and report that me is me), so I had to go to a gifi store or something, and wait in line, while one madame bought a flower pot without a bar code, and the next monsieur bought a frying pan, but he did not have the store card, so he could not get the discount... and it was 12 minutes before the "standup" meeting. So I ran back.
Ok, ok. Then it turned out that while I was implementing, nobody on the other side figured that, well, to get a key from my server one needs a key id... ok, at least the provider id, can do - but they just introuced a flag: "need a token". As if my code is a GPT and could make any wild guess regarding what t.f. that token is, and who they are, those clients.
Ok, ok. At least Davis and Karen told me why my config is not available in my code (although they are in the same repo).
Configs are tricky in this application, they are posted to a config server... In short, it's all smart, and correct, and undocumented. I had sworn to document everything I see. The 1:1 map of China.
In any case, the deadline for the "sprint" is 4pm eastern, which is 21:00 french time, but I managed to deploy it to prod and test it before 16:00 french time. So, I'm good.
Did I tell you I'm on pager duty? The good part is, the application was written by geniuses (genii?) and only cracks (not crashes) Monday morning, not even every morning, and the failure is pathetic, and one can just manually restart that service (this generation is not familiar with scripting).
Ok, anyway, and we are all good people now. Just too many meetings.
At 1pm we had a post-mortem meeting. Although nobody died. And Jorge wrote that we should immediately adapt the newest version of ZIO. There was silence, but I started giving my comments, how important it is to use the latest version of ZIO, with Layers, and how this framework is totally superior to any other stuff/shit (like Cats) - yes, it is. In short, Jorge (btw, a contractor) got his idea pushed.
I also have an idea - my server does not check the encryption, the usability of the signing keys, the non-emptiness of the keys of the signing keys. But I'll do it anyway, big deal. We are on the right path.
At 2pm eastern we had another meeting, planning.
So, by the time I deployed to prod, I a) was totally exhausted, b) could not find how t.f. I can get errors in the logs from Kibana (I just forgot how to use kibana... I really forget too much, this morning, on the bus, I forgot both Dunning and Krueger's names, wtf, right? How long do I have before Alzheimer hits? Fight! Struggle! Never surrender!
But it's 20:37 now, and I'm totally ok, everything's fine, and tomorrow will be a great day (I'll need to implement the token generation based on keys in db, cached).
