iamwpj

I would except to get up and running doesn't require you to keep up with the feature releases or even and extensions really. You can install, create a file with the right extension and have syntax highlighting and formatting functionality out of the box. That's a pretty simple process!

News so apparent that no one has any care to embellish upon it.

Spot on. If all the deaf community needed was rapid signing attached to presentations this issue would have been solved. Reliable subtitles have been around for years on TV with a short delay. ASL presentation is so much more than waving hands.

I tend to agree. After working with data outputs from a variety of Linux sources for years I find the PS output is much more standardized -- or at least PS handles string outputs in a much more standardized way. I love the Select-String ... approach to field display. Making and outputting tables in PS is much slicker than the same magic on Linux. Ugly is a matter of opinion, but the real magic of PS is never having to drop characters or spaces to munge text into a column.

The commenter didn't say they were getting hit with OOMs. Is this something that is happening to you?

Anti-note advocate here!

Your notes should either be updates on tickets, documentation, or comments in code/git readme. You shouldn't be isolating information on separate platform and outside of the tools that you share with your team to manage a codebase/software stack/etc. You're doing a disservice to your team if you're withholding access to knowledge!

If you're not a natural notetaker don't worry about becoming one. Update tickets/tasks, docs, etc.

I use this method for nested VPN connections. At work I have one VPN for main stuff and then once on that I connect to another one for more secure access. The workflow is Windows centered so typical users will RDP to the secure edge and then go from there, but on a Mac and attempting to SSH to machines was kludgy running from a separate desktop. I run openvpn to connect and use tinyproxy to catch web traffic (I have a separate browser with the proxy address set in it). Love the solution, it even passes MFA.

Caffeine affects individuals only a little. Its true effects are seen on the societal and global scale. Modern history was born in the coffee and teahouses of the cities across the Middle East.

I would be fine, but would WE?

Yes! OP is being super condescending. And thus far, this amazing new paradigm in stealing recipes and posting them elsewhere on the internet isn't working as well as any of the "mommy blogs" OP complains about.

Similarly I consolidated my Makefile process into a CI. Having a workflow that is: 1. Set up venv of this version or greater 2. Install packs from requirements.txt

I think the repeatability and simplicity combo of this is my favorite approach. I'm all for standard tooling wherever possible.

Yes, Python comes with 100% overhead from Shell. I have packages inside either the system or virtual environment tools. Honestly I err toward sh/bash because I write it, ship it, and forget it!

IME people like it when they can submit something and move on with their life. I think a small data explorer for web can go a long way and a simple web portal that allows submission of zipped files. That might cover the first 90%, then you can deal with the last 10% that need additional help.

For your second question about data ingest, unless you're enforcing standards on receiving data (for example, check it as people try to submit and fire back if it's not right) I don't see a way to index except by set schema. Elasticsearch would allow you to index on dynamic fields, from there you could merge data.

A critique of the dieting advice, "just eat less" is that it doesn't apply to many people. On the surface a comment like that is presumptive. In 2016 when I realized I was more overweight than I ever thought I could be, I stopped eating out, stopped eating junk food, and stopped eating seconds. Eating less was the advice I needed.

Make sure that the advice you need isn't just: "buy less".

Aside from that, budgeting everything is a great place to start. There's apps that can help, but a spreadsheet could do it too. My advice is to not pay to start saving. The more granular you can be the better too. If you have some small debts then I recommend setting aside just enough for rent and food then working to pay those off immediately. There's no shortcut to building out a budget, so you'll have to itemize your spending and do the math to get your baselines -- then work from there.

I have a food obsession and the only things I've found to cope is just being hungry. I try and drink coffee, I think hot drinks help. I don't eat breakfast and just remind myself that the hunger I have is nothing -- it's a result of boredom and sedentary. I have enough nutrients in my diet that even one of my meals for a day would sustain me. It's not pretty, but that's the actual thing I do. What's that method called? Passive suffering? Reality check?

Also, if it costs money and is unhealthy, cut it. That's the number one priority.

I think my code would become clunkier. I rely on the creativity of the masses when I use SO. I know I could solve a problem through a complicated routine, but SO helps filter for the right builtin function or syntax that helps to improve my code quality. I can read the manual all day, but these are the things I don't get from it.

It's almost never a software issue. If you had another application besides Confluence would you be suddenly motivated to document? I doubt it. It's discipline and habits. The boring stuff. Tickets and projects should always include a component of documentation. Document about things, avoid how-to's except for specifics. Don't worry about screenshots, GUIs change all the time. Summarize uniqueness and put annotations on why something is set a certain way.

