rubylark

I think it's a difference in expectation. For some reason, people are surprised that birds have the same intelligence level as a human toddler. However no one wants an AI assistant that's as dumb as a toddler.

As a counterpoint, Jesse Ventura was famous before he got into politics. It's much harder to win when no one knows who you are.

I'm a third generation "woman in tech" (grandma did punch cards, mom did COBOL) and I haven't had any problems that I keep being told I'm supposed to have. I suspect discrimination is location specific. The most I get is the annoying "you guys..." pause to think "...and gal".

(PSA: "you guys" is gender neutral)

I am surprised how weirdly common it is. Something similar happened nearish me as well:

https://www.chicagotribune.com/midwest/ct-madison-arboretum-...

In this context, they are speaking of electrical efficiency, i.e. the amount of power lost to system impedance during transmission, not some abstract concept like effectivity. The efficiency of a transmission line is expressed as a ratio of power received at one end of the line over the power sent at the other.[1]

[1] https://en.m.wikipedia.org/wiki/Electrical_efficiency

The only reasonable explanation I can think of is that Chatterjee's motives and subsequent termination (which is not elaborated on) was related to gender discrimination. Otherwise I can't see what relevance anyone's genders has on the issue at hand.

Also: synchronicity

https://en.wikipedia.org/wiki/Synchronicity

I'll add an anecdote to contradict that argument:

I work in embedded, and the place I work restructured to have a dedicated software group. They hired young software engineers and focused on getting people who are good programmers without really caring what they were good at. Most people ended up being web developers and liked webstack.

We were tasked with making a handheld air quality measurement device with a touch screen that could pair with a computer app that we would also write. Most people on the team knew webstack so we decided on a HTML/CSS/JavaScript +SQLite that would run in Electron Chromium on Linux on the physical device.

So what went wrong? Well, electron is bloated for embedded devices and the mid-tier processor we were using chugged so much that it would get hot. Hot enough to affect the temperature sensors at the top of the board and throw off the gas density measurements. Our MVP was nearly done when we discovered this problem.

