ascotan

>>>Recent research shows that developers—especially women and older engineers—face a “competence penalty” when using AI

and why did this study (performed in China I might add) find that women and “mature age” (which is not defined in the study) have less usage of AI tools?

>>>? We suggest a new barrier: using technology to assist task completion signals a lack of competence to perform the task independently.

So basically the study suggests that older engineers and women are reluctant (and especially women) to use AI tooling because they feel they are being judged more on non-technical competencies.

This study may have a strong cultural influence but I would say that one thing they noted I’ve also seen. 41% of engineers in the study had used AI 12 months after the initial rollout. This aligns with my observations. Some people are struggling figuring out how to adopt in their day to day while others are full in.

Oof. All coding standards have to be written as an RFC document?

“virtually all” - said the three anonymous sources familiar with the matter.

correct. the push for dispensaries has been financial not medical. now that we are getting large scale trials there will be more real evidence to show the public health effects. my guess: it will go the way of smoking eventually. realization around public health effects -> cost of those effects on public services -> taxes and costs go up. I'm curious as to why heart attack and not stroke. seems like bp isn't the only thing at play.

i thought apple is already doing this on all it's devices?

The article is misleading. The sale of geolocation data can still take place but not for precise locations. The bill prevents the sale of data that can identify you within 1750ft. You can still be tracked just not precisely. i.e. companies will just sell fuzzy geolocation data.

so.. hand over your data to china to spite orange man. yes excellent move.

yep. and anyone not aligning to the anti-american reddit rants here get downvoted. shows you where HN is going.

The implications are far reaching beyond cell phones. any service that stores location data for it's user is subject to 4th amendment expectations _regardless_ of an opt-in. The court specifically rejected the argument that by opting-in the user is abrogating their privacy rights. If you centrally store location data you have an obligation to protect that data under the 4th amendment as private and would require a warrant.

The impacts here are with food delivery apps, fitness apps, weather apps, cloud services, ad tech agencies, data resellers/brokers, etc.

this proposal is an extension of the WH crackdown on what it sees as misuse of USG funds for things that are deemed not in the best interests of the USG.

Among other things this proposal attempts to prevent:

1. prevention of DEI related grants

2. prevention of grants promoting anti-american ideologies

3. prevention of gain-of-function research (think covid-19)

4. prevention of ai-powered social media censorship research

5. prevention of FEMA dollars going to help undocumented immigrants

6. prevention of foreign aid dollars being spent in africa on gender ideology

It would but restrictions directly into the grant awards give strong tools to the USG to suspend the grant and prevent the money being dispersed via a subrecipient.

clickbait. they knew what they were doing.

there's a long history of X is dead posts. PHP is dead, Java is dead, jquery is dead, unix is dead, REST is dead, graphql is dead, microservices is dead. and of course none of those things are dead. but... they're great for clickbait.

here's the uncomfortable truth. most software engineers are good enough to hire.

i've seen a few interview types in my time:

1. technical interviews run by nontechnical or junior engineers who can't judge technical talent. this typically produces sub-par hires. imagine you are made the director of UX design and you have to hire someone but know little about the industry. what type of hires are you going to get?

2. technical interviews that focus on CS skills. can you write a red-black tree in Java? can you write a bubble sort in haskell? The problems here is that this has bias towards new CS grads that dont have much industry experience but just took tests on stuff like this in their degree. google pioneered this style of interview and it's taken off as leetcode. the problem is that experienced devs dont typically write bubblesort algorithms. this type of interview is biased toward younger out of college hires and codecamp hires that have little experience but gring on leetcode sites.

3. technical interviews that have too many opinions for a hire recommendation. this seems to be a new trend where you need 3 or 5 or 7 thumbs up to get hired and any negatives sink the candidate. this does raise the bar, but typically what i see is someone on this panel has a high opinion of his/her abilities and gives everyone they seem a thumbs down.

What i've found is that soft skills and team dynamics are > the technical accumen. I can teach you how to write go(lang) but its much harder to teach you how to influence your peers or to communicate effectively.

Experienced devs probably dont know how to ace your leetcode interview, but they do know how to influence and communicate and when to stay away from bad ideas. You dont get tested on these things. It's analogous to a being combat veteran. You've been there, you've done that you know how to survive. You might not know the new tech, but that can be taught. I have never seen an dev not be able to pickup a new platform/language/skill within 6 months of hire - anywhere.

Here's hoping this will get better one day but i'm not holding by breath.