I'd write a book about documentation, but I just haven't had a chance to get it all down yet.

I recently rewrote my resume and this time I just did it in HTML from the start. Simple CSS template and some pandoc and I have a Markdown, PDF, and plaintext copy available to download from my git as well as an easily viewable HTML page. It scales for phones and screens.

This site looks official! Very good! I highly recommend your public documents function like this.

Hey man, I'm 15 and never missed a beat.

I requires multiple people to be successful at sustenance. There's a reason humans in history have large groups of families and many children bunched into a community (tribe!) to work together. The same is true today. Everything takes time or money. So if you require more than 24 hours a day and 7 days a week to upkeep and grow your food supply or craft goods -- you need more people working on it or you pay the difference.

Sarah Taber might offer some more context on this too: https://nymag.com/intelligencer/2019/06/america-loves-the-id...

I'm with you on this. Toxic internet is toxic even if you block the bad stuff. Don't go there.

I'll just add some things I think are missing:

* Here's GitHub's guide: https://docs.github.com/en/authentication/connecting-to-gith...

> Before I get killed here for using Excel files for credential storage please note that I have about thirty+ years of excellent experience going that way, have tons of managed credentials and think that millions of users have similar practices.

That's not true and even if it was, it's not a justification to do anything. You know it's wrong, but to be honest it's not my job to convince you that you should be using the right tool for the right job.

What steps did you take to research a good solution on your own? How do the responses here compare? Do you think that asking questions here will have an effect on how you see your current workflow?

I looked into this, but ended up going with PagerDuty's Rundeck. It's a similar idea, but with a less public and more internal focus. I see it as one step beyond an active monitoring service (because of the scheduling services). We use it to aggregate scripts that rely on several disparate data sources. It's easy to create one-liners or short dependencies that are highly re-usable to and then use those to gather the right data for more complex scripts.

This service runs as an interim before we can migrate to full containers and rely on their orchestration services. Sometimes I imagine SysOps as layers, this is a Layer 7, where as K8s is all of Layers 3-5.

Don't perpetuate that type of logic. It's toxic to your peers and not good for society. It's shorthand for a phrase like "It works for ME, so don't change it for OTHERS." Also, this concept requires anyone making a change to justify it to you so you understand it -- even though the changes are for a product and user base as a whole. Most other people read and accept the change and either make adjustments or even switch products all without requiring a bespoke explainer.

Also, your comment about designers and product managers is pretty dismissive and leads me to believe that you aren't very appreciative how hard it is to get UI/UX right. Just because it's area you don't understand or don't practice within doesn't mean it's not important.

I'm unimpressed with these commenters griping about the UI change or sponsored this and that. I don't think that's an honest standard you hold yourself to in any fashion and is simply not a functional way to live your life! What about your toothpaste packaging -- or gasp the product itself?! Things change all the time, you can be annoyed about it, of course! But accepting change is part of being a human in societies. "UI changes breaking my workflow" -- seriously? I don't buy it. I wish the conversations like this would fade because it encourages bad attitudes across the board -- I can't put my finger on it. Is it entitlement? Mozilla owes ME a good browser?

The Apple on that comes with a iMac or Mini. It's old and corded and feels just right.

Big fan of Cloudflare's posts: https://blog.cloudflare.com/tag/engineering/

Yes, it's like being mad that your salmon doesn't taste like tuna, even though you clearly chose it at the market.

I agree with this sentiment. I think a dream would be to get a condo in a desert town for a couple months to escape the winter.

Remote work has basically ensured I don't have to leave the town I'm in. I live in a small city in Iowa, specifically one with fantastic municipal internet service. It's got a Target and a handful of good restaurants and is a few hours from family. I don't plan on leaving now that I can work for a large variety of remote companies. You should try to live somewhere because you like it -- not for money or job reasons. Obviously that's not always possible.

There's little things that are built to last scattered all over my home and office. A chunk are inherited from previous generations others are unsuspecting items I bought that just keep chugging (I'm looking at you $9 toaster from Walmart). I have a few things that I've bought that I really hope they are built to last -- part of my motivation to purchase was this quality.

Of course building things to last isn't obsolete. Most things we buy are for a purpose. Typically that purpose results in them being "used up". Socks get holes, mechanisms wear -- all of that is normal and expected. Periodically through either some extra care or happenstance the item doesn't get used up in an expected period of time. It seems it was BUILT TO LAST, over time our kids and dependents will marvel at the way things used to be built. Some day in 40 years someone will look at your Aeropress and bemoan, is "built to last" obsolete?