We had two choices: throw out the hardware or throw out the software. We ended up throwing out the software and starting over (in Winforms + C# if anyone's curious). I and two others quit as a result. It is _really_ depressing redoing something you've already done in a different language.

If we picked the lighter weight framework from the start instead of picking the language most people knew, we wouldn't have lost a year of work.

Would that not be the person running the AI? The one giving prompts and verifying that prompts are fulfilled adequately?

In the US, it depends on the waste services provider, city, and county. I've had garbage companies that offer compost and yard waste services and some not. Sometimes it's provided through the city or county for free or for a fee, though not everywhere

Do you have examples of wordy US signs that are only symbolic in the EU system? All of the ones I see on the article are either city names or pedestrian signs with complex instructions that I don't think could be conveyed effectively in only symbolic form.

The ones I can think of that are words only that might have a better symbolic notation are Dead End, No Outlet, and No Passing Zone.

Why not? If the airline has a policy that allows them to fly, why wouldn't they? It's not the people with allergies asking the flight not to serve other people peanuts, it's the airline itself deciding to do that.

Besides if someone has a contact allergy to nuts, I can't think of a place more likely for it to happen than a plane. One patch of turbulence, and your seat neighbor's peanuts go all over you.

It's not always only ingested food that is a safety issue. Some people have allergies that are severe enough that physical contact is enough to cause anaphylaxis. For example, there was a kid with a dairy allergy who died when other kids put a piece of cheese down his shirt[1]

[1]https://www.theguardian.com/uk-news/2019/may/02/boy-with-all...

I find this kind of assumption that "coders can't understand feelings" as a harmful stereotype and baseless assumption just because many of the comments here disagree with your take. Emotional intelligence* has nothing to do with it; sympathy does. You can recognize the emotions of others without feeling sympathy for them. You think the author is sympathetic, others here (myself included)...don't.

*Emotional intelligence is the recognition of your emotions, the emotions of others, how your actions influence the emotions of others, and how to regulate your own emotions. Ironically, by this definition, the author is the one lacking emotional intelligence. They didn't understand why they were angry, why others were frustrated or how to mitigate it. They still don't understand that just saying that you are at peace doesn't mean that you are. To me, the author is still brimming with hurt, anger, jealousy, greed, and pride, and because of these last three, I don't have much sympathy.

Not that uncommon in my experience. Depends on the kind of microcontrollers/embedded computers. Weaker ones are closer to the bare metal and need some EE during development. More complex ones with a GUI or that run Linux are mostly application level work. And for mid-level microcontrollers (the kind I work on), once the drivers are there, it's all application work.

The problem for switching from pure software to embedded is that companies like you to have EE experience, even if the job doesn't require it at the moment, so you can use it if you need it. Of all my embedded coworkers, only one was a pure CompSci major. The rest were CompE or EE.

Personally I consider myself more SWE than EE, and half of my job titles have been "Software Engineer" instead of "Firmware Engineer" or "Embedded Engineer".

Depends on the project. Most of the teams I've been on were 4-12 SWE for 1-3 EEs. These were usually mid-range microcontrollers with GUIs. It's typically only weaker, single-purpose embedded without an RTOS (like sensors or whatnot) that has 1 to 1 unless the company wants the project to drag on for half a decade.

I exclusively work on microcontroller projects, and my experience is the same. I've only worked on one project that really needed my EE experience to write some drivers. Once the drivers are there, it's all application layer for the rest of the project, which usually go on for 1-3 years for a team of 1 to 12 people.

Depends on the embedded system. I've only worked in mid-sized companies, and most of my projects were teams of 4 to 12 SWE-type with 1 to 3 EE for the project. Typically light ARM4 or weaker microcontrollers will have smaller teams, or no team, while anything beefier, like embedded Linux projects or anything with a UI, will have bigger ones.

Absolutely. This modchip is just a raspberry pi plus a couple parts. You'd have to try hard to get it to be expensive. The BOM for most embedded systems is going to be cheap unless you need some exotic hardware. It really does seem to ignore the amount of time this guy spent to get to figure out what parts he needed and where to solder them. If it was developed by a company instead of an individual, you can bet it wouldn't have cost "only $25 to develop".

Edit: fixed for clarity of thought

I really like this strategy. After one god awful experience at a company that led me to quitting after 3 months, I will not work for a company that doesn't show me a snippet of their own code. The whole experience at that terrible job could have been avoided if I could see their coding practices: early returns, gotos everywhere in C++, 7(!) different languages that compile into one >1GB executable over the course of an hour. They only did white boarding questions which told them a lot about me, but told me nothing about them.

I've had 4ish interviews since that job, and all of them gave an on-the-spot code reading assignment to walk through their code to find the bugs. It let me see who has old style coding standards, who takes advantage of modern C++ utilities, and that the interviewers are competent enough to walk through coding examples, too.

I find it super frustrating. There's been leaps forward in fuel efficiency, but car manufacturers compensate by making trucks and SUVs bigger and heavier. The newer trucks can fit a third adult in the front seat comfortably. I hope the Ford Maverick is successful enough that more manufacturers start making "little" trucks again.

Isn't the issue with your city, then? It's not like the film crew just annexed your street without asking anybody. Your city council approved it, likely after several public hearings. At least that's how it worked in my small hometown 25 years ago when a major Hollywood film shot there. They made a mess scattering dish soap on the streets and river front to look like snow and closed a public park for a few weeks. Lots of people were angry, but at the city council, not the camera people. The film crew only did it after a bunch of people in charge told them they could.

Perhaps they broke out a start of concave curve and used a grinder to get it the rest of the way there*. It would probably be labor intensive and fragile but it might work.

I'm going to disagree here. I'm a woman and I had the same results as every man replying here: I recognized all the science, game, and action terms and almost none of the fashion and textile ones. Never once when I have gone clothes or makeup shopping (always exclusively in person) have I encountered any of those terms, written or otherwise. I feel I might have been more familiar if I actually shopped online where these words might be displayed.

This is a baffling article. It is a mix of actual facts and apparently well researched journalism mixed in with completely bizarre claims like this:

> White-tailed deer and North American moose don’t normally share habitat; the deer’s shorter legs and thinner fur aren’t suited for the deep snow and subzero temperatures that moose prefer.

White tail deer range well into Canada (the entirety of which is north and colder/snowier than MN) and always have, from what I can tell.

It's like the person who collected the facts wasn't the one who wrote the article, and the author decided to fill in some gaps by just making stuff up that supported their thesis.

Definitely agree. Coding is so different depending on the language and the field. I'd also add:

4. Version Control

I've onboarded some new grads, and was surprised to find they don't teach version control in college. Students generally picked it up on their own, but I'd kind of expect at least 5 min of the first lecture of CSCI 101 to be something like "here's git and here's why you need to use it".

The problem with general statements with "every programmer should" is that programming has become such a diverse field that there are definitely things that not _every_ programmer will need. For example, as an embedded software developer, I would say that every programmer should know I2C/SPI, EEPROM/Flash, semaphores/mutexes, RTOS task scheduling strategies, assembly language, what a HAL is, etc (I don't see any of those on the list from my brief perusal). In my field, if you don't know any of those, you're going to have a tough time getting a job. But the reality is that most programmers don't need to know the majority of what I use day-to-day and I don't need to know some things they need like basic web UX practices or how to serve a terabyte of data that I'm sure is the absolute fundamental minimum required for certain other development positions.

Demanding a subject to actively participate in your study upon pain of vague and mostly incorrect legal threat is ethically wrong. Passive participation (like scraping) without consent is morally wrong, but since it doesn't cause undue distress to the subjects, it is not as big of a story.

The IRB in this case didn't consider this ethically suspect because "websites aren't people". And yet the study disproportionately targeted small websites where there is, in many cases, only one person involved.

Preventing wireless communication, even in wilderness areas seems like a bad idea. I remember a Reddit post many years ago (back when the concept of a internet post from the middle of nowhere was novel) from a bush pilot in Alaska. His plane had some sort of failure (not a crash) that left him stuck in the wilderness. But he had satellite internet that not only let him call for rescue, it let him pass the time by posting about the experience on Facebook and Reddit.

I'm curious to see if this really pans out. Seems like its a little pie-in-the-sky for "light trucks," whatever that means (anything smaller than an 18 wheeler? Or only small like a Chevy S10?). From my very cursory research several months ago, there's been almost no improvement in mileage in trucks in at least a decade. My 2008 Tacoma is no less efficient than the 2022 model (20-25 mpg). From what I've seen, the only trucks that come close to meeting the 40 mpg requirement are the fully electric and the Ford Maverick hybrid.