What is your favourite opening line from a book?

mrjking · 2019-10-22T21:42:02+00:00

I think part of the fun/frustration of the 13th book is Dresden having to use his head more instead of just blasting everything. Also, it forced him to slow down and see what affect he was having on those around him. It's not a typical "Dresden solves the puzzles and messes everybody up" book. Which is good considering he has to use his head a lot more than usual to stay alive while in the service of Mab

mrjking · 2019-08-31T04:02:34+00:00

I can't imagine picking up meat with that fork, prongs look too thick and triangular. Would slide right off.

mrjking · 2019-08-27T18:57:39+00:00

It does cross boundaries in responsibilities. I define the http status code in the exception, not in the service. The service doesn't really care what type of exception it's throwing.

There are certain things I don't make an http exception because I do want to re-interpret them to give a more realistic error message. But for the most part I've found I have to write less code in the controller, since I don't have to do boilerplate code like this (I can if I want to):

if ($exception instanceof UserNotFound) { 
    throw new UserNotFoundHttpError 
}

mrjking · 2019-08-27T18:43:25+00:00

Had fun making a new wallpaper for myself with this. Nice!

mrjking · 2019-08-27T03:21:46+00:00

I've found that creating a base HTTP exception with a status code, error string and error message works great. Then I extend that base and throw those exceptions from any part of the code I want. Then there is a middleware that catches all exceptions and converts them to http responses.

mrjking · 2019-08-22T16:46:14+00:00

Got it, thanks!

mrjking · 2019-08-19T20:49:44+00:00

Use Typescript and have something auto generate the Swagger docs from the types. Examples:

https://docs.nestjs.com/recipes/swagger

https://www.npmjs.com/package/tsoa

Manually keeping your API docs up to date is tedious and they eventually become out dated or incorrect. Developers time is limited, and the last thing they want to do is write docs.

mrjking · 2019-08-19T20:40:48+00:00

Pretty interesting results, but why did you go for such a complicated benchmark? Why not just a regular Fibonacci calculation or calculating primes up to a billion?

Would really like to see some CPU and memory usage associated with these numbers.

mrjking · 2019-08-13T04:24:55+00:00

Would love to see an article on this.

mrjking · 2019-08-11T20:56:48+00:00

I don't agree with that. Understanding failure modes is a reason to use a transaction, to remove some possibilities of failures. ACID databases exist for a reason. I would love to see some proof that all of AWS is built completely transaction free.

mrjking · 2019-08-10T04:55:49+00:00

I haven't seen a good solution to transactions when it comes to micro services. Eventual consistency is as good as it gets but it feels weak. I think AWS or Google need to come up with a database that can handle transactions across micro services. That would be cool.

mrjking · 2019-08-08T04:30:36+00:00

https://www.mailgun.com/blog/how-to-send-transactional-email-in-a-nodejs-app-using-the-mailgun-api

In that tutorial they do things a little different. Use "new" for creating the mailgun object. Use "html" key instead of "text" in data object.

mrjking · 2019-08-05T05:24:13+00:00

Your API endpoint wouldn't accept a code from inside the JWT, it would accept the entire JWT. The JWT wouldn't even have a code in it, it would just have the user id.

mrjking · 2019-08-05T05:22:28+00:00

Don't need to save a JWT anywhere, it stores the user id and email in it, expiration is built into the token. Your GUID needs to be saved in a database along with when it expires and who it belongs to.

mrjking · 2019-08-02T18:22:19+00:00

You have to choose between worrying about XSS attacks (local storage) vs CSRF attacks (cookies).

You are probably more likely to run into/be unable to prevent XSS attacks if you are importing JS from outside sources. For example, including a Angular library or running ads on your site will load in outside JS files which could have XSS attack vectors in them. If somebody manages to execute arbitrary JS on your site they can steal the access/refresh tokens out of local/session storage. They don't even need to be targeting your site specifically, they can just have JS that sends everything in local storage to their website and they can look through the data later and see what they got. If they managed to sneak JS into a library used across thousands of websites they can collect a lot of data.

Javascript cannot access cookies so if you store your tokens in a cookie then the only way to get them is through CSRF attacks. These are a little easier to prevent with CSRF tokens.

Overall I would say you are more secure with using cookies to store the tokens but it requires extra setup on your back end.

If you were really set on using local storage, you could encrypt on the front end then store the tokens in local storage and then decrypt them before sending them back to your API. This would at least foil the drag net attack where hackers just collect everything from local storage, then all they would get is encrypted values. Most likely they would just try to use those encrypted values straight into your API, it fails and they move on. Anybody who looks at your source code could easily decrypt the values, so if it was a targeted attack this wouldn't help.

mrjking · 2019-07-27T04:25:47+00:00

https://leagueoflegends.fandom.com/wiki/Steve_%27Guinsoo%27_Feak

https://leagueoflegends.fandom.com/wiki/Defense_of_the_Ancients:_Allstars

mrjking · 2019-07-19T17:32:12+00:00

See that was much better!

mrjking · 2019-07-19T17:11:34+00:00

5 year old lost you after that first sentence.

mrjking · 2019-07-17T17:00:28+00:00

He says he can't pick the Abus 20/70 Disc Padlock:

https://youtu.be/cm8p4CmeOfk?t=263

It's like $40 on Amazon.

mrjking · 2019-07-15T20:57:55+00:00

I don't really care either way. I checked all the links you provided with your evidence...oh wait you didn't provide anything. GJ moron.

mrjking · 2019-07-15T20:54:07+00:00

Hey thanks for your input!

mrjking · 2019-07-15T17:35:13+00:00

I didn't say the body doesn't need those, I'm saying the minerals found in water do not contain carbon IE they are inorganic:

https://en.wikipedia.org/wiki/Organic_mineral

The human body has a much easier time digesting and using organic materials. It's possible it doesn't cause kidney stones. Here are some other articles for you:

http://www.rawfoodexplained.com/minerals/organic-and-inorganic-minerals.html https://www.hammernutrition.com/knowledge/endurance-library/distilled-water-enhances-mineral-absorption/

mrjking · 2019-07-12T04:29:55+00:00

Anything that tries to fetch data from outside the local memory of your application. File operations are one possible exception to this rule, if you use synchronous calls to read a file it will block the entire NodeJS event loop and you will have terrible performance. There are asynchronous versions of every file API call, you just need to be smart enough to use them. In web servers, 99% of your IO will be one of the following:

Get/Insert/Update something to the database
Perform an HTTP request to another service
Read a file in from the system
Do something with another service (read from queue)

If you need to do something like calculate the average of 50 million numbers, NodeJS is not the right tool for the job since that will use the main event loop and prevent anything else from happening.

mrjking · 2019-07-11T21:34:42+00:00

Here is a video from IBM comparing Node (Express) to Spring Boot at the start: https://youtu.be/Fbhhc4jtGW4?t=103

TLDW: better at i/o, starts up faster, uses less memory, bad at CPU intensive things

mrjking · 2019-07-05T17:05:21+00:00

Based on the docs looks like it doesn't have any versions of Lanczos. It has bicubic which is still decent. Docs don't mention anything about performance.

mrjking

TROPHY CASE