tachang's comments

tachang | 7 years ago | on: Security Issue February 2019: FAQ

For those wondering MD5 by itself is a terrible hash for passwords. It’s really fast and without salting you can build rainbow tables against it with reasonable speed.

If the passwords were salted it still means that a determined adversary can find your password relatively quickly.

Other better hash functions for passwords include things like bcrypt. Though I do understand it is a pain to migrate users over since you can only do it when they login.

tachang | 7 years ago | on: Conversations among German Nuclear Physicists at Farm Hall (1945) [pdf]

How did we end up purifying the amount of U235 needed?

I saw on another page "General Leslie Groves consulted with lead scientists of the project and agreed to investigate simultaneously four separate methods of separating and purifying the uranium-235: gaseous diffusion, centrifuge, electromagnetic separation and liquid thermal diffusion."

Seems like a ton of work.

tachang | 7 years ago | on: REST and GraphQL really aren't that different

The reason you'd do this is because you are probably planning to return the same response for all the HTTP verbs.

Like if you wanted to return a empty hash {} for:

  GET /
  DELETE /
  PUT /
  PATCH /
  POST /
I guess just being lazy.

tachang | 7 years ago | on: JIRA is an antipattern

What are you doing that I am not? Jira is slow as hell and updating statuses take forever.

Are you on an onprem version?

tachang | 7 years ago | on: Serverless Best Practices

I agree with this. Having a traditionally relational store can be a huge help: lots of people know it well, the disadvantages are well known, and everything is insanely mature. I dislike how the article tries to say that isn’t serveless’s fault when it is just a trade off.

tachang | 7 years ago | on: Massive Comcast Outage Hits the US

Some of you conspiracy theorists are insane. No Comcast didn't purposely do this. I can guarantee it was just a backhoe digging around. Happens more often than anyone would care to admit.

tachang | 7 years ago | on: How 'DevOps' Is Killing the Developer (2014)

For a react developer I'd say one level is understanding reactive design and maybe how you would implement it in pure JavaScript without react. One level below that would be how you would implement JavaScript and maybe a bit of knowledge how the engine works and shadow Dom.
page 1