ResearchCode

8 ms·

151.
by ResearchCode 3y ago
That has more to do with discrimination against the unemployed.
152.
by ResearchCode 3y ago
Stores existed before the MBA, but MBAs could be why food prices are up 30% since last year.
153.
by ResearchCode 3y ago
The person who does not do any deep work probably gets automated away first. Doing simpler office tasks with a lot of context switching sounds like something for an LLM.
154.
by ResearchCode 3y ago
Don't forget the 3 month - 2 year probation period. You're at-will for a large part of your average tenure for a quarter of the US pay. US might be more progressive than large part of Europe in some regards, like protection agains
155.
by ResearchCode 3y ago
They're the open office plan of project management. Tech workers have open offices, other professionals don't. I think we're just treated more poorly in some regards. Sprints tend to create lots of of tech debt and they'
156.
by ResearchCode 3y ago
Unnecessary overhead and micromanagement. You don't need "sprints" for any of that.
157.
by ResearchCode 3y ago
They do, and if you need to adjust a project you don't need 10 hours of weekly planning meetings (the Linux kernel developers don't need it, so your CRUD app developers don't either). The higher you go, the less agile it gets
158.
by ResearchCode 3y ago
That works great in FAANG companies, you might have 1-3 hours of meetings in total a week. That is how your typical PhD program works too, meet with your supervisor once a week. And low meeting culture seems to work just fine for the Linux
159.
by ResearchCode 3y ago
The good software companies do these projects in the 3-6 month length instead of 1-2 weeks.
160.
by ResearchCode 3y ago
Do Linux kernel developers do that?
161.
by ResearchCode 3y ago
I don't think that's the case for most of the substantial software projects. The plan for the Linux kernel doesn't change each week (do they have "PMs"?). 15% seems very excessive. Almost a whole day a week and two
162.
by ResearchCode 3y ago
It's busy work if you do it more than 1 hour any given week. If you do it full-time, you're something like a -10x engineer.
163.
by ResearchCode 3y ago
Generally the good jobs don't have "sprints".
164.
by ResearchCode 3y ago
That doesn't mean it's the best model. Successful in the sense of the career ladder, then maybe you're right. Successful as in productive or good for the organization or society, probably not. They are responsible for many of
165.
by ResearchCode 3y ago
Don't think there's any evidence for that.
166.
by ResearchCode 3y ago
It's not about low performers, but workers who complain about mistreatment. There is usually nothing preventing unionized companies for offering higher pay for high performers, but sometimes they use the union agreements (which ask for
167.
by ResearchCode 3y ago
Surprised any FAANG uses teams. I think the only headshot you might need is for your badge, can't imagine any serious company mandates LinkedIn (that would be your boss deciding that and not HR).
168.
by ResearchCode 3y ago
I thought it would be the opposite. People heavy on the soft skills and light on tech are more easily replaceable by a large language model. They seem the most promising for slide decks or fill in Excel sheets, or generate a meeting protoco
169.
by ResearchCode 3y ago
Yeah outside of the US they do constructive dismissal instead, and you'll be paid pennies even if you win the suit (and fail future "background checks").
170.
by ResearchCode 3y ago
Mostly agree but HR would have no clue about that.
171.
by ResearchCode 3y ago
Have to tune (hard-code) answers to some of those "gotchas" published on Twitter. Very core to give an impression of intelligence.
172.
by ResearchCode 3y ago
It's not less research mathematics than bathroom remodeling, that's for sure. I never tweaked any CSS, did you?
173.
by ResearchCode 3y ago
I think it's about balance, and a lot of software engineering projects would do better by steering more toward the academic research group model than the current fad of two week "sprint", plenty of non-technical pseudo-manage
174.
by ResearchCode 3y ago
In my experience just working by priority works better than endlessly estimating tiny chunks of a project, that doesn't actually give any real predictability. Workplaces that go heavy on estimation and "agile" methodology pro
175.
by ResearchCode 3y ago
If a computer scientist is doing completely routine tasks, they should be automating them, not estimating them every two weeks.
176.
by ResearchCode 3y ago
We're doing applied mathematics, not bathroom remodeling. Try telling a mathematician to "story point" the conjectures they're working on.
177.
by ResearchCode 3y ago
Because of non-technical micromanagers.
178.
by ResearchCode 3y ago
Probably similar to you but without "sprints" or "stand-ups" or reporting to "product owners", "agile coaches" or "business analysts". You would work on "epics", or projects as you
179.
by ResearchCode 3y ago
Those 10 minute meetings are 5 hours of lost time for deep work each week. Daily status reports are excessive. "Sprints" in general don't work in my experience, they are unnecessary overhead. You want to work in something mor
180.
by ResearchCode 3y ago
But the agile salesmen can't do code reviews.

More ›