tedyoung

It's all those unnecessary ports I can't stand. I don't need the HDMI, SD card, network, etc. plugs. Just gimme more USB-C Gen2 and maybe some Thunderbolt. I'm fine paying the equivalent of a Caldigit TS4, I just don't need most of those ports.

I love the Accusonus sound tools. This page doesn't have any details as to why they were acquired. Other pages (https://therecursive.com/greece-on-the-meta-map-facebook-own...) mention the Metaverse.

I'm happy for the folks behind Accusonus, but sad that I'll likely see my valuable tools disappear into the Meta-verse.

Often keys are stored in some sort of secure Key Vault. This is part of the infrastructure, e.g., Azure Key Vault. Or something like https://www.vaultproject.io/docs/secrets

Asking questions that elicit thinking, and not just rote answers, are what we want in learning. Not just "what's the answer to [question]", but "how did you get that?" This also works well for uncovering wrong assumptions or incorrect problem-solving methods. Getting students (or anyone) to learn how to learn on their own is, sadly, not taught in school here (California).

I gave a talk a few years ago on how people learn: https://ted.dev/learntalks

I generally do "outside-in" development, but only after I understand what I want the software to do as visible (observable) by a user (or other system). I'll sketch the UI, find the UX flow for the "things to be done", etc. This defines the "outside".

Once I have that, I get detailed enough on the UI, either by writing some code, or understanding what information it needs to get from and send to the underlying parts. As soon as possible, I write an automated test that defines the behavior I want (which fails), then "move inward" to the next boundary, such as the Use Case/Service layer (I use Hexagonal Architecture), write a (failing) test at that layer, and then start implementing some behavior.

I'll refactor, which often leads to the creation of a new class with a bit of behavior (this is the "inside"). I'll TDD that new behavior until it's all Green. Then I'll go back out to the Use Case boundary and write more tests/code, TDDing at that level, with continuous refactoring to extract new classes.

Once I'm done at that boundary, I'll return to the Outside/UI test and if it passes, I'm done (and maybe I have some UI cleanup to do). If it fails, that tells me I need another spiral down the boundaries (toward the inside) and then back out.

At each boundary, I may pause and do some CRC Card (class-responsibility-collaborator) design work, if I feel I don't have a good sense of what I'll need ("do I need a Group class here, or will the existing Roles for a User be enough?").

I used Publii for my blog, but it was very constraining in terms of its styling (the templates were mediocre). And I had made changes to its defaults for styling (which ended up not being responsive), so that when upgrades came around, it messed things up enough that I just stayed on prior versions. Now I'm stuck.

The whole template problem, along with customization (or is it configuration?) is the biggest blocker for me. I'm going back to a straightforward Markdown-like to HTML generator for my next blog revision.

