The struggle itself is a learning. It forces the brain to build the connections. The process is the learning.

One tip to use AI correctly is:

Use AI like a coach or a reference book, not always like a substitute for thinking. Leave room for your brain to struggle, because that struggle is where durable understanding is often formed.

So the method is to keep some hard thinking even with the strain:

• take handwritten notes
• attempt coding or writing from scratch
• spend time with difficult material before engaging for help

Playing as artistry, catalyst, fun, playgrounds, spontaneity, tinkering, anti-work

The researcher went on to summarize playful programming as "experiences that allow programmers to spontaneously and creatively express their ideas to code, to provide safe playgrounds for experimentation, and to support tinkering as a purposeless, ludic activity."

The Midnight is a virtual pub that lets you write posts and create pages.

Use proper contrast to make fonts readable

Some projects has more value to be written in Rust:

• Rust's safety allow to use complex patterns more safely
• Concurrent or multi-threaded systems
• Security-critical components

There are three approaches for ar Rust migration:

• Full Rewrite
  • the codebase is relatively small and the scope is tractable
  • there is an exhaustive blackbpx test suite that validates behavior
  • the API surface is well defined and stable
  • the deployment environment is controlled
• Incremental migration for each module
  • all other use cases
• Incremental migration with vertical features: each feature is built from the ground up to use 100% Rust code. Business value can be measured directly.

The incremental migration has its own challenge: FFI with C and C++. The rule of thumb is to keep the code responsible for the memory allocation do the deallocation.

most blogs that persist or accumulate value have a few things in common:

• they have a perspective, not just a topic
• they build
• they're written for someone specific
• they exist at a consistent address
• their authors accept that most posts won’t go viral, and that’s fine.

A classless stylesheet.

There are also many other themes out there!

• HTML only
• awsm.css
• bahunya
• bamboo
• bootstrap
• evenbettermotherfucking
• holiday.css
• kacit
• marx
• meyer
• minicss
• mvp.css
• no-class
• pico.css
• sakura
• sakura-vader
• simple.css
• stylize.css
• tacit
• thebestmotherfucking
• tufte
• vanillacss
• w3c-chocolate
• w3c-traditional
• water.css-dark
• water.css-light
• writ
• yorha

1. Rust doesn't prevent TOCTOU (Time-of-Check to Time-of-Use) race conditions (file path resolution → use file handlers directly)
2. Panics are denial-of-service vulnerabilities when handling untrusted input.
3. In case of a well established tool, compatibility is a security feature.
4. Resolve external information before crossing trust boundaries.
5. The interactions with the operating system is a security boundary in Rust. The developer has to be careful.

The post goes in-depth for many cases.

For later when it will be needed.

A way to start a website and connect it to the Fediverse and the ATmosphere

Micro.blog supports Mastodon, Bluesky, Threads, Tumblr, Nostr, LinkedIn, Medium, Pixelfed, and Flickr.

Another service similar to bear.blog

A list of /uses pages detailing developer setups, gear, software and configs.