5 ms·
What's wrong with how we train, hire, and motivate programmers [video]
- thorw73m 4y agonothing beats pay. Pay 20% more than your competitor.
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- ethanwillis 4y agoSomething that's much more worthy of your time and consideration instead of this video is to read up on the history and goals of A. P. Ershov: https://scholar.harvard.edu/files/gafinogenov/files/04_14-3afinogenov.pdf https://scholar.harvard.edu/files/gafinogenov/files/04_14-3a... Even more seriously for Ershov’s vision, the Ministry of Education and the commission charged with implementing the informatics course took aim directly at the cornerstone of the whole concept. In contrast, the commission proposed that the course focus on skills that would be directly useful to students in a practical context, and specifically not train them to be programmers.
- solardev 4y agoThis is a really long article written in difficult language. Can anyone summarize?
- newjersey 4y ago> how many [...] are actually solving problems [...] not a lot How is this specific to programming? Surely there are more pressing matters if we are looking for BS jobs that don't solve problems. > U.S. health care spending grew 9.7 percent in 2020, reaching $4.1 trillion or $12,530 per person. As a share of the nation's Gross Domestic Product, health spending accounted for 19.7 percent. https://www.cms.gov/Research-Statistics-Data-and-Systems/Statistics-Trends-and-Reports/NationalHealthExpendData/NationalHealthAccountsHistorical https://www.cms.gov/Research-Statistics-Data-and-Systems/Sta... This is almost one out of every five dollars in this country. Now that is something actually worth talking about.
- RhodesianHunter 4y agoParticularly when you consider how poor our outcomes are relative to our spending.
- drjasonharrison 4y agoIt's expensive to get good outcomes when you provide health care for a population with many older obese, inactive, and smoking members.
- XorNot 4y agoThe entire western world population is both aging and fattening, but the US has consistently had poor outcomes relative to spending. This explanation doesn't cut it: per-capita the US spends the most but it's demographic trends are not unique.
- Retric 4y agoThe US is unusually obese. https://en.wikipedia.org/wiki/Epidemiology_of_obesity#/media/File:Obesity_country_comparison_-_path.svg https://en.wikipedia.org/wiki/Epidemiology_of_obesity#/media... But US healthcare is also horrifically inefficient largely due to a combination of a private insurance system, poor management, and massive government subsidies. Unfortunately any effort to improve efficiency would lower profits or cost jobs.
- Retric 4y agoNot to detract from the overall point, but increased healthcare spending during a pandemic seems completely reasonable. I would also expect military spending to increase during a war. What the US wastes so much money on isn’t really healthcare it’s healthcare adjacent tasks like medical billing, insurance, advertising, etc.
- astrange 4y ago> Not to detract from the overall point, but increased healthcare spending during a pandemic seems completely reasonable Public health spending yes, healthcare spending maybe not. (For instance, if everyone's staying home they can't get injured in workplace or car accidents.) I've seen this argument used for universal healthcare in the US too, but it doesn't really make sense. Formal healthcare couldn't do much for you if you got covid since there weren't treatments for it, and now there is an antiviral and vaccine you don't need to go visit a doctor to get them.
- yellow_lead 4y agoIt's hard to focus on this video when you're staring at a Firefox start screen, the audio isn't very good, and it's out of sync with the video
- mihaigalos 4y agoConcerning the "Certified extra scrum master" quote from the video, I really like [1]: > [..] if your organization is struggling with an Agile transformation, drowning in chaos, you’re going to leap when someone offers you a lifeboat in the form of certifications and processes and tools. Executives understand processes and tools much more than they grok self-organizing teams. [1] https://www.simplethread.com/agile-at-20-the-failed-rebellion/ https://www.simplethread.com/agile-at-20-the-failed-rebellio...
- jillesvangurp 4y agoThere's a reason startups run circles around not-so-agile but yet self-styled agile corporate teams: mental agility. Mental agility is mostly found in young people and sometimes in older people that choose to stay humble and keep an open mind about their own abilities and skills. I like to think about myself as such; though if I'm honest, I'm more conservative than I used to be. It's disgusting how much value I get out of young people on my team willing to learn whatever and unburdened by experience vs. grizzled veterans with a lot of certificates and a rigid/dogmatic mindset that regard anything new as a threat rather than an opportunity to learn. I find it very energizing to be around such people. I've worked with veteran teams as well (like more than half > 40) and there were some spectacularly cynical types on those teams sucking all energy out of any room they entered. Given the demographics of developers (doubling numbers of programmers every five years), finding yourself on such teams is relatively rare. I've worked with numerous people that had certificates for this and that and rarely came away impressed by their skill sets. Also, I shook Ken Schwaber's hand (one of the people behind Scrum) at the end of a 2 day workshop many years ago that made me a "certified scrum master" and him probably a little bit wealthier. So, I know how hollow that phrase is. Licensed to wield multi colored post-its and sharpies, basically. That was one of the least agile companies I've worked with trying to be agile. No mental agility whatsoever at the senior level. But they compensated by sending all their senior engineers to trainings like this so they could virtue signal their supposed agility. These days, I keep my teams agile mainly by keeping them small. Small, remote teams don't need a lot of process and can resolve issues by simply communicating with each other. Partitioning teams and keeping the team boundaries informal removes a lot of need for process. In person meetings are rare with remote teams anyway. So post-its and sharpy wielding scrum masters have no place in such teams. We do have online meetings but I limit them to once a week for engineers and keep them informal: I want people to talk, ask questions, debate, and bond in the rare meetings we do have. Standups in front of a web cam are even more pointless than the zoned out de-caffienated cluster of extremely bored engineers droning on about what they did or did not do yesterday. So, not a thing that I do. I've always hated those type of standups and lots of developers I respect a lot seem to feel the same. I never got much value out of those. People waiting for such meetings to raise important issues are actually wasting time instead of being agile. Reach out asynchronously as early as convenient. Lots of issue resolution and problem solving does not require having any meetings whatsoever. And when there is a conflict that requires a meeting, have it 1 on 1 as early as convenient and don't burden the rest of the team with unresolved conflict. The best resolution is often just asking "do you have time for a quick call about this?". Waiting for some arbitrary meeting to happen turns those meetings into synchronization bottlenecks. The longer they are or the more you have of those, the worse the problem is. You solve synchronization bottlenecks with asynchronous processes and not with a "stop the world" point in time where people "meet" and are collectively not productive. Some OSS projects function entirely without meetings or meet very rarely. And some of those projects have orders of magnitudes more commits, developers, and change happening than most corporate "agile" projects. So, it can be done and IMHO is actually optimal and more agile.
- moonchrome 4y agoI'm 10 mins into this video and it's unbearable. Old farts (more about the attitude than the age, I'm not that young either) talking about architecture/organization layers that make things pointlessly complicated in the real world, cannot grasp stuff like the split between frontend/backend because likely haven't done nontrivial code on both for the last 10-15 years. Probably consult on "architecture and process" and the closest thing they get to writing code is write examples for books/talks. Guys like these are a big part of the reason we are an industry of building complex messes.