knightofmars

It's not that simple. This article covers both the original claim and the counter claim that the video you linked makes.

It comes down to numbers and frequency of this type of event.

https://www.theatlantic.com/science/archive/2019/04/why-are-...

Do you have to deal with gift cards legally obtained but obtained anonymously using illegal money?

E.g. https://news.cybersixgill.com/how-gift-cards-are-used-to-lau...

I suspect your perspective is based on your personal exposure. India has a lot of people. As such, they have a lot of content producers. Some of which will naturally be "a few years behind". There is still a significant amount of modern and "cutting edge" content being produced from India.

I was about to reference this book in a separate comment. Glad I checked if anyone had already mentioned it. It's an absolutely wonderful read.

https://en.m.wikipedia.org/wiki/The_Diamond_Age

It's funny when people generalize this way. You cherry picked specific scenarios as if that suddenly supports your claim that ageism is well justified. Anecdotally, I've worked with engineers across age ranges. Sure, there are the "rest on their laurels" types who stagnate in their careers. But there are also battle hardened veterans who can debug issues that are mind bendingly difficult to unravel and are happy to stay as IC. I'm curious what metric you'd pick to validate the claim that "...young fresh grads are running circles around old timers." Because based on the quality of the code and other observable aspects this isn't the case. Google introduced a whole new programming language (Go) because fresh grads weren't running circles around anyone and it was easier to go that route than get them to parity with the industry veterans.

There's a history that partially explains why this is.

https://news.ycombinator.com/item?id=16353398

Nonsense, they need raise the social security cap on income. This is typical USA politics. Move the retirement goal post instead of fixing the system.

I don't know that your experience is but I've worked on many products that are 10+ years old. Additionally, I'd take 3 old time engineers over 6 new engineers in a heartbeat. The problem is that every business wants to cut labor cost because that's the MBA way to do things. Why pay USA wages to someone with 15+ years of experience when you can hire three new beginners in the USA or an entire team in another country (again with less experience) for the same amount? The part you're missing from your analogy is the speed and quality of the bridge to be built. Want it done fast and right? Hire the engineers with experience. Want it done fast and possibly going to collapse and end in a lawsuit in 5 years? Hire those idiots.

Wow!

https://sciencedemonstrations.fas.harvard.edu/presentations/...

