llamajams

I belive you are describing the the article quite aptly.

Well; Feature X is about to be released and the industry just invented feature Y and its all the rage and if its not in the pipeline the shareholders and the critiques get mad. So, The boffins decide that the company needs to get on it ASAP and cannibalize feature X team to make feature Y team and the "best" need to get on that team otherwise their career suffers. So the unwilling/incapable are left to sort out the kinks. They are divided into two camps which play a 0 sum game to get feature X released. Losing is bad for the losers, so you either resign t being an asshole for the benefit of the product or you try to not get your teammates fired at the detriment of the product. Maybe you try both and see. Either way youre resource starved and dammned either way. Maybe noone cares if you caught a bug before release. Maybe the guys that catch the bugs at the end of the line get praise and attention. Maybe everyone just gets mad that youre holding up the release, cuz the boffins wanted it done yesterday. After a while youre in a meeting debating whether an issue is not an issue and after an hour everyone has somewhere to be and one camp insists that if you hold it just so its not really an issue, and some think that this is a very rare edge case and would never happen IRL. one guy thinks this isnt a bug at all the user just has bad expectations. Others are tired of having to speak up and just wanna get on with their day because there might be a feature Z team and even though you got passed up for Y , youre actually a really god fit for Z s you better shut up if you wanna leave this mess. The guy who would have stopped this train rage quit 6 months ago. Finally everyone just calls it a non-issue and full send. Six months after the release there is an issue and now the regulators are coming, and you feel very vindicated that this was an issue but you didnt speak up , but secretly told Gary at lunch that this is gonna come back. Gary was in the meeting with the VP and the regulator ad made an off hand comment to the VP that you actually spotted this way back. And now the VP is mad that this issue could have been stopped, and now they think youre a pansy for staying mum , in fact this is unethical behavior and so youre off Z team and back to X. So you figure you never wanna be in this mess gain and switch to a diff org/company/ rage quit.

Rinse. Repeat.

Aren't haplotype groups essentially "race"? Certainly there is not white/black race, but a southern costal Indian would self differentiate from a central one, you can spot the difference visually,culturally and lingustcally and there is also well understood predispositions of different groups to specific ailments (see diabetes). Not my area of expertise so might be way off

Thanks for writing this. Had similar thoughts when I was reading the refwrenced article. What happens when "the next generation" actively resist education, convention , disregards the value of Canon, and the overhang is 1000ft over their heads? Just last week I gave up on the next generation dug a moat around my core libs and resigned myself to watching the slop tidalwave from my little island /sigh.

Same. I stopped reading after that. I get the sense that most of these people thing all code is web or mobile or something non critical. Granted im not a web or mobile guy so I cant presume the complexity, risk, cost of such things. But I assume its in a different category than safety/mission critical things. I do dev tools for ASIL-B systems devs now and even then I cant say im comfortable not reading the generated code. Some of my junior peers are though, and im very frustrated that I feel like I keep having to play AI janitor, dont think the bosses care.

These all seem to be gross simplifications that dont really help the argument. While we could certainly make a case that no value is generated in trading certain derivatives,commodity futures and options are very imporant in regulating price/ supply supply shocks in the global market.

Im always frustrated by such journalism; "why won't they do something!?" . What is there to do besides, face id , chat controlor, heavy moderation, and if it were done, a whole other crowd wpuld have their pitchforks ready to go.

Somewhat out of my league in this thread but,I think I am.one of these people. I do remember a time before I had an internal monologue , in fact I remember the day in elementary school when I learned, after having been explained to me by my teacher, that everyone else was "talking to themselves in their head". I think I spent the next month or so obsessing over this new found ability. But before that day I was perfectly capable of thought, and conversation, and writing. Even now I can "switch modes" and have coherent thoughts occur, with no labeling or accompanying narrative. I can distinctly identify concepts and transitions between them but there are no words involved until I open my mouth. So I dont know if it was just a hidden background process before that day. But it definitely "feels' different when its in the foreground or back, or nor there.

Disagree with your take about how much you can trust the GPS. Maybe on a sparse road network this may be the case, but on a dense road network, stacked roads with adjacent lanes (like on a highway interchange )it can be downright wrong, even after corrections. But like you said in those cases we would have to rely on other inputs to compute precuse lane level location.

Where are these figures sourced from? This data does not seem to be consistent with EIA reports which bucket the contribution of renewable (including hydro and biomass) closer to 20% for 2023.

Hello, I am interested in your area of research. Would you mind linking to some of your work?

Another season of tech bros ruin everything.

I worked in this industry. It used to move slow and consistent. Incremental progress or evolutionary improvent some used to call it. Wisdom borne from time and experience culminating in modules that ran on hundres of millions of cars, they to five years to finish but golly was it finished, no updates needed. They sold to every competitor, and even our own suppliers. Across the Atlantic and the pacific they scoffed at our POS cars, flimsy plastic trim, akward power trains. But, the beating heart of their cars ran our code.

