StressedDev

I am not surprised. First, it's a subtle bug. Second, in C/C++. a lot of times you get unlucky when reading uninitialized memory. Basically, the bug does not occur when you test the code on your machine or when you run the automated tests.

Another problem is writing good automated tests is hard and often skipped. Lots of software engineering teams talk about the wonders of automated tests. Unfortunately, many automated tests are not very good and either do not ensure the major functionality works or just do not test some of the code. There are also limits to how much time a software engineer has to test. No one can test everything.

Basically, I am not surprised developers make mistakes and I am not surprised the tests either did not catch this mistake or even did not exist. Software is very hard and software engineers are far from perfect.

Why? C# has added a lot of good features over the years including lamda functions, generics, private functions, string interpolation, LINQ, etc.

Create React App should not be used because it is no longer maintained. Here is its GitHub repro: https://github.com/facebook/create-react-app/commits/main/ . It has had very few updates since July 2022. This is bad because it needs constant updates because it depends on a large number of packages and those packages are constantly releasing security updates.

React has very good documentation and an excellent tutorial. Here is a link to it: https://react.dev/learn . I recommend doing the exercises. They really help you learn React.

If it's a fine, it probably goes to the United States Treasury or the SEC's budget. I also wouldn't be surprised if the settlement was not fully paid.

If a browser does not support modern TLS (SSL), it probably also has unpatched security flaws. Unpatched browsers should never be used on the Internet because they will get hacked.

Perhaps you should either file a bug with NetNewsWire, or debug NetNewsWire and submit a PR so it works with her blog.

Ad-based businesses exist because a lot of people (including many on this forum) refuse to pay for anything. During the late 1990s/early 2000s, people hated paying for anything and demanded that everything on the Internet should be free. Well, that led to the vast surveillance machine which powers Google, Facebook, and every ad-tech business out there. They need surveillance because it lets them serve more relevant ads and more relevant ads make more money.

The bottom line is if you hate ad-based businesses, start paying for things.

Substack's UI is fairly minimal and does not appear to have many anti-patterns. My only complaint is that it is not easy to see just the people I am subscribed to.

In the United States, Gun sales are heavily regulated and require background checks. Manufacturers and stores cannot just sell a gun to anyone.

Agreed - If you got a Computer Science degree from an engineering school, you probably had to take Linear Algebra as one of your required classes. Also, Linear Algebra is not that hard to learn.

I did this with a Samsung TV I got recently. I works great. I am really not sure why everyone is upset. If you don't want to use the smart features, you don't have to. All you have to do is not connect the smart TV to the Internet.

What put you off?

What makes Carta different? Why is offboarding more complex?

No one is overthinking anything. Carta's behavior is poor, self-serving, and definitely using a dark pattern. If they cannot promptly schedule a meeting, they should wave the meeting requirement.

Here are some other thoughts:

1) Canceling a subscription should be easy and take less than 3 minutes. There is nothing special about enterprise software subscriptions.

2) Requiring a meeting to cancel and then scheduling the meeting after the customer is charged a renewal fee is outrageous. This should never happen.

3) Customers tried to contact Carta and could not get help. This means they could not just "call up Carta" and tell them "Your shit is broken, there are no cancellation meetings for weeks."

The pre-college US education is not excellent. I know because I went to a US public high school. Here are some of my observations:

1. The standards are low. Here are some examples:

- My high school calculus class went at half the speed of a college calculus class. Some of the students still complained it went too fast!

- I took Spanish for 3 years. Native Spanish speakers laugh at my Spanish because it is extremely poor (poor pronunciation and I cannot read a Spanish newspaper).

2. Students and parents are more concerned with grades than with learning.

3. I know of teachers who have been punished because they had high standards. I know of one English teacher who was made a librarian because he failed half of his class. He was the best English teacher in the school, and he had high standards. I know he was good because I had him.

4. When I went to high school, I was surprised at how many students could not write a coherent argument in English.

5. My physics and chemistry classes in high school looked nothing like the classes in college. Basically, they were relatively easy, and I did not learn a lot. In the case of physics, the textbook also did a poor job of explaining concepts.

My main point is my experience with US public education was poor. Classes were easy, students were not pushed, and concepts were not taught. I don't think you can call a school which cannot teach physics, chemistry, or Spanish a good school. I also do not think my experience was unique.

