ngc248

I transitioned into an ML Engineer.

There are different types of roles in an ML project.

1. Data scientists - These are the people who analyze the data and prepare the models. They basically deliver a jupyter notebook to us

2. ML Engineer - We take the notebooks from the Data scientists and productionize it.

3. MLOPs - These are people take care of the required infra, basically the equivalent of devops.

Personally, for me I worked as a hybrid of Data scientist/Ml enggr. I liked being an ML enggr better.

Product managers are no longer about the users. They just want to have some "impact" and then they move onto another product.

Mushishi is so atmospheric and just amazing

Also for some madcap anime FLCL ... that is quintessential anime for me.

hard work is a necessary but not sufficient factor to achieve success.

Yes, most nonfiction books should be pamphlets instead of books.

That is what it would devolve into.

Exactly, every company and org has a meta that you need to understand. If you understand the meta and you can/want to play the game, then play else start searching.

Do just enough day to day. Show heroic effort here and there. Don't get too attached to your project, service, code etc. Always understand the undercurrents so that you can keep abreast of things.

yep ... this is most likely the reason ... happened to me a lot of times

Politics happens whenever there are more than 2 people :). OP above must be really lucky to have not seen politics at all or one of those beneficiaries of politics who are like "Politics ... wut? nah"

If something has to happen, it will happen.

This is the situation at most big companies.

very clearly said, this is such a subjective process.

After The Pirate Bay and other famous public sites went down, there has been a proliferation of private trackers. These private trackers have high quality stuff. To get an invite, some of the trackers need references and also do personal interviews etc.

>>> Code is simply an unfortunate vehicle to do so.

This is akin to saying "Eating is simply an unfortunate vehicle to get energy"

>>>> feature factory, I think of an engineering team that has zero input into the product process and just builds whatever PMs or leadership says is important.

Yep, this was what I had heard referred to as a feature factory. No input of the engineering team, just take stories and churn out code.

Wish him a fruitful recovery. Man's a legend

UT 99 and Quake 3 Arena came out at the same time. But UT with its modes and different game types was just amazing.

There is a way to splitting data. The service which owns the data always does the writes and others who need reads on that data can store replicas. ofc the complication then will be in replicating data, but this will enable services to massively scale and eliminate SPOFs

If you join companies like HPE, Dell etc you can probably double your pay and still have good WLB. FAANG are outliers with regards to pay. There are other tech focused companies like the ones I mentioned above which still pay above average and have good WLB.

There is a wiki page too --> https://en.wikipedia.org/wiki/List_of_grenade_attacks_in_Swe...

Exactly, a monolith is suitable for small orgs or companies which deliver one thing. Microservices are not a fad and they solve a real world problem where you need to deliver for ex: something like a cloud platform. 10s of orgs cannot work on a monolith without stepping over each other, just the communicatin over. Also microservice enable you to scale (scale-out) the parts of the system that need scaling.

At scale microservices do help, but you get into unnecessary problems when you don't have scale and use microservices.

Its not just tech, there is a shortage in the trades and skilled labor

>>> They weren't going to design a perfect microchip. They were going to design the perfect microchip factory.

Its the "selling shovels vs digging gold" concept.

am in the same boat and the ppl responsible for the issues are always busy denying . Some of these ppl have also got into management, so they have got management cover. The only way things get solved is if some other team takes over the codebase maintained by them, but the actual culprits are failing upwards and moving into management.

NEET and hikkikomori are not the same. NEET are just unemployed. Hikkikomori are totally withdrawn from society and family.

Depends on at which level you need atomic updates. At the entire document level or at individual property level

I have implemented a Distributed lock using DynamooDB and the timeout for the lock release needs to be slightly greater than the time taken to process the thing under lock. Else things like what you mention will happen.

What I feel is there may be some princples of leadership which overlap, but Military and Civilian leadership is essentially different.

In the military the lower ranks are mostly trained with drills to follow orders unquestionningly. The creativity is mostly left to Specops/Intelligence.

In the civilian world, even the lower ranks get to at least debate.

At scale ... it is better to use CQRS ... sou you have a transaction model which is fully normalized and a read nly model which is wide, if you really want to use a RDBMS.