These people are dangerous and the ones I watch for the most. I see them as a somewhat dark manifestation of the "Peter Principle". They are charismatic people full of ambition who want to climb the corporate ladder but lack the skills, leadership ability, and knowledge to actually do so based on merit. Some common behavior I have observed, 1) they never deliver bad news to leadership and are willing to lie or misrepresent to achieve this 2) they never will be responsible for the failing project (which they've caused to fail) and will immediately find a way to move to another project 3) they take credit for all successes regardless of their involvement in those successes 4) over represent their own contributions and constantly talk how busy they are and how little work everyone else is doing.

Combining the above they will move from project to project and position to position once a year or sometimes two years leaving the team or some poor soul who was recently promoted to take over their mess. Then when the project continues to fail they can shake their head to their boss and say, "Everything was on track when I left project. They must have really gone away from the original design for this to happen."

I agree with you here. A parallel example being the IRS and tax reform that's prevented by private companies in the tax preparation domain.

You're being down-voted for some odd reason. This response is very accurate with regards to the types of crime that happen in most major cities.

EDIT: Having read the additional comments I understand that the perspective is those in US cities versus other locations in the world. The crime being described is common in major US cities.

IMO, I think this is a valid question (though asked a bit crudely). To generalize, it's because someone who has done JavaScript programming can point to NodeJS and say, "I'm full stack." Which, while technically true, skates over the reality of NodeJS as a less than ideal backend (see Ryan Dahl and the dawn of Deno). Second, it's more lucrative to bill oneself as "full stack" even if in reality a person isn't. At one point in my career I would have considered myself "full stack". Over time I realized that a "full stack" engineer is a jack-of-all-trades type, which in theory, can be valuable in the right circumstances as an individual doing work alongside non-full-stack engineers. Asking a room full of "full stack" engineers to design and build a product of any complexity above CRUD will naturally lead to a self-sorting of UI/UX and server side engineers.

The most important question when upgrading audio, "What's your price range?" There are lots of options.

For example:

Sony SSCS5 Bookshelf Pair $100

JBL Stage A130 Pair $300

ELAC Debut 2.0 B6.2 Bookshelf Speakers $340

And on up!

If this is what you currently own (https://www.logitech.com/assets/52567/3/z333-multimedia-spea...) you're likely going to need to purchase an AMP as well to drive your new speakers.

You might be able keep your current setup, remove the existing Logitech speakers, and use the L/R RCA out from your sub to the new AMP (depending on what the sub is outputting to the existing speakers) and then wire your new speakers into the new AMP (you'd need to figure out how to convert the output correctly to do this however). That should keep your handy volume control knob still functioning.

That said, a simpler approach if you're willing to give up your control knob and headphone port, you can just run the input to the new AMP and then run the sub out to your z333 subwoofer.

I recently picked up a Fosi Audio BT30D Bluetooth 5.0 Stereo Audio Amplifier 2.1 for my office. You won't get wall rattling volume levels with it due to the wattage output but (in my opinion) most people don't need that for a desk setup. It's not expensive ($90) and is nice and compact.

What type of organization have you been applying to? (E.g. Google, Netflix types? Enterprise business types? Start-ups?)

What type of work have you been doing the last 16 years? (E.g. PHP web dev, Enterprise Java/.Net, etc.)

There is nothing surprising about this. In the eyes of VC or the acquirer the idea of someone having "earned the stock" means nothing without a contract that says they've earned it. People need to stop gaslighting themselves into thinking that the company they work for or the company acquiring the company they work for will "do right by them". Capital doesn't care about you, your mortgage, your dreams, or anything else. Stop pretending it does.

This reminds me of the short story "Computers Don't Argue" by Gordon D Dickson. The format is a series of correspondence between individuals regarding a book. The plot starts with a man attempting to deal with the situation of having been mailed the wrong book by an online retailer. It then proceeds to take a turn into the dark.

https://www.atariarchives.org/bcc2/showpage.php?page=133

A "senior" title often equates to a pay range in companies. This can lead to employees that want/need to get paid more (and leadership wanting to retain/hire them) getting a senior title without the expected experience.

You're lucky the CEO had connections that somewhat panned out. I've experienced the "connections" based C-suite hire that was a complete and total net negative. It took 3 years for the removal to happen. It was a painful 3 years.

>Because it's not necessarily either bais or that Republicans lie more, it could also be that Politifact is asked to rate statements that are obvious lies by Republicans more often.

Agreed, the statements that Politifact chooses to cover are contentious and have high visibility. In the specific set of data points that were used to evaluate Politifact, a larger percentage of the statements made by Republicans are classified lies and more harshly (see article below from 2011). This proves nothing about the overall number of lies made by individuals within the Republican and Democrat parties. There are numerous ways this sort of situation within Politifact can come about even after excluding bias from Politifact. For example, a unique time period in which a small number of individuals who identify as Republicans are independently making more outrageous claims which skews the result. Or a time period in which a specific talking point (generally proven false) is being pushed as a narrative by a portion of a party but not a majority of the party (e.g., the 2020 election was stolen, or Donald Trump colluded with Russia during the 2016 elections).

Point being, reaching the conclusion that Republicans lie more via Politifact or the findings of the original study is a fallacy. And reaching the conclusion that Politifact is biased is also a fallacy.

The original article here: https://archive.ph/Drhw

Did these people run "always on" sockets in their houses? Any time I have an issue, I flip the physical switch off and then on and lo and behold the lights turn on.

"...things like SOC compliance." This is an important point. If you work in a regulated industry or work with software used in a regulated industry you need a "paper trail". Having to document and follow a process is often frustrating to people who work or have worked in industries that don't require it. That said, a poorly implemented process in a regulated industry is even worse. As you're overloading teams with busy work and likely still failing to meet the requirements of the regulations you're following. Regulated software is not a place to "move fast and break things" that's what prototypes that never see the light of production are for. Build it without regulation to figure out how to do it and then build it again following the documentation process. It may sound odd but having a second chance to correct errors of assumption from the first time around is quite valuable, buying information when done right is a great tool.

Exactly! Estimates are useful and volatility is real.

This! Reading in general manifests to others as if you have superpowers at times. Whitepapers, RFCs, manuals, API docs, regulations, devour them all and the doors will open so fast it will make your head spin. General advice to all, don't get bogged down thinking you need to memorize every algorithm and data structure to be a great programmer. It's more about understanding the domain you work in and knowing how to "stand on the shoulders of giants" within that domain.

I feel like you don't know that you're talking about. That's not meant to be an insult but to highlight the fact that "feeling" doesn't matter. Because my feelings about your statement has no bearing on the accuracy or content of your statement.

They are a memory test not an intelligence test. If you truly wanted to measure intelligence it would have to be based on a priori knowledge and not on the ability to memorize algorithms and their implementation.

The irony of technology workers who constantly express their unhappiness and frustration with being micromanaged telling a discipline (teaching) how they should be doing things.

Hammock driven development is real.

https://www.youtube.com/watch?v=f84n5oFoZBc