Programmers write code SLOWER under pressure!

preview_player
Показать описание
#shorts #programming #programmers #code #coding #softwareengineer #softwareengineering #softwaredeveloper #softwaredevelopment #programmer #scrum #scrummaster #agile #agilesoftwaredevelopment #agiledevelopment
Рекомендации по теме
Комментарии
Автор

Every PR be like: 9 woman can deliver babe in 1 month.

lukaogadze
Автор

Once you destroy morale, or create a culture of panic, or generalized anxiety, your team, your product, your company even, are done.

WarrenPostma
Автор

This is why, whenever I start a project, I remind the product owners and any managers that want to micromanage the project of the old axiom. "Good, fast, or cheap: choose two."

uyk
Автор

That is what some people with "assembly line" reasoning do not understand: Software development is not just about wielding the tools. It is about combining your mind with the tools to tackle unique problems - to innovate. It is not a process that is as predictable as acquiring the skill to use a machine more efficiently nor producting in a predictive manner when it comes to time.

And just to say so: Software development is about automating tasks so that people are able to do more of their time - and people to spend less time. We are freeing up resources. This is thanks to us programmers using our minds to try to understand the businesses (people) that are using our software. Software development is the backbone of our modern society. That is why they pay us as much as they do.

marna_li
Автор

I worked full-time on a project where I am the only full-time developer for over a year. I was also on-call for every day of that year. My manager still gave me negative reviews because I was stressed out and couldn't be as productive anymore after a year of abuse.

ironuckles
Автор

but as a manager, if you remove this pressure, then you would have to define the problem and the goal correctly and precisely for the team. This is a hard thing for many managers/product owners since it requires deep technical knowledge. Many of the situations where the team got stuck (and you think the are wasting time), is just because the problem or real goal is unclear.

mazdakhng
Автор

And scrum (and kanban, but those two are similar enough as to treat them as identical in this) is the latest software assembly line.
Daily progress meetings, biweekly deliverable deadlines, weekly planning meetings, etc. etc.
And of course giving management (whether the scrum master, product owner, project management, or whomever pulls the strings the tools and metrics to push harder and harder for more code, more deliveries, more of everything except the mental and physical long term (or even short term) health of their employees (and then just allows them to discard employees who end up burned out or otherwise "substandard" with the dirty water and replace them with "fresh blood".

jwenting
Автор

Try telling all this to my boss who doesn’t understand software development. He wants me to look into a crystal ball and tell him exactly how long it will take to code.

samb
Автор

You could turn your videos into management training videos. I suggest viewers turn each of these videos into at least 1 question to ask management in an interview.

queenstownswords
Автор

Thank you so much for this one.
I feel as if I'm not persuasive enough when I say the same very thing.
I'll use this video instead :)

kardahaspindal
Автор

Just did a technical interview for a simple task (simulate a spreadsheet with setCellValue and getCellValue methods/functions). The interviewer kept asking me questions if I stopped talking for more than a minute. And while I was working through an issue (off by one or some unusual Array method not working as expected), he'd keep commenting on every debug action I'd take. I did get it somewhat working by the end, but I did not do well. Doesn't matter because I don't want to work there now.

In contrast, when I was interviewing, we would send the canidate with a take home problem that closely mirrored what they would ACTUALLY BE DOING in the role. It's much less stressful for the canidate, much more informative for the interviewer.

Creating a spreadsheet in a timed high stress environment out of JS arrays is not the metric to measure real life design architecture and decision-making for a business.

AmatuerHourCoding
Автор

This is something that I got intuitively, but it didn't seem like my team did, so I let myself feel inadequate for a long time when I noticed that I wasn't necessarily a faster "widget builder". But I still get feedback from my manager that they appreciate how I dig into a problem to prevent us putting up just bandaids or letting code quality suffer.

vulpixelful
Автор

Even good junior devs believe it's their job to produce a final product, like a factory produces widgets, or a cow produces milk. It's a career changing event when it becomes clear software development is -- exactly as you said -- establishing a process.

timgerk
Автор

truth
any pressure makes me at least 20% more dumb

deepfuchsia
Автор

Way back in 1989 Space Quest 3 summed it up nicely with the scene at the final planet where programmers are being whipped while working at ScumSoft.

ArisAlamanos
Автор

This is So true. I’m refusing to work crunch for the rest of my PhD, outside of very specific circumstances. Over months, it makes me Substantially slower.

carrias
Автор

This is soo true I can write 100 line within minutes but if given time to think, we can make it in 20 or 30 lines. That's how fast efficient codes are written but we don't get enough time because even if we do come with 30 lines solution we need to take care of all edge cases where the program might fail to perform the task.

anuragtekam
Автор

When I ran a team, my main goal was to avoid the "herding cats" effect, in which people wander off. A short weekly meeting reminded everyone of the team goal, what each person was tasked with / how they were progressing and if trouble was on the horizon (and what we could do about it). Other than that, I wanted to keep hands-off and let people progress at their own rate. This was all systems design and writing pretty evil acceptance tests to go with the designs.

My boss tho was under terrible pressure and sometimes that got to much. Once he came down whilst I was at lunch and ripped into the team. I was so so angry and had to go beard him in his den. Those games though did not stop. Once he came out with "your team is the only one that makes any progress" and dumped another project onto me plus 20 more guys to manage. So, I starts going around these people talking to them trying to sketch were they could fit in. Yet, the whole thing was a fiction in that he'd made it up; he hadn't cleared the reorg with senior management or the guys team leaders... so this was all shocking news to them! BANG! My phone was ringing.

Can't make this stuff up.

xlerb_again_to_music
Автор

well said. In our company we work using scrum and we have a lot of distracting meetings. How am I supposed to create software when I am always distracted and stressed out?.

MilMike
Автор

We have 3 scrum meetings in a single day, every day.... Guess what would be our plight. Its an Indian Service mnc which mandates 70hrs/week.

saurabhpande