Not in large corporations. Typically, this is what happens for full time employees:

1. The manager decides the employee should go.

2. The manager reaches out to the Human Resources department. They explain what the manager has to do to ensure that the employee can be fired without causing the company to get sued.

3. The manager meets with the employee and puts them on a performance improvement plan. Typically, the employee is given goals they must meet to keep their job. The manager documents the employee's performance. The documentation's goal is to ensure that the company can avoid a lawsuit if the employee is fired.

4. PIPs last about 3 months.

5. If the employee meets the goals, the employee is taken off of the PIP and stays on the team.

6. If the employee did not meet the goals, the employee is fired.

Note it is a lot of work and this has been going on for decades. There are a few problems with this process:

A. Teams are stuck with poor performers because managers cannot quickly get rid of them.

B. A lot of time, the employee on the PIP has no chance. The manager wants him gone and unless the employee does an amazing job, that employee will be fired no matter what.

OK, this is bullshit. I have worked for a lot of managers and frankly, almost all of them worked hard and tried to do the right thing. Managers are people too and we need them because they ensure that the right work is done, and that the team is solving problems customers, and the organization care about.

I am really sorry to hear that. I hope you find an organization which wants to remove poor performers.

The OP can report the security problem by going to https://www.alaskaair.com/content/about-us/site-info/report-... . I think this is probably the best way to get Alaska Airlines to fix the problem.

How do you know they are unwilling to fix this? My guess is it has not been fixed because the people who can fix the bug do not know it exists.

I don't think this is fair. My guess is the person who found the bug did not report it to a person who knew how to handle a security bug report. My guess is the technical people at Alaska will fix the bug once they know it exists.

I am not a lawyer but this line of thinking does not make sense to me. First, poster did not post any personal information. Second, the poster responsibly disclosed the bug to Alaska Airlines but Alaska did not fix it. The poster is now publicly disclosing that the bug exists. Note that the poster did not include repo steps for the bug.

The bottom line is we need a mechanism to ensure security bugs are fixed. Publicly disclosing security bugs when an organization does not fix the bug is a good way to do this.

Note this practice started in the 1980s or early 1990s because software venders refused to fix security bugs. The full disclosure movement was created because security researchers wanted the bugs fix and publicly disclosing them was the only way to get some organizations to fix their security bugs.

Thank you for sharing this.

If this is not by choice, I hope you solve your problems and I hope things get better. Please do not give up.

You will find work. One thing to keep in mind is the job market goes in cycles. Right now, finding work is hard but things will eventually pick up. Here is some advice for job hunting:

1) DO NOT GIVE UP 2) You don't need every skill the employer is asking for. What you need are the major skills the job requires and the ability to pickup the rest on the job. 3) Only apply for jobs where you are a good fit. 4) While job hunting, spend time each day learning a new skill. It can be a programming language, a technology, or something interesting. 5) Once you get a job, save lots of money. It helps you make it through lean times and sets you up for a nice retirement.

One last thing. If your depression does not let up after 6 months, I strongly recommend seeing a therapist and a psychiatrist. I wish you luck. Things will get better.

Some people don't mind living paycheck to paycheck. It has a downside but if it works for someone, I don't think judging it really helps.

This is a good example of why entrepreneurs, founders, and investors should make a lot of money. Frequently, they fail, or go for years making very little. Starting a successful business is incredibly hard and I wish shilin (the person who wrote the article) the best.

Software engineers are notorious for not wanting to support legacy devices and software. You see this all of the time on Hacker News. If you want more venders to support older devices, you need to change the culture. You also need to acknowledge the costs. Here are the costs:

1.Increased software development costs - Costs increase because software has to be designed to fallback to alternative implementations when the newest OS, browser, database, etc. features are not available.

2. Increased performance optimization costs. Older devices tend to be slower and this means software engineers will have to spend more time optimizing programs.

3. Increased testing costs - You need to test all features on older and newer devices.

The other problem is it might not be worth it to support older devices. Basically, supporting older devices may not be profitable (i.e. too few users who do not generate enough revenue to justify the increased costs).

The author appears to be someone who gets angry or very annoyed when he does not get his way. The author may also just not like change. Basically, he is upset he had to buy a new phone after 6 years and the new phone was different from his old phone. I do not think his behavior is productive or helpful.