Hate google chat.

Won't let me upload multiple files at the same time.

The Dev was asked an update on his sprint task.
What task? The Dev asked.

"You know changing our git branches from master to main" says the Scrum master.

What are your thoughts on jumping ships often to get higher salary?

I feel it doesn't make sense if you are really into learning. From what I've seen, when you become senior or have more responsibilities, the work that needs to be implemented takes more time. Because these responsibilities include aligning multiple teams in the company. Jumping ships won't let anyone experience the work.

I'm not against getting higher salary. But is jumping purely for that reason sustainable in the long run?

Guess the other 4?

Most of the product managers seem to explicitly mention user metrics with unique. Say # of unique users for the day, # of users ordered and so on. While being explicit is good, I'm wondering is there any metric that doesn't require unique counts?

Manager: Can we achieve X?
Dev: We can do with Y. But with the time that you are allocating it is difficult to complete Y.
Manager: Can we do a temporary fix?
Dev: Sure. We can do Z. But we need to prioritise Y in the next sprint else Z will cause issues in the long run.
Manager: Sure

After many next sprints,.......

Manager: Hey, Z is causing us issues regularly. Can we do something about it.
Dev: We still can do Y.
Manager: Come up with document on the implementation. We'll implement it.
Dev: Sure. Will do.

Dev: We have a data quality problem. Combined with data silos, we can't trust the numbers. We need to agree on metric definitions as a company.

CTO: (Points a PM)Help him on the metrics he has defined. We'll discard any other alternate definitions inside the company.

PM: You can start with these. (Throws a bunch of metrics without their definitions. Doesn't respond to questions regarding definitions.)

After a week of generating aggregates,

PM: The numbers seem wrong.

Fuck I know the numbers will be wrong. Because you didn't give me the definitions and I'll have to deduce them myself.

Seriously guys, how do you deal with PMs who don't cooperate in the requirement analysis?

A junior Dev was assigned a particular task where he is expected to come up with the command to run inside the system. He came up with the commands. I being a senior Dev and who has access to run the command on the pod did it after verifying it. I ran the command with screen sharing it to the junior Dev for him to learn. Now manager asked him to document the steps. I found that the doc contains screenshots from our call. My screens exactly.

Now my question is, I'm feeling that he should have asked or informed before taking a screenshot of my screen? Is this feeling normal?

Dev: The requirement is not clear. This seems to be a general usecase which you are thinking we might need but we won't actually need it.

Manager: You have to do it. This is the requirement. No other option. Don't ask any questions.

...... One week later....

Manager: Why is the team not open to me?

One of team member was showcasing their time series modelling in ML. ARIMA I guess. I remember him saying that the accuracy is 50%.
Isn't that same as a coin toss output? Wouldn't any baseline model require accuracy greater than 50%?

CTO: We'll use epochs for any time related fields in our services.

After service integration...

Dev from producer team: Hey the time field is showing up as 1970 and not null in your table. That seems to be a bug.

Me: Code looks fine. We are converting epochs to timestamps here. Null is taken care by the library function itself.

The same dev: Actually we are sending zero instead of null values in that time field. But we'd want the end table to treat that as null.

Me: Why can't you send null then?

The dev: Actually avro doesn't support nulls. Hence the zero.

Me: WTF??????

Manager to me: Actually you need to convert them as null. Anyways, this is not a blocker and we can live with it for now.

END OF RANT

Why can't they fucking send it as null? And when I asked about the details, that particular event type doesn't require that field. Still the manager insists on sending that field for it.

Fuck people who take design suggestions personally.
And that too in an architectural design review.

Ever wondered how Elon himself talked about not messing with AI in the past. I vaugely remember this was when there was a clash between Mark and Elon. And now Elon's companies OpenAI and Neuralink working on advanced tech. The same tech he told everyone to not mess with.

I haven't followed the trail of events clearly. But now this thought comes to my mind.

Anyone thinks the same? Or am I missing something?

Fucking lazy product managers....

Can't fucking care about renaming a word document....

The document says template you moron. You are supposed to duplicate it for your requirements. Not edit directly on the template.

And fuck whoever gave this moron edit access to a global template.

Fuck....

I hate people editing slack messages.

Here it goes...
1. I receive a slack message (notification sound while working)

After 5 mins of finishing my work...

2. I open slack to look at the message
3. The message says just a hyphen with an edited sign. Why tf you have to edit the message when you can delete it? Or better, don't send it in the first place.

Why people? Why?

All the microservices are planning to communicate via kafka. And they are planning to put a REST API between kafka and the service. So all services hit the REST API with the events and the REST API send events to kafka.

I don't see any benefit of having a REST API between the service and kafka. What are the opinions in the wild?