Feel like we all bottom of the barrel engineer having to pass quiz and mind game to get hired for job. Begging to get hired by passing quiz lc sys design agent usage llm mastery
What point does company chase u? Wat kind of value do I need? Do you need to make global product? How successful? Or make open source tool that get adopted by one of big company?
39.99 vs 49.99?
Only other company I know that released a sequel cheaper was Grounded 2 which is in early access.
Is this game gonna be complete barebones at launch? Is it a EA release or full release?
Is team17 rushing this game out or something? How not a single picture for preorder skins? Are they still work on it
Is my GPU outdated already
Is there agent orange or is this game taking historical liberties?
Haven’t played in a while, looks like this is the new game.
It hurts quite bad right now and I’m also feeling quite sick, like chest congestion and stuff.
It was gone for a while but came back, I can’t even really sit at all cuz it hurts and it’s big and red and under the skin.
Idk if I should be going to a derm (do they do same day visits?) or should I just go to urgent care? Idk what they can even do
AI can 10x productivity, so why aren’t tech companies laying off 90% of their work force already, instead of these small amounts?
Then, they can hire back people at a fraction of the price to monitor the agents. Meta can easily be lean and operate under 10k employees. 10k employees * 10 agents = 100k employees.
Trying to figure out whether to take a rag/nlp class or a Etl class. This stuff is like random so idk, not the typical stuff I hear of
Yeah, some people throw in blockers here and there but it’s really just people talking about how productive they were the day before. Makes the standup so long, but the managers get googly eyes I guess because they think people are rockstars
Maybe this is the game you have to play though for promotions? Not sure
TBH stand ups should just be revised to “is there anything stopping you from during your work that the entire team needs to know”
What’s there difference between Comp Security 1 and 2? Seems like 1 averages a B, while 2 averages an A. Why is Comp Sec 1 harder?
Also, the in campus program seems like it has a lot more interesting classes than the online one. Will any of these ever get migrated to the online side
Idk I never had any of these symptoms on Lexapro
Zoloft seem like it’s activating my body more than relaxing it
as a software engineer the scary part is ai doesnt gotta be perfect. it just has to be good enough that companies go “why do we need this many ppl.” then teams shrink, hiring freezes happen, juniors get skipped, and seniors end up babysitting agents while everyone calls it productivity.
then the work itself gets automated. bug comes in, ai writes the ticket. logs break, ai investigates. agents code it, test it, fix ci, update docs, and deploy behind a flag. at that point it barely feels like an engineering team anymore, more like a machine with a few humans nearby.
and companies dont need to hate workers to do it. they just need to see payroll drop while output stays up. once one company proves it works, everyone else copies it. and its not just engineers, its pms, qa, support, analysts, writers, designers, managers, basically anyone whose job turns into tickets, specs, reports, tests, or approvals.
I see everyone complaining that reviewing AI Pr is too time consuming.
The answer is simple, just hit approve.
If some issue arises, you say it was missed in review. I mean reviews can’t catch everything, that’s why bugs exist
People keep creating extra work for themselves or others at my work. I speak up and say that it’s not needed, with why and what should be done instead. And I get ignored. And now, I don’t get invited to the meetings now.
Should I just let them do whatever at this point and try to avoid getting caught in the time wasting? It’s odd cause these people all complain that they have too much work and then do stuff like this
I’m working on a legacy app that being migrated to be modern.
One thing I notice is the team is making improvements all over the place for better practice, but at the same time, these improvements mean changes in the existing user workflow.
The user is accustomed to maybe 10+ years of the same workflow and I’m more adverse to changing how it works unless it’s necessary.
The way I think is more along the lines of migrate as is and improve where needed. Reduces risk, scope creep, less work and potential issues. Unless a change is needed, it should generally be avoided.
Others are thinking migrate and improve/change always. This means more user documentation and workflow changes, increased risk of something not working as expected due to the change, additional scope of let’s fit this improvement in and unexpected issues.
How do you know which philosophy is correct?
Maybe I’m in the wrong and we should shove improvements in while we have the chance, but at the same time, I’m adverse to blowback if things get muddied at the end because the amount of the change becomes confusing and things start breaking down. Which in my experience, always happens and requires a heroic effort to save the product
Is a month enough where I should be getting results?
Debating on whether I should increase or not
I could have sworn at one point, I had 6 active CBs. But now I only have 5 active cbs and my 6th is benched.
Is there a way to change this