m4xm4n

I believe analogpixel is being facetious

brb writing a dystopian fiction where members of the criminal underworld pee in bottles and do... other things... to evade the state. and then there's a sherlock-type investigator who's chasing a character through the sewers, etc.

Tailscale

I like debuggers, but I don't always use debuggers. Typically because I can find the problem quicker w/ a puts/print/etc. than the time it takes me to run the debugger.

I also do a lot of web stuff, and if you're running some server process and you're not running the server process through a debugger directly, then you need to find and attach to the server PID, etc., then maybe deal with threads, and it's just a lot of upfront effort when I could just find the issue by throwing a puts/print somewhere or writing a test.

I'm not anti-debugger, I'm just busy and it's easier to put something in my code (which is how I frequently jump into debuggers too, e.g. binding.irb, binding.pry, debugger, byebug, etc.)

the CLI debuggers (gdb, lldb, etc.) are great when I really need them, but they're a pain in the ass to setup with things that are not C or C++, editor integrations sometimes need setup, and using them without setting breakpoints visually is tedious.

Think about what you want out of working on some side projects. If you think it's important for your career or because there's an itch you want to scratch, etc. you'll make time for it. If you think you're doing it just because you feel you _should_ be (because of something-something-#hustle-#grind), then I would think twice about spending your precious free time on writing code in your free time for the sake of writing code in your free time (or trying to monetize your free time!). You own your free time and you should fill it with the things you want to do as part of a balanced, enjoyable life.

I write a lot of code outside of work. I have some sort of compulsion to do so, and have numerous passion & open source projects I work on. They pretty much all scratch some sort of itch for me personally (either creative or mentally). This keeps me motivated because they're all stuff _I_ want to do and mostly not things I feel like someone else wants me to do or I'm making myself do. I don't worry about going months between touching some of them. Some weeks, I don't feel like touching any of them and will spend most or all of my free time on other stuff.

This makes me feel warm and fuzzy again for the old web. This is wonderful!

I remember using this! I liked it and used it for a while! But not having it in the bookmarks bar, I kept forgetting about my feeds :/ and then I stopped installing it. I'm sorry :( Glad to hear it's still going strong though. Maybe I'll give it another shot!

as other's pointed out, RSS is still here if you want to use it. It's just not ubiquitous as it once was.

IMO the big thing that killed RSS ubiquity was Google Chrome not having support for it natively. Before that, Firefox, Opera, Safari all had RSS as well-supported, central thing and I remember finding it super annoying that Chrome didn't have it when it launched. But I kept using Chrome for the same reasons everyone else started switching to Chrome. And the RSS extensions all sucked. And eventually I stopped using them. And here I am, no longer reading RSS.

But as Chrome ate up browser share, I'm sure fewer people went to RSS because it wasn't natively there and so the incentives to implement RSS decreased as fewer people expected it to be there, especially as many more people were coming online only having used Chrome.

Oddly enough, I switched back to Firefox years ago and _could_ get back into RSS at any point (or with any number of RSS reader apps, etc.), but the habit has stuck, and I now stay up-to-date on everything via email newsletters, Twitter and this orange website instead. it's worse and I hate it, but oh well

nice try Oracle!

In short, healthcare is very complex and there is no incentive structure that prevents the software from managing that complexity poorly, primarily because the users of the software are often not the ones making the purchasing decisions. Many are optimized for billing, and others are optimized for health systems who want lots of data points and jam the software with data collection forms.

There's lots of _better_ healthcare software out there. It's still complex, while remaining fairly user-friendly, but it tends to live inside healthcare startups and healthcare tech, and not deployed as broadly as the big EMRs like Epic, Cerner, eClinicalWorks, etc. These established players tend to be the only ones with the feature sets that big hospitals and health systems want/need.

Aside:

A lot of people in this thread are complaining about "regulations" making things difficult, but HIPAA, HITRUST, Meaningful Use/Promoting Interoperability, SCRIPT, etc. are not _why_ EMRs suck. They make it harder to start from scratch, but they do not prevent you from building easy-to-use software. The software sucks because there's generally no incentive to make it not suck and a whole lot of legacy suckage with a lot of momentum, money, and influence.

I've used Linux for a long time. Though primarily on servers these days, I've occasionally used it as my main desktop OS, and always end up going back to macOS because of three things:

1. battery life on laptops. Linux tends not to Power Management well on most laptops. Whether this is a hardware/ACPI thing, a device driver thing, or an overall ecosystem thing, I'm not sure. But it's noticeably worse than when running Windows or macOS.

2. as others have no doubt mentioned, trackpad. Apple's trackpad hardware and macOS's trackpad gesture support is so good, it's really hard to not have it. I can emulate some of it on my XPS 13 running Ubuntu w/ some additional agent thing that runs in the background, but it's only 85% there and not as smooth an experience.

3. desktop environment stability & consistency. this is _much_ less a problem than it was say 10 or 15 years ago as GNOME has gotten quite good and Flatpak/Snap/etc. are decent at containing various GUIs and their disparate dependencies, but there's still a lack of good integration with DEs across ecosystem tools generally. But also Electron has also sort of leveled the playing field a bit, so many desktop apps behave the same across platforms (for better or worse)

I would've said slow package/kernel updates, but there are enough solutions to this now, that it's not as much of a problem (Ubuntu HWE, Nix, Linuxbrew, or using ArchLinux)

I guess I don't quite understand the target audience? I put in my average checking amount and it quoted me at how I'm potentially missing out on $262 dollars/year, at which point, I think, yeah okay, but I have FDIC-insured deposits, so I don't feel too compelled to forgo that for the promise of maybe adding another $262 to my wealth. I'm just simply not keeping 10s of thousands of dollars in my checking account. To me, that's what a savings account and/or investment accounts are for.

So who are these people keeping so much money in their savings account that they want to invest it, but are not already being served by other offerings from traditional investment firms of high-yield savings accounts?

In this topic: people not getting the joke

That's fair! I was considering Ansible for the same reasons but felt that:

1) Ansible on a Mac host is lacking 2) I didn't enjoy setting up Ansible first-thing 3) I hated running around looking up Ansible module docs when I needed to change/fix something 4) I wasn't psyched about writing more YAML

