cyb_

Code review is where many of the design & code quality problems are observed/highlighted.

> Employed full time: Median usual weekly real earnings: Wage and salary workers: 16 years and over

> 1982-84 CPI Adjusted Dollars, Seasonally Adjusted

> Data measure usual weekly earnings of wage and salary workers. Wage and salary workers are workers who receive wages, salaries, commissions, tips, payment in kind, or piece rates.

In other words, moving money/spend from non-AI projects to AI projects/cost. This includes trimming the bottom X% of performers to reallocate that money too.

In most cases, it is not about current productivity or AI doing people's jobs.

I've seen a number of stories about LLMs going rogue and messing things up (dropping databases, making unwanted changes, etc). Also, apparently there are security concerns with the MCP protocol itself.

https://www.dmagazine.com/food-drink/2023/05/why-jalapeno-pe...

https://www.goodreads.com/en/book/show/42397849

I found it helpful in understanding the underlying causes of my own feelings of burnout. Also, don't be put off that the book says it's for women. The core lessons seem to apply to everyone.

(comment copied from earlier conversation on a similar topic: https://news.ycombinator.com/item?id=35849384)

JPEG XL support has officially been removed from Chromium https://news.ycombinator.com/item?id=33933208 (292 points, 378 comments)

> These massive trucks are actually safer for their occupants, but far more deadly to the people outside

We used to say that the process will never turn a mediocre engineer into a good one but it will absolutely turn a good engineer into a mediocre one.

In general, I've observed that a lot of these heavyweight processes are used as a substitute for high quality engineering leadership. They are not a good substitute.

When I've seen this happen it usually boils down to communication problems. The solution is often to talk to the reviewers _before_ writing the PR.

For example,

1. Disagreement about the problem/solution - hash out the design first, then write the code

2. Disagreement about priorities - align expectations before investing too much time in design or code

3. (etc)

Yes, communication is hard. Unfortunately, it's really the only way to get things done with other people. Building decent communication skills is a worthwhile investment for all SWEs

In my experience, simple solutions are not the lazy minimal-effort ones. It takes a lot of work to distill complex problems down into simple solutions.

One thing I noticed is that the earlier research took into account productivity increase of the employees due to less commuting time. This certainly benefits the employee and probably the overall economy, but maybe not the employer.

1: https://wfhresearch.com/wp-content/uploads/2022/01/Barrero-A...

https://www.goodreads.com/en/book/show/42397849

I found it helpful in understanding the underlying causes of my own feelings of burnout. Also, don't be put off that the book says it's for women. The core lessons seem to apply to everyone.

Higher != High

> Named davemaoite after prominent geophysicist Ho-kwang (Dave) Mao, the mineral is the first example of a high-pressure calcium silicate perovskite (CaSiO3) found on Earth.

IME, many hiring managers want to see passion (desire to focus on the user/mission), drive (evidence you will work hard), and humility (ability to be a team player), in addion to technical skills.

Displaing corresponding negative traits can really undermine their view of you. For example, cynicism, ignorance/resistance to hot/new tech/approaches, lack of interest in learning on your own time, condescension for decisions they have made, disdain for the hiring process, etc.

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