danmg

It's only a very small minority of engineers who do. Unless you're a PE and you get to sign off on large development projects, there's no real accountability.

No matter how much teeth a governing body has, it's always going to be gun shy about denying people their livelihood. They're only going to go after the most egregious and flagrant problems. As long as the transgressions are mild, they pose no real danger to those who want to violate whatever ethics code are in place.

Most queries don't require further action.

You can glean the information you were looking for from the results themselves. This is particularly true when you use google as a spell checker.

Thanks!

Very interesting, but every one of these executives I try on my fairly stock Ubuntu system returns 'run-detectors: unable to find an interpreter'.

I'm invoking them with 'bash -c'.

It's disingenuous and factually incorrect to compare WSB with a DDOS takedown crew running a tool against scientology.org.

WSB is legally sharing trading information and making informed investing decisions based on public information. What happened with Game Stop is completely predicated on large investors, who should have known better, buying positions that exposed them to an infinite amount of risk.

The short squeeze is the reason this is happening and not "ancillary." The hedge fund took these positions because they thought they were a form a free money. A better analogy would be "The Producers." The audience just walked out of "Spring Time for Hitler" for intermission and they're humming the songs and laughing.

It's not a pump and dump. It's a short squeeze. It's nothing new. It's the plot of the 80s movie "Trading Places."

A hedge fund bought short position futures contracts for 120% of the available stock on the market. That's the underlying reason the price is going up: because they're forced to somehow buy more than 100% of the available Game Stop stock because they agreed to sell it to the people on the other end of those contracts for a set strike price.

It leaks memory on every line it evaluates.

Is this really DFA-less? Isn't the look-back table you construct just encoding the DFA?

The optparse-generic library in Haskell generates a CLI directly from a struct.

The part didn't break. Someone who thinks they know better decided to make it not work, and complicated some normal person's life with some security theater.

If a manufacture intentionally made a product they sold you not work, much like how Tesla disables fast charging capriciously, it would be a violation of the Magnuson-Moss Warranty Act.

You're really going to scrap your car from 2015 because the off-brand android doo-hicky they stuck in it hasn't been updated?

Even if you're technically inclined, it's not like installing some community provided roms image on your slightly out-of-date flagship phone. The device likely has some proprietary aspects to it which would render it useless even if you attempted.

Not that much content either at least on the "web".

QuickCheck was probably the thing that stuck the most when delving into Haskell. While, I don't use Haskell daily, using some kind QuickCheck derivative in whatever language I'm working in is something that has stuck.

It makes doing "TDD" much more appealing as you're not stuck thinking of the test cases all the time. You run it long enough, add any counter example it finds to your test suite.

They told people just to make html5 webpages for the first year or so of the iPhone.

The first third party native apps were people who managed to get the gcc toolchain to emit a binary that the iPhone could run.

Then the App Store came out a few months later. Native apps caught on very well over just making html5 sites for iPhone users, because, in a lot of cities, AT&T's network just couldn't support all the users' very well. Even then, you were limited to a max of something like 20 (?).

Win32 API.