Well I’ll be damned.
Text for my screen reader using friends.
Me: What is the I in LLM stands for?
Gemini: The “I” in LLM doesn’t stand for anything. LLM stands for Large Language Model.
Well I’ll be damned.
Text for my screen reader using friends.
Me: What is the I in LLM stands for?
Gemini: The “I” in LLM doesn’t stand for anything. LLM stands for Large Language Model.
At what cost, though? I thought the generations after the millennials would be more tech-literate. But after seeing Gen Zs around me at home and at work, things are just regressing.
I hate how true this is. Not even 2 years later for my case.
All the projects that have shittier outcomes in my experience is always waterfall. This is mainly because the stakeholders usually have this bright idea to be added in the middle of development that’s really need to be added at all costs and then got angry when the timeline got pushed because of their fucking request breaking a lot of shit.
At least scrum has a lead time of around 2 weeks so that when someone has a idea we can tell them we’ll add it to the backlog and hope they forgot about it during the next sprint planning.
If your work is bleeding edge enough, even ChatGPT won’t be of help since it’s not in their training dataset.
Ohh I had a similar experience with a quite big open source project (~10k stars on GitHub). Posted an issue, it’s obscure enough even the lead maintainer comes in to help and still got stuck unable to fix the issue.
If you’re competent, a SM is invaluable, however it’s one of the easiest to replace role. As an example, almost all of the engineers in my division has a PSM I certification. So all the SM do is just facilitate meetings. When we started we have around 5 SMs but currently only have 1 because all of the SMs are redundant since the team already know how scrum works.
Ohhh that’s me right now. I work in a consultancy and I only got assigned to projects that are on fire. It’s almost 24 months without a gap between projects. Help me ಥ_ಥ
A good PM is rare because as soon as you get one, they’ll get poached within a few months.
It’s only scary if you’re incompetent.
My company started with full stack devs only and we’ve transitioned to specialized back end and front end since we realized that 1 specialized BE Engineer and 1 specialized FE Engineer can work faster with better quality than having 2 Full Stack Engineers.
I usually just do what they requested and when they come to complain I just tell them “well, you’re the one who requested this” and pull up receipts. My DM to myself on Slack is filled with screenshots and links to confirmations for bullshit requests that the product team made.
It’s just telling the computer in a very detailed way. Are you monolingual? I think the concept of learning how to code is easier if you speak more than one language.
Teams are just shit like that. Although my company has migrated to 365 for our work apps, the team’s main communication is still Slack. With Slack I’m still able to find old messages easily and be able to link it in relevant context.
One thing I learned about Lemmy is their users are much more serious. There’s a lot of obviously sarcastic comments getting replies treating it as a serious comment here.
After the report that codes made by the assistance of copilot are actually shittier than code written manually I’m feeling safe until the next breakthrough in AI development. Meanwhile I’m saving up gold for the eventuality.
If we’re really living in a simulation my dude is really asking for reality bending powers.
It’s bad if you don’t have a design system. If you have a design system it’s :chef’s kiss:
TBH compared to the old versioning system people used to use like SVN and Mercurial. Git is a godsend. Just taking your time in learning and not using a GUI client works wonders in learning how it works. Especially when all the GUI clients are basically a collection of commands being executed so if you fuck things up on CLI you know what happened vs using GUI.
In software development it’s usually used to describe the situation after an incident was resolved. The team that’s responsible for the feature usually performs a postmortem to find out the root cause and find out what they can do to avoid another incident.