karmicthreat

My first paid developer job was writing backend code for what I would later learn was the Canadian mafia. I was doing some backend and embedded work to build super shitty gambling kiosks for them. They already had some person "managing" project and the Indian contract house that was building flash games for the kiosk. He was useless, so I was stuck figuring everything out. Including getting things running on a then obsolete HP Itanium Integrity server with an old insecure version of Fedora on it. Plus figuring out how this was all going to work in the Dominican Republic where power was not a given at any particular time nor was connectivity. These kiosks would be scattered across 10's of casinos down there.

Eventually things got weird, and I figured out that it was probably a form of scam against their investors. Since they wanted things very insecure and unlogged. Then they wanted me to come down to the DR and help with setup there. I bounced at that point, I was unwilling to give them that sort of power over me. They were in with the former president down there and I would have been at their mercy.

10 ish years later I would hear from the "manager" again. He wanted me to help with an automated locker system. I helped a bit but once he begged me to go to an ATT store and recharge his prepaid phone I was done with him. (I did recharge his phone because I am a sucker for a sob story)

If someone seems scummy, DO NOT work for them. Your gut is probably telling you something.

That said, a good work ethic and a baptism by fire where you have to do everything can be an effective way to get your start.

Going to high levels of normalization also makes the code harder to understand. It's very extensible, but every system that I have dealt with that had high levels of normalization was a huge pain to figure out.

There is lots of inconsistency about hash behavior with the various repos (pypi, ruby gems) and tools (poetry, bundled).

For a long time poetry didn’t even check the hash. So the safer option is just maintain these artifacts yourself so you know what is going on and have your own policies on maintaining them.

Toyota isn't the shining star it once was. Cost cutting has pulled Toyota vehicles much closer to the industry average. As well as the general quality level of American and korean automakers improving over the last 10 years.

Notable exceptions being the Prius and some of the Lexus lineup.

Makes me glad I have been migrating away from bitbucket as I update projects lately.

Node-RED is a completely nifty piece of software and I hate it. Mostly because it doesn't do things how I like to interact with them (Not a visual programming person). Also it gives me flashbacks to dealing with Labview.

I don’t think it’s necessarily the best book ever. But for me it was useful for thinking deeper about how I and other people perceive things.

Yea, this seems more like a tool insurance companies will use to deny coverage.

Most sendgrid customers are in their public IP pool. They don't tolerate spam on those IPs because its difficult to manage with the spam lists. So they are definitely proactive about killing leaked keys.

I leaked one when I accidentally left one in a repo I was making public. Took 15 minutes for sendgrid to drop it after putting the repo public.

There are bluetooth enabled pacemakers and electrocardiologist can already wirelessly connect to pacemakers. I'm sure the industry can come up with something.

Not really sure what that pictogram would look like to convey that easily. There are safety instructions included though that mention medical device interference mitigation.

Maybe the easiest solution would be just put an NFC tag under the skin above the implant and have phones trigger an alert if they see it.

I don't think this is so much an Apple problem as a medical device manufacturer problem. These devices disable themselves in the presence of magnetic fields. Maybe device manufacturers should consider a different disabling technology. Or alert users when their device is disabled.

That's what is usually said. I don't think I've actually heard of this getting triggered. I'd like to think that global governments have this totally under control. Maybe the US does, but does China? In any case so far it's seemed like a whole "this rock keeps away Tigers" sort of thing.

In the particular context of Though Emporium this wasn't going to happen. It used an adenovirus that couldn't reproduce so it was only going to alter a limited number of cells in his intestine.

The technical requirements to this kind of limit the number of people that are going to really mess themselves up. I would be more worried about people accidentally releasing edited bacteria or viruses.

Jumpgate scratched the itch years ago and I was hoping this game would too. But its just not really a game yet.

Star Citizen is pretty much the proof that unlimited resources is not necessarily a good thing for a project. Constraints can help keep things focused.

Amazon would pay their employees in store credit if they thought they could get away with it.

These super tests are dumb in any case. All it ends up measuring is who is most effective at cheating. The people that came up with this system probably wouldn't be able to pass it legitimately either.

You can already buy screen printable resistor inks.

I can understand the author not wanting to deal with extra noise. But they did try to accommodate them. Forking and changing the contact info is probably the best tactic. The author didn't like that, but is probably the best outcome.

Don't do open source (especially a very permissive licence) if you don't want others using your code as a dependency.

Those unlicensed chips can be even worse than just a plainly nonfunctional chip. FTDI had this issue a few years back and the breaks were more subtle.

If I'm paying for a specific chip, I want all the reliability and QC I expect at that price.

But will they be good enough to let me play T. C. Vilabier's 26th String-Specific Sonata For An Instrument Yet To Be Invented?

The Replit CEO seems like a pretty fragile person. They could have turned this into an advantage.

It gets to be difficult to constantly come back to management for money at a small company. The MFA/Identity services want 3-12$/user. EDR wants 4-12$/user. Phishing training, same. VPN (fortinet in my case) same.

The 57$/User of MS E5 is starting to look like a steal.

That could very well be. It was quite a while ago.

I remember back in the day Jeff or Joel came on the somethingawful forums and started talking about their idea. They were resoundly trolled about how horrible their site idea is. Why would we want un-certified randos on the internet giving people advice?

Stack Overflow succeeded and SA is just kind of limping along. Though maybe now that Lowtax is gone it can just kind of maintain.

Rowhammer has been known of for over 5 years.

Is there any evidence of Rawhammer being used in a successful attack in the wild?

I think you are making a pretty big assumption that it would fail in the supreme court. It's not like the supreme court has abolished asset forfeiture either.

Those two radio systems are still used. Just that many states have CORS sites that post correction information.

My guess would be treat it like when you pull the chute on a Cirrus GA aircraft. Total loss, but you didn't die!