Lots of grey beards, round tables, lecture rooms, the new kids like me squeezing into whatever room we could find to listen in. For some of these geezers their day job was just to investigate, educate, bring up the next generation. Some just sat around doing mostly nothing at all, schmoozig around the coffee machine, except when an exec or a new hire got a smart idea, skewer and stop them dead in the tracks, back to caf. They used to brag about how refined their bom was and the lengths they went to test the foundation that we now stood upon.

The age of #innovation. New ceo, new board, new directors. We aren't a car company, we are mobility! We are SAFE, scrum, stories, velocity! 5 years? No! 1 year, or else. That's how the apples success don't ya know? Features! Bugs? Bugs don't have story points and we aren't in the business of shipping bugs so why are you talking about the last release? Why does your test bench cost $5mil, can't you do that with a raspberry pi and a beagle bone? Why do you have so many testers and QAs, this team we hired from the valley is gonna white the AI that can auto-test everything. Why are you paying so much to license this esoteric tool chain? O P E N S O U R C E buddy! The car is a phone ...with wheels!

The grey beards are gone, picked up and left when the winds changed or forced off the boat altogether. No promotions unless you're a yes man. SV kids that have never opened the hood of their cars or been around at a company long enough to see a product live and die in the market. More product managers than QAs. If you have a mortgage or kids, better put up and shut up.You get the idea.

Assuming youre not a quiet quitter , youre not double dipping and you have some interest in your job. I'm pretty sure WFH is more productive and efficient. I'm pretty sure corporate knows this as well. They might even have the numbers to prove it but don't wanna show it. BUT i think the reason they want us to return is that if we stay home.. we will use the efficiency and productivity gains to optimize our personal lives and not the bottom line. It would change white collar culture fundamentally and that would not be good for the status quo.

Style nit: This is a badly written article; it about to a series of inconclusive quoted from experts duct taped together.

General observation: Discussions about not eating meat in popular and social media seem to forget that 2/3rds other world don't exist. India, te most populous nation consists of 30~40% vegetarians and the rest have a very low animal protein diet compared to western standards. This is the same for much of east and south asia. The diet is heavily plant based, is healthy, nutritious and delicious, and does not contain much processed ingredients. It has been this way for hundreds if not thousands of years. Animal farming culture is very different and less industrialized. Many countries don't have a dairy industry to speak of even though dairy products are consumed. Whether you're a non meatertarien on nutritional or ethical grounds, the east seems to have an answer for you. So you can stop eating meat...or you know eat less of it and still have a good time. I'm not sure why we in the west keep talking as if it's not possible without having some conglomerate reinvent meat for the 11th time.

What a jarring style! Is this a twitter thing?; No capitals and single spaced everything... Don't you have to go out of your way to do these days with auto formatting and all?

I've seen this style become "popular" and I have nothing but morbid fascination.

There needs to be more articles like this, far too often the answers on SO and the like is canned and dissimissive; "you don't need to optimize because who cares youre writing a crud app anyway".

Best I found was the giving the first task without a deadline, they claw their way through it and get it done asap or you get a series of excuses for a week, or somewhere between the two.if they ask you when or with what quality it needs to be done,it right off the bat it's good sign.

I have brought up a dozen or so freshies over the last thre years, with mixed results. My approach has changed since the beginning. Initially I would spend a lot of time; casual chats 1-1 and with teams to establish personal bonds, long sessions going over documents, the domain, active support and coaching over progressively harder tasks. This was not successful at all. Now, I just drop them off a cliff. Within the fist week, I have a short chat to get a feel, and throw them a non priority not too difficult task with no deadline. The ticket contains barely enough information. I add them to a few chats, point them to the docs home page and say goodbye. Based on the turnaround time and the quality of the work submitted abd how they go about seeking help I get a REALLY good gauge about their aptitude and attitued. They are either active about doing the task or they putter around and come up with excuses. Don't care much about code quality unless it's actually horrendous. This is great at catching ppl that faked their was through the interviews, the leetcode monkeys and other less desirable traits. Based on this the next task either involves a lot of collab or little to none. As and Bs get a difficult independant task, C's get an easy to medium task that needs a lot of interaction. In both cases they are "prod" issues that, the importance of the delivery and the deadline are stressed, they have to do an internal and external demo at the end. Team members are on standby for support or takeover if absolutely needed. This approach is WAY more sucessful. And stressful as well for the newb, but trial by fire seems to be the best way to get people integrated and being productive. Everything is learning on the fly, domain, process, culture, tools, everything. Compalined about not enough docs? Ok you go make the docs? Didn't like some part of the process? You make sure it changes. Didn't get enpugh support? You schedule the support call.

The biggest learning for me was that the amount of time spent coaching was inversely related to the "success rate". For those who genuinely wish to learn whatever the approach is makes little to no difference, for the others it makes a massive difference. Some hate it initially, but the consensus is that they all appreciate being a valuable contributor. Noone wants to be stuck in the back cleaning up docs or writing sorry tests for so done else's shitty code or doing wild goose chases or ,"ramping up" for months.

