Just about anything is OK for a server, I use whatever hardware I get from work thats being decommissioned.

The biggest limit I see is the ram. Depending on what you spin up and how, it'll be the tightest budget per service.

Then tag with [CBH] as required.

Isn't that exactly what you're doing? Generating drama?

No proof or reasoning, while saying "Nah don't look at me I'm not involved" while doing a thing thats creating drama?

I have to assume this is related to the tesseract debacle, and I have to assume that this sort of drama generation - which is what this post is - will continue from startrek.website now.

I guess I'll go elsewhere for my trek themed lurking.

No, but maybe its an experience thing - have to be burned enough times by not having something to want to have something?

I think a lot of projects start off just someone goofing around with an idea so no hard requirements to start. I do that when I'm learning something new but they aren't ambitious or worth sharing.

I always start with defining requirements, and then I follow with a bunch of pseudo code. Its how I do things at work too. I like getting the ideas and structure out before I write any actual code or I get stupidly distracted.

Well I know what I'm looking for tonight

Start small

This is my strategy whenever I learn a new language. Start easy, escalate in complexity.

• print to the command line
• take input from the command line
• dumb blackjack game
• dumb blackjack game and store session results
• Make a fugly UI but keep the operations text
• Make a fugly UI and add basic graphics

Etc.

The basic game itself doesnt matter - make it hangman if you want. The idea is to get used to a language.

Keep doing that sort of thing, experimenting and learning, find ways to break things, find weird ways to solve problems, figure out ways to write even less lines of code. Find elements that you can make a function instead. Sanitize inputs excessively. Whatever.

Play around, and keep playing around. You'll learn in no time.

For the record, this is how I learn, by doing. I have a really hard time sticking to tutorials, and I find examples far more helpful than a manual entry explanation of what something does. YMMV.

Thats right! I forgot about that part.

Cops are nightmarish levels of stupidity.

If I remember right, one cop brought his rifle in which got sucked into the MRI machine.

Even the warrant was based on a cop lying iirc. The basis boiled down to something like "energy use and tinted windows", which, you know... Medical imaging and patient privacy.

Idiots and asswipes.

We have everything because there were different groups and changes along the way, and no one wanted to put in the effort or lose anything.

Now things are mostly in teams, but files are not on SharePoint but Box, making it even more ridiculous.

I loathe how messy my work laptop is with all these different variations of... Messaging.

Especially an aerospace company it would seem.