What course/book/resource will help me understand nixos on a deep level?
depends on how wealth you are, and who you follow.
I was actually trying to make their post show up on "introductions", but I guess I failed?
I only skimmed it, but it does look useful. It fills a need for people who learn to code because they want to build scale-able things, rather than 'to get a job', or 'because it's interesting', or whatever.
Difficult to find resources like this in the sea of garbage for people who aspire to work at mag7.
Thanks for sharing.
we should fork nostr
protocol should never define application logic in the level that nostr does
"kind" should be replaced with "namespace"
none of the namespaces should be defined in protocol (nostr)
tags and content should be replaced with "data"
although we could probably also make signature and pubkey optional, maybe place them in data if necessary.
but do we really need json?
i think we should remove the json part and replace it with unformatted ascii or binary.
sounds great!
concept of relay and websocket is ok, but i think http would also suffice.
maybe replace websocket with http.
then we can just
curl https://my.relay to get some events
#introductions
Why are some users un-follow-able? Like this one for me.
The Twelve-Factor App Book, for building apps that focuses on automation, portability, cloud deployment, continuous deployment, and scalability.
https://github.com/twelve-factor/twelve-factor
#dev #devops
This seems like a nice reference resource.
nostr:nprofile1qyxhwumn8ghj7e3h0ghxjme0qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qpql2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqta478g Wondering why you've decided on closed source so for for #olas?
It seems like the fediverse has more of the 'dev' culture than nostr. how do we change that?
I've figured out (My total questions to LLM's are <10.) that "prompt engineer" means someone who's not a completely cluely narcissist. OR, someone who's managed to suspend their cluelessness and narcissism for as long as it takes to convince a decision maker of their worth...or get claim results from their LLM endeavors.
#devstr
Is this actually how you buy? I think about features so little. I try to figure out if it's purpose specific, then it's all about performance, efficiency, cost, and resell-ability.
I wonder what the optimal breakdown for learning new concepts is:
Practice 75% of the time
Read 15% of the time
Socialize about topics and adjacent topics 10% of the time?
And that doesn't take into account resting and not thinking about it at all. How much of that should one do, and when?
Have also been thinking about if it makes sense to just go for it for as long as you have energy to, or maintain a daily routine and start/stop at a given time (or approximate given time) everyday.
I suspect erroring toward 'Going for it' is on average better for learning, but worse for health.
Thoughts?
#devstr
"Django security releases issued: 5.1.7, 5.0.13 and 4.2.20"
https://www.djangoproject.com/weblog/2025/mar/06/security-releases/
#security #django #python
but what does it mean....
it seems like development on nostr is for more experienced devs...which there's a shortage of...at least rn.