I run a Discord server that focuses on the tech side (Java, TDD, Hexagonal Architecture). It supplements the things I do on my Twitch live coding stream (https://JitterTed.Stream). We have weekly book study groups, an "office hour", etc.

(You can DM me on Discord for an invite if interested: JitterTed#4770)

Apparently journalists don’t check Grantham’s past predictions…e.g., https://www.marketwatch.com/story/stock-market-legend-who-ca...

Even given the recent turmoil, being bearish like he was in June 2020 would have cost you lots of money.

It’s easy to “call” the bubble if you keep saying it every six months

I believe the intent is to not be a perfectionist (like me) and, instead, publish things that might below one's level of perfection. It's likely that's more than good enough, and is ultimately better than not publishing them at all.

I don't think he's saying anything about self-promotion? I believe many folks have the opposite problem: not promoting themselves, often because they think their stuff isn't very good.

> don't see the state (especially bloated California) doing better [than Kaiser Permanente]

In what sense? What do you like about KP: the doctors, nurses, etc.? The billing department? Single-payer would not take the staff away. It would get rid of large swathes of the billing department that are pure waste.

Not everyone has had your positive experience with KP. We switched away due to lack of availability of certain specialists.

Fails to mention the trouble Lambda School got into with their deceptive practices, according to the State of California: https://dfpi.ca.gov/2021/04/26/lambda-school-reaches-settlem...

Depends on what the course is and the content. Is it just a video? Then, no. Is it self-paced? No, he's not going to progress on his own.

Depends on the company (size, structure, etc.) whether any of those are negotiable, but certainly worth considering. Also, learning stipends for books, courses, conferences, etc. are useful.

All names are unintuitive. The point of Design Patterns is to have a catalog of solutions with names (aka jargon) so we can have higher-level discussions. This requires those involved in the discussion to have a clear understanding of the pattern, which isn't always the case.

Same, though every year I'm able to part with some of the truly dead pieces of equipment at the recycling center. Those old hard drives pile up, though. But now I've got half a dozen broken laptops—which have awesome screens that I wish I could use.

You haven't said what you currently know, but here's some ideas:

Security - even just understanding the various protocols and limitations of things like JWT would be useful.

Automated Testing - I'm a Test-Driven Development advocate, but I also know that's rarely easy to incorporate into existing codebases. However, the ability to write good, small, focused, developer tests is a very useful skill. And not just because of the tests, but often because it helps you implement functionality in smaller steps.

HTTP API Design - Especially since it involves designing protocols without you realizing you're designing a protocol.

The Bail Project - https://bailproject.org/

Anti-Terror Police Project - https://antipoliceterrorproject.org/

Lots of journalism: Hechinger Report, Grist, ProPublica, NPR, etc. They're not perfect, but they're necessary.

(I also pay for subscriptions to individual journalists such as Matt Stoller, Emily Atkin, etc., but those aren't tax-deductible.)

Agree that Heroku, while possibly more expensive, is the most straightforward to get going and maintain over time. You're paying them to figure out all the VM/container/database/etc. stuff, and that's what you want. I've had several apps running pretty much untouched for years on Heroku (other than updating libraries and the Java runtime).

Depending on the language, there may be other services that work just as well, but AWS/Google Cloud/Azure are either more expensive or will require more time to setup and maintain.

That's what the "a" in "..as A 'Legal Name'" means, right? That there's not one, all-encompassing, in all legal situations, name.

Still 100% true and applicable.

Y'all did read the important bit in the Abstract, right?

> if research results are selectively chosen, a review has the potential to create a convincing argument for a faulty hypothesis. Improper correlation or extrapolation of data can result in dangerously flawed conclusions.

Haven't finished reading it yet, but it's been enlightening and thought-provoking: "The Essence of Software" by Daniel Jackson.

Avoid getting distracted by every new thing you read about, from frameworks to architectures. Focus first on the fundamentals of software development, which often aren't taught:

1. Break things down into small "complete" steps. Nope, smaller than that. Nope, you can still break that down. Test-Driven Development can help here, not by making sure you've got good test coverage, but by encouraging you to break down the solution into small, testable pieces.

2. When learning something new, don't copy-and-paste. Retype it if you have to, but at least understand _why_ that code will work, and maybe a bit about _how_ it will work. As you get more experienced, you can copy-and-paste, though you'll find you'll do that less anyway.

3. Related to 2 and the post about technical communication: learn how to concisely ask questions. The number of juniors (and seniors) asking questions, but failing to show the precise problem (or at least what they think the problem is), with enough code (but not everything!) to evaluate is...frustrating for those of us who want to help. Tell us what you tried, tell us what the errors are (precisely, i.e., here you want to copy-and-paste!), but do so with as few words as possible. This is _definitely_ a skill, so you'll get better as you do it more, so pay attention to the questions you get in response to your question. Reflect on whether that could've been included in your original question.

I really like the idea of games for a niche audience. Does your game lend itself to being a "print & play" game? I launched a Print & Play version of my (very) niche game[0] because I didn't (yet) want to deal with the physical manufacturing and it's been a pretty good experience. Have you written about your journey on creating or manufacturing the game?

In early 2022, I'm going to manufacture a small number of the game using The Game Crafter (it's more than just cards), but the whole idea of manufacturing 500 copies and the logistics of shipping are daunting.

[0] https://jitterted.podia.com/print-and-play-version-of-jitter...

American Express never forgets. 20+ years after declaring bankruptcy and I'm still not able to get an AmEx card, because they have their own records. (I have an 820+ FICO score.)

Since you're the merchant of record (as it's your Stripe account that's getting the money), how are you handling tax collection for those jurisdictions that require it?

Another +1 from me for mkdocs and mkdocs-material (and I'm also a supporter of squidfunk). I use it for lab exercises[1] as part of my online courses (deployed onto Netlify). It just works and looks good.

[1] https://moretestable.com

A programmable search engine for code that is limited to your trusted or preferred sites would be very useful. Minimal requirement is that it understands code and doesn't strip out operators, parens, etc.

Would help if it was smart enough to show only latest information for your search. For example, no more XML configuration results for your question about modern Spring Boot applications.

Like any business that I'd start, I'd find a niche where general-purpose search is not very helpful. For example, code search, or drug information. Fine-tune the querying, synonym detection, stop-words, stemming, etc., for that particular niche.

Are you referring to Cloudflare's R2 storage? If so, I'm not sure that's completely comparable as Backblaze has a huge focus on backup systems, not just cloud storage.

[Edit: didn't realize Backblaze has cloud storage, I still think of them as the cloud backup company.]