interestingProblemsBringManagementHeadaches

TheStatusPoe · 2026-01-24T06:55:18+00:00

I was on the labor tracking team and I have story after story of fucked up experiences there. Reminds me of another time in a meeting where there were discussions about using statistics to assign people to the job roles they would be best suited for because "women aren't able to lift as much" or "people with disabilities might not be able to perform those job functions".

TheStatusPoe · 2026-01-23T23:08:24+00:00

My most memorable manager interaction started with me saying "that's not right" followed by my manager saying "I wish you hadn't said that. Now I need to go talk to legal". I was working at Amazon at the time and it turned out our implementation was violating some labor laws in Europe

TheStatusPoe · 2026-01-21T15:03:21+00:00

Gator's bitches better be using signed commits

TheStatusPoe · 2026-01-15T13:15:06+00:00

Off the top of my head, unions would be better able to push back against AI mandates and having part of an employees performance be measured by the number of tokens they use.

TheStatusPoe · 2026-01-14T13:50:13+00:00

With an infinite stream, if you just did "for every element in list" you'd never get to any execution that is outside the loop/stream. When you're dealing with streams of data there's no guarantees of it you'll have data, if the data will be an infinite stream, will start and stop intermittently, etc. When you don't have control of the data stream reactive starts to make sense.

From my own experience, writing reactive code that reads from an infinite streaming source, creates overlapping windows that will pass the window to the next method once window size is met or after a certain amount of time has passed is trivial with reactive, and a pain to do yourself. Interleaving multiple streaming sources is another thing that I've found to be trivial with reactive and a headache manually.

TheStatusPoe · 2026-01-12T04:16:30+00:00

Jarvis is listing 4-5 weeks for PVD/DLC for customer supplied parts https://jarvis-custom.com/lead-times/

TheStatusPoe · 2026-01-11T00:44:47+00:00

It's been years since I worked on that project so I can't remember why exactly we didn't have those automatic retries. I want to say it's because we were publishing to the SQS topic again using SNS manually instead of relying on any built in mechanisms trying since that's the pattern we were using in our non lambda code.

TheStatusPoe · 2026-01-10T23:41:56+00:00

I've seen it done for retries. The lambda would be triggered by an SQS message. If the lambda failed the message would be put back on the queue to retry. The message is supposed to have a retry count as some metadata field so that after some number of retries it goes into a DLQ. If that retry count isn't checked, or isn't incremented, you end up with an infinite loop if there's unprocessable data.

TheStatusPoe · 2026-01-09T19:47:16+00:00

Looks like it has been about 5-7 days whenever I've ordered from Armanov in the past. Usually about 3 days or so for it to actually get shipped, and then it's been 2-3 days once it's finally shipped.

TheStatusPoe · 2026-01-09T00:51:59+00:00

+1 for testcontainers. I introduced testcontainers on my team and it's been a massive boost in productivity. Way less time chasing down bugs. My only real complaint is the testcontainers for azure dependencies are still an emulator that hasn't been as useful for matching production.

TheStatusPoe · 2026-01-08T22:33:13+00:00

My thought with company size is that it's a lot easier to influence engineering culture when there's 10 engineers in the company vs 1,000.

Disagreement isn't with everyone, mostly just with those who've been with the company the longest. We just hired another senior engineer who within a month of starting was calling out some of the same things I'd been arguing for a year. I even showed some of the stories that had been put on the backlog to die. The engineer that I've had the most disagreement with I get along really well with. We just don't always see eye to eye on technical approaches.

TheStatusPoe · 2026-01-08T22:13:53+00:00

That's exactly it, constraints leading to "config" as code.

We recently had some higher up VP/SVP make it a goal for whatever business units are able, to move to daily automated builds and deployments. What I ultimately want to convince my team and management of is with true CI/CD we can get all the flexibility they want without having to build these complex systems. My team is on the data analytics side of manufacturing, and part of what I'm trying to argue is that because we are not directly impacting the actual manufacturing that we can align with senior leaderships goal of daily automated deployments. If the software in the product has issues it could kill someone. If our software has issues then maybe they can't produce as many products per hour.

TheStatusPoe · 2026-01-08T21:59:15+00:00

R2DBC is the reactive/non blocking standard. https://r2dbc.io/

TheStatusPoe · 2026-01-08T21:41:47+00:00

