These two are my favorite balance of fundamentals and getting to purposeful application as quickly as possible (the first link is definitely not enough, but combined with the second she should be comfortable with the syntax and able to get basic things working):
https://www.kaggle.com/learn/intro-to-programming
https://www.kaggle.com/learn/python

This one takes its time with fundamentals and includes some projects to put them in context of building something. It’s presented on Google Colab and Jupyter notebooks: https://allendowney.github.io/ThinkPython/

Working with GIS data means cleaning data. This one covers that and a lot of common analysis tools and techniques. But it assumes a bit of programming knowledge (Good to follow up after one of the options above: https://wesmckinney.com/book/

Good news from September:

Introducing the Ghostty “Quick Terminal” feature: a terminal that drops-down based on a global keybind (also sometimes known as a Doom or Quake-style terminal). This was one of Ghostty’s most requested features.

https://x.com/mitchellh/status/1840449807095394391

I think that Hashimoto is using this project to iron out details that are left unaddressed due to convenience for other projects and the very low impact of any single issue Hashimoto has addressed. But much like with Apple projects, Hashimoto intends for the the end product to have greater value than the sum of the parts. Unlike Apple, it will be perfomant cross platform.

I think the only way to evaluate a project like this is to ignore the feature comparison charts and use it to see if it really is better when those details are addressed. I have a feeling that many people will agree and most will shrug their shoulders and not give it a second look if they even gave it a first one.

I’ll be trying Ghostty out soon. I hope it’s great. But I’m not expecting to be blown away.

Lemmy still doesn’t let someone post an embedded link and picture. People don’t realize that you have to include the linkin the body of the post which is annoying and intuitive, specially because when creating a new post Lemmy will allow you to fill out both form fields for link and picture but only use one.

I’m not sure I understand the trade offs you’re choosing by deploying this way. The benefit of simplicity an speed of deployment seems clear from your write-up. But are those the most important considerations? Why or why not?

How are you liking bearblog.dev?

This is a teaser for the promised future posts. Don’t ghost us.

Yup

Everyone can save time and just read your synopsis. These are billionaires backed by huge investment funds fighting over service fees.

I get the sense that you might appreciate golang.

It seems there’s room for both

FYI the person with enough money to donate $300,000 to a programming language foundation is the founder of HashiCorp.

If each lemmy instance has only a partial dataset

You can stop saying if. It is nearly certain that any instance only has a partial dataset in the same way that a search engine only indexes a partial dataset of every web page.

If this is the case: what happens if a bad actor subscribes to all communities of all servers?

There are bots that were built to do exactly that. I wouldn’t call them bad actors unless the instance owner prohibited such actions.

Perhaps the following rewording of your last sentence would be easier for readers to follow along:

With a lack of precision, 1/3 might become 0.33333333. When evaluating the expression 1/3 + 1/3 + 1/3, using 0.33333333 as an approximate representation of 1/3 will return a result of 0.99999999, instead of the correct answer of 1.

That link didn’t work for me.

There seems to be mixed reactions to this suggestion. I don’t know enough to understand why.

Or The Odin Project if you don’t want to cover Python in the curriculum and just stick to JavaScript.

https://www.theodinproject.com/

(The Odin Project also has an option for Ruby along with JavaScript)

A git commit is a snapshot. The node-based tree structure is an artifact of recording pointers to other snapshots and labeling snapshots with a branch name.

Try Odin

http://odin-lang.org/

Nice article.

why bother? Why I self host

Most of this article is not purely about that question, but I dislike clickbait, so I’ll actually answer the question from the title: Two reasons.

First of all, I like to be independent - or at least, as much as I can. Same reason we have backup power, why I know how to bake bread, preserve food, and generally LARP as a grandmother desperate to feed her 12 grandchildren until they are no longer capable of self propelled movement. It makes me reasonably independent of whatever evil scheme your local $MEGA_CORP is up to these days (hint: it’s probably a subscription).

It’s basically the Linux and Firefox argument - competition is good, and freedom is too.

If that’s too abstract for you, and what this article is really about, is the fact that it teaches you a lot and that is a truth I hold to be self-evident: Learning things is good & useful.

Turns out, forcing yourself to either do something you don’t do every day, or to get better at something you do occasionally, or to simply learn something that sounds fun makes you better at it. Wild concept, I know.

Contents

Introduction
My Services
Why I self host
Reasoning about complex systems
Things that broke in the last 6 months
Things I learned (or recalled) in the last 6 months

• You can self host VS Code
• UPS batteries die silently and quicker than you think
• Redundant DNS is good DNS
• Raspberry PIs run ARN, Proxmox does not
• zfs + Proxmox eat memmory and will OOM kill your VMS
• The mystery of random crashes (Is it hardware? It’s always hardware.)
• SNMP(v3) is still cool
• Don’t trust your VPS vendor
• Gotta go fast
• CIFS is still not fast
• Blob storage, blob fish, and file systems: It’s all “meh”
• CrowdSec

Conclusion