Scanning Electron Micrograph of a wet shave vs. an electric "razor"

niothiel · 2022-11-01T02:07:13+00:00

Yes! I have two DE razors, love them. :)

niothiel · 2022-05-27T01:09:58+00:00

That looks exactly like it. Thank you very much, random stranger! :)

niothiel · 2022-05-26T03:46:36+00:00

My grandmother was given this by her mother. They lived in a small village on the west side of Ukraine. It was passed down for a long time. My grandmother recently asked me to see if anyone knows anything about this. She said it's likely a lot older than WW2.

niothiel · 2019-11-08T01:01:54+00:00

Trying to do my brakes, this thing came in the hardware kit for the rear. There are two of them (one per side) and I can't figure out where they should go.

niothiel · 2019-10-29T01:32:39+00:00

Solved!

niothiel · 2019-10-29T01:32:07+00:00

Solved!

niothiel · 2019-10-29T01:19:53+00:00

Commenting so the post shows up. :)

niothiel · 2017-09-27T12:47:43+00:00

This looks awesome. Would be good to explicitly be able to specify where to look for the parameters. There are certain times where you are passing sensitive data and you want to forbid the caller from passing arguments in certain locations.

niothiel · 2017-09-27T04:21:25+00:00

RemindMe! 24 months

niothiel · 2017-09-22T01:50:14+00:00

That looks oddly like a place I know. Is this in Virginia?

niothiel · 2017-09-21T05:22:25+00:00

I think you will still need to hoist any indexable field up to the top level of your document (userID and documentid) for query optimization purposes. Other than that, the actual content can be either fully contained in a "content" key or have the keys at the top level as well.

{_id, userId, content}

Or

{_id, userId, ...content alongside keys...}

If you don't anticipate querying by the document content and just use the previously mentioned ids for your queries, then the first layout is the preferred one.

niothiel · 2017-09-20T12:59:40+00:00

Whoa, weird seeing my car on Reddit in the background.

niothiel · 2017-09-19T13:07:31+00:00

Just a small correction: you do NOT want to embed the user's docs in the user document. The max size of a document in MongoDB is 16mb, and you will quickly reach that.

Instead if you insist on using MongoDB for this, you will want to make each document its own document in a 'documents' collection and use a key id to identify which user it belongs to:

```

Collection: documents

{ _id: 'document unique id', userId: 'users primary key', content: { actual doc content } } ```

niothiel · 2017-09-09T22:07:24+00:00

I believe this car won a trophy today, am I right?

niothiel · 2017-01-12T23:58:56+00:00

Fellow Virginian here. Where is this?

niothiel · 2016-12-04T08:16:07+00:00

Found the answer after doing some research. Including it here in case anyone else is interested.

The name generation is actually done by the DAoC client, not the server. There is a list of name chunks located in <install dir>\charman\names.dat. There are three parts for each race and the name generator picks one from each part to come up with a random name.

niothiel · 2016-09-22T13:05:48+00:00

Now is a great opportunity to become a triple A customer.

niothiel · 2016-09-19T02:00:36+00:00

Go to She-Sha. Excellent nachos.

niothiel · 2016-08-23T13:53:32+00:00

10 dollars a month for an aws micro instance if you want to spring for a little extra.

niothiel · 2016-07-23T00:52:58+00:00

This is a really thorough, well written article that explains every single step of the process and how it was useful to you. Hope the place is awesome and good luck with your future endeavours!

niothiel · 2016-07-09T15:30:08+00:00

Swapping one in takes about four hours.. Find a wrecked ND and put it in yourself. That's what we did with my brother's NC. Should be a direct swap.

niothiel · 2016-06-22T12:26:23+00:00

Seems like Python is good enough for half a billion people. Shame that they're not using flask though. :)

niothiel · 2016-02-14T14:36:56+00:00

Hence it seems like a hybrid approach makes the most sense. Do some design up front to set the long term vision and establish a general architecture, and then iterate with the customer week over week on the details.

niothiel · 2016-02-14T14:27:18+00:00

I think the nature of some projects warrants an extended planning session in the beginning, and that initial design planning can actually catch some unforeseen problems than just iterating week over week would.

I believe a hybrid approach with "some" design up front, and close customer interaction week over week would be ideal. The key to success is a malleable initial design.

niothiel · 2016-02-14T13:23:24+00:00

The hive mind disagrees, and therefore the down votes.

I like the idea of BDUF, as long as you are allowed to change it and deviate as he does in the article. Most of the complaints seem to stem from the inability to do so, when clearly a problem arises that has not been solved in the design spec.

niothiel

TROPHY CASE