FWIW, the cognitive load of adding another tool here should be fairly low. It mostly leverages tools you're probably already using, and the management of those is still up to you for the most part. The configuration piece is pretty minimal. Write it once and forget about it. There is a CLI surface, but for the most part you can get away with just running `mstrap`.

Yeah man, that sucks.

But your behavior towards the GitHub support person was childish, and I think you owe them an apology.

My current preferences are

Large or complex apps (such as those at work or things I intend to have a long lifetime):

- Backend: Rails

- Frontend: Ember

The combination of these two is really powerful. I can focus on my complex problem domain and not have to make too many choices about project structure, testing setup, and other decisions that lead to bike-shedding.

Smaller applications (such as side projects):

- Backend: Rails, Phoenix, or Amber

- Frontend: Ember, (P)react

Rails & Ember are still very productive for small apps, but I'm finding Amber (written in Crystal, similar ethos to Rails) to be a faster, smaller alternative when a side-project is resource limited (plus, it's an interesting new community). Preact and React are quite good for building small things quickly or dropping into existing projects, so I've enjoyed them in that context. Ember and Rails are phenomenal over a long period of time, because they tend to have a relatively smooth upgrade path (in many cases with Ember, there are automated tools.)

I'm a strong proponent of Postgres. It gets better with every version and is great for both development and production use, especially if you want to do zero-downtime deploys (Postgres has some cool tools for avoiding locking of whole tables during updates, e.g. concurrent indexing, etc.)

Oh, very cool! I like the data model for the changes. I've been thinking about adding an analysis pass using something similar to make it possible to implement more sophisticated strategies. The tricky bit will be retaining the stream-based approach.

Yeah, I need to work on making the displacements and replacements a bit more context-aware (& probably linguistically aware). There are cases where it can "replace" a character with the same character, for example.

I do like your idea about visually similar but distinct character replacement. That would be a really fun one to implement.

I've been in this exact situation before. Go for Option 2; it is the best option for your physical, mental, and financial health.

Likely due to the fact that as of yet, no one has found a particularly good way of monetizing torrents without alienating downloaders. Monetization is a necessity for industry adoption, so it's hard to tie the future of television to something like torrenting, unless there's a way for content creators & licensors to get paid.