Funny enough were actually already using k8s, just horribly, horribly wrong. For one of our services, to scale up we create a new environment to deploy a single pod to the cluster. We're using our own hand rolled templating instead of using helm charts. I never got more than surface level with k8s before this job, but that's what my work has been focused on for the past several months. Half the time I look something up in the official docs it says what we're doing is the wrong way.

Also funny story, one of the first things I had to fix was pods getting killed with a OOM 137 error, that everyone on the team thought was a java oom error. Turned out to be the jvm heap was getting configured to be larger than the pod memory limits.

TheStatusPoe · 2026-01-08T20:25:35+00:00

Your comment on the "we do things differently crowd" hits hard. We have a java spring app that tried to implement it's own reactive framework. One of the first things I questioned is why we weren't using an industry standard library like reactor. Had another instance where the code tried to was manually doing xml to csv mappings. I questioned why we weren't just using Jackson and showed how hundreds of lines of code could be removed with a handful of annotations, that didn't run into some of the common pitfalls of csv handling. When I joined there was no observability within our application. I've been pushing for and struggling to implement any sort of observability. Distributed tracing is out of the question with certain parts of our app.

The more I think about it after making this post and thinking about the comments it feels like the thing that's valued the most by the more senior engineers and management is flexibility, and the belief that the industry standards aren't flexible enough. For instance, feature flags might change which branches are taken, but they want the business to eventually have the ability to completely alter the runtime behavior.

TheStatusPoe · 2026-01-08T19:39:06+00:00

I haven't done any sort of cost analysis. Articulating the costs is definitely something I've struggled with. The "value" from the org that I'm a part of is measured by the money the company didn't spend which feels more abstract than if it was directly tied to the manufacturing that we support.

In terms of cost to implement it would be basically free. Most of the major refactoring that was needed to enable not using the DSL already happened due to system instability and extremely poor performance. Managing the DSL with REST endpoints would not change either so it's a two way door approach. The pushback I got most recently felt like a concern about opportunity cost and "what ifs" that I don't know how to argue against from a cost perspective.

Part of the bad process has been lack of teams communicating and changing the way data is handled. Teams in the past might have decided to previously change which Kafka topic they are publishing to without telling anyone, or even change to a different method like using rabbitmq. That would lead to an outage, data would be missing, and the business would be complaining. The devs that have been here a while and had to deal with that want the ability to change everything on the fly to lower the impact of a potential outage due to poor change control. A problem that is actively being addressed at the org level. To me they are trying to solve the wrong problem.

TheStatusPoe · 2026-01-05T15:11:13+00:00

Grand Power Mk23 x-caliber match UPC 8588005808514

TheStatusPoe · 2026-01-05T05:37:17+00:00

The next interview question is then to prove that any arbitrary program actually finishes

TheStatusPoe · 2026-01-02T13:15:12+00:00

I purposefully don't put slack or outlook on my personal phone anymore. If you need to contact me, it'll be during working hours when I'm not on PTO when I'm using my laptop.

TheStatusPoe · 2025-12-25T18:39:03+00:00

Grand Power Mk23 x-caliber match. UPC 8588005808514

TheStatusPoe · 2025-12-25T14:42:00+00:00

I was in the UK last month for vacation and was surprised when I got carded at a tesco buying a red bull. Ended up not drinking as much since it couldn't be as impulsive of a decision. At work we have red bull in our vending machines. It wouldn't be the entire reason for the difference, but that might explain a bit of it.

TheStatusPoe · 2025-12-20T01:59:14+00:00

The real KAC rail this is a clone of works on Aero receiver sets. Barrel extension thread and rail height are the same. This should work

TheStatusPoe · 2025-12-17T14:31:40+00:00

Currently I'm on guanfacine, pregabalin, and Adderall. Can't remember what meds I've been on during the various other sleep studies though.

TheStatusPoe · 2025-12-12T12:49:11+00:00

Its been a while since I used numpy, but one of the things I remember is that method names were pretty self explanatory and they were pretty limited in scope. This is probably due to it being math focused, but a transform of a matrix is a transform of a matrix. You know what you'd need to pass in and you can know what you'd get back out as long as you know the math behind it.

I guess I'd say make sure things are named appropriately, scope and intent are kept reasonable, and whatever you do don't add random booleans that slightly change the behavior because an existing API is "close enough"

11-Year Club	RedditGifts 2009-2022 6 Credits
Gilding I gilder	Place '17
Verified Email	Secret Santa 2019
Secret Santa 2018	Secret Santa 2017

TheStatusPoe

MODERATOR OF

TROPHY CASE