We have a strong team/collab culture. Everyone is "nice" the worst thats going to happen is that people leave you on read. My advice to all is to not worry about "bothering" people. Bother as many people as possible, ask all the dumb questions. You DM 10 people or post in a GC with 50ppl the same question in a minute. If I don't have the time I won't respond, but someone else will. If you need I'll stay on a call with you for hours while I do my work. So I actually think the amount of support available remotely is much more than the office, if you get over your hangups.

Struggling and being lost, wasting hours or days on the dumbest issue are all part of the process and there's no way around it, so the sooner you get comfortable with it the better. We work in domains where Google runs out of answers very quickly, the SR guys are still figuring things out and half the time noone knows what in world is happening right now. Getting on your own two feet is your responsibility.

C++, c# , python

If that was the only see you'd see a lot of work trucks changing tyres as often as they change oil, which does not happen.

Candidate supply is high quality is low.

Ask a NCH, even from prestigious school with advanced degrees to investigate an issue and write a report. 3/5 chance you end up with a steaming pile of doodoo.

I get the impression that some people think there is a silver bullet that we are not using because the big bad corporations are keeping us down. But...there's isn't one, and there are no free lunches, you always have to break the egg to make the the omelette.

I'm not sure there are any solutions other than customized and active management. Have lead two teams over the last 3 years. I'm not a manager, a mere scrum lead, that entails more of a frontline people/technical leadership position in my org as opposed to process evangelist. Both teams Ive had the exact same approach with at least in the beginning; people over process, autonomy over oversight, explicit expectation of no more that 80% commitment, flex time etc etc a healthy approach as far as I was concerned. The first was brilliant sucess to the point that the team was naturally agile, scrum was a joke of a projects, and I actually started cancelling dayil stand-ups because they were a pointless meeting. Over half the team turned into overachievers, we actually had to start forcing people to take time off to guard against burnout.And not PTO mind you, unaccounted flex time as a courtesy for good performance.

The second went completely off the rails. Near total underperformace, maybe on average 20% utility, people trying to game the system and cheat the team, esp with flex time and PTO. Why I have no clue because we never changed our policies, "I don't want to work today" has been a valid excuse our org. The larger org is so cooperative, that you could check out in the middle of release if you wanted to, no questions asked and people would cover for you, because there has always been an underlying trust that you do you best when you can and you would do the same for your mates when the time came. This was so widely abused that I have to take 2 sets attendance, one publicly and one on the side (the latter is where I count how many times grandma died), I'm having to chase people for deliverables, stand-ups are daily and an interrogation session when I have to publicly shame people for trying to cheat their teammates. One guy actually posted his second job on his linkedin(he was axed). And now I have to wave the big hammer of looming layoffs around. Overall a pretty miserable situation. Finally after many draconian measures there is a glimmer of acceptable performance.

I would really like an invite to this if someone could hook me up

Terrible article but yes probably. The amount of people , that have joined the industry, with no knowledge, no knack, no appreciation for the craft is way too high. A lot of them were just drawn by the lure of easy money and now I have to deal with them I don't want to. They can smash LC but can't wrap their head around a single class in an existing codebase. I am tired.

After a decade in the auto industry, I can confidently say that the difference (in quality) between FCA and others is not marginal. There is a severe lack of sound engineering during development and process control in manufacturing. All OEMs screw up, but FCA just manages to do it consistently.

I have been on both sides of the fence on this one...and it's rough. There are/ were people making ludicrous amounts money that did nothing, or openly did a second job.But it didn't matter because there's free money, and the workaholics made up for them, and management was too busy patting themselves on the back. Now there's "productivity goals", and pressure and an everpresent threat of layoff. I see people working late , overworking and trying to game the metrics.

Got into it for a buddy, we became leading cofounders along with 5 others. It was in ag tech before ag tech was a work. I had expressed that I had no knowledge or interest in the buisness domain but I'm in to because I like the tech and the people.

Fast forward a while and we get to the cold calling stage. And I'm getting frustrated because I'm wearing 25 hats and running surveys and whatever, and we don't have good leads , we HAVE to start cold calling and I whip up a list of a 100 or so numbers and call a meeting and say , "look we have to go through these" , absolutely noone wanted do to it, not even the guy who's idea this was. I walked away shortly after that and it never went anywhere.

Not an employer and I'm not a fan of RTO personally, and I've figured out how to remote work.i do help with interviews and I do have to say our success rate of good hires kind of went off a cliff with WFH, hires that we would have expected to excel absolutely flopped. Now it may be that we as a company or group are not geared with our processes to properly bring up ppl in this environment,becaus we expect a basic amount of integrity and work ethic from people, which is starting to look like a bit much. We actually have a very relaxed culture, no unpaid OT generally and unchecked flex hours...all on an honor system, I see a lot of abuse from the COVID hires and I worry. So I see why management isosing faith. Even I'm starting to pitch office days to get people moshing.

Y'all ain't work on projects with NO docs and no OG devs. I'll take an outdated Google doc over nothing and day of the week.