I like this rule of thumb: Spend more effort producing the work than it takes for someone else to consume it.
HN user
glennericksen
CTO & cofounder of FaithStreet
@glennericksen https://www.faithstreet.com
You can switch to the mentioned "delayed" mode if you're using pnpm. A few days ago, pnpm 10.16 introduced a minimumReleaseAge setting that delays the installation of newly released dependencies by a configurable amount of time.
I don't usually think of Data when grouping values together in Ruby. Seems like I should. Lucian puts forth a good explainer of when and why they are helpful.
To summarize, Data became available a few years ago in Ruby 3.2. You can create value objects by subclassing the Data class with Data.define. Data objects are immutable, comparable and easily greppable. They are constrained in ways Struct, Hash and Class are not. The shorthand removes boilerplate and the constraints create the utility.
Measure = Data.define(:amount, :unit) weight = Measure.new(amount: 50, unit: 'kg')
"Business moves at the speed of trust."
This is a good post exemplifying this axiom. It is one thing for a leader to be trustworthy. It's a different challenge to cultivate trust within an organization in the midst of rapid change. Enjoyed reading this account of Anthropic's adventures scaling trust.
+1 to Typecraft for reworking your Neovim setup. As a longtime Vim user, I adopted Neovim with my Vim .vimrc in order to use Copilot. With Typecrafts guidance, I switched to Lua config, and really happy with where I ended up. Haven’t touched VSCode in months.
"Will not" allows the existence of a bridge but it's not on your route and you say you're not going to go over it. "Cannot" is the absence of a bridge or the ability to cross it.
Rapid ecosystem churn is my gripe with Javascript. I've generally found Rails and popular Ruby gems to be very durable over time.
There's was a story in Smithsonian magazine a few years ago (https://www.smithsonianmag.com/science-nature/meet-ecologist...) about an ecologist who more or less did what this article proposes, increasing the biodiversity in his backyard. He called his project a "Homegrown National Park".
Tallamy's Suggestions:
1. Shrink your lawn (replace grass with plants that create habitat)
2. Remove invasive plants (native plants support more animal biodiversity)
3. Create no-mow zones around trees (accommodates insect life cycle)
4. Equip outdoor lights with motion sensors (lights can disturb animal behavior)
A long post, but the final paragraphs sum up both the problem and the ask:
"This was the last attempt to keep core-js as a free open-source project with a proper quality and functionality level. It was the last attempt to convey that there are real people on the other side of open-source with families to feed and problems to solve.
If you or your company use core-js in one way or another and are interested in the quality of your supply chain, support the project."
“What’s so beautiful about creating products is that saying it in a poetic way, if you have that passion it naturally starts waves and those waves connect people. Then you don’t know where it’s going to end up, anything can happen, but if you don’t do anything, if you don’t write that text, if you don’t draw that picture or design that object, you can’t expect anything to happen. You need to start that chain reaction in life.” - Jesper Kouthoofd, founder of Teenage Engineering
I was curious enough to look at this story a bit more. Some related, interesting tidbits: In 2004, Niger estimated 50% of farmland was using the farmer managed natural regeneration framework (FMNR) described in the article, essentially reforestation through growing new trees from sprouts on old tree stumps [1]. An update in 2022 says over 200 million trees have been added via FMNR [2].
[1] https://en.wikipedia.org/wiki/Farmer-managed_natural_regener... [2] https://theworld.org/media/2022-04-29/niger-s-unexpected-suc...
Thanks for sharing this. The lecture format helps draw out some of the implications of the Alexander's work. For example, "a healthy mind in a healthy body–in a healthy environment", connecting the value of shaping the environment well to human benefit.
He also simplifies an explanation of why algorithmic design vs "all at once" may be preferable: an algorithm offers opportunities for discovery beyond intuition and memory. In other words, trust the process.
Bluetooth, a union of different communication protocols, after King Harold Bluetooth, 10th century uniter of Danish tribes.
I like to work through a process like this: what do I have to work with; whats important right now; what’s the next best step to go forward; do it. Again and again.
None of your immediate next steps will solve the problem; but maybe it will be step 6 or 8 or 20 that does. But if you are only ever repeating steps 1-3 you are going to run out of time. Change direction if it seems like you won’t be able to capitalize on the current strategy, not if another strategy might work better.
Norwegia aka Norway :)
"Because Indonesians come from Indonesia, and Russians come from Russia, Norwegians come from Norwegia." - Urban Dictionary
A "when to" should be added to this "how to". This might be cohesive in a smaller code-base, but it is not pleasant as "query objects" multiply. There are other ways of handling complex queries closer to the model without this type of abstraction. If you reach for this pattern, be sure it's worth the added cost in complexity.
Thanks for sharing this. I checked my router config and found the option to turn off LED lights except power. A more elegant solution than electrical tape I had been using before.
Reminded of this bit from Carl Rogers’ “A Way of Being”.
“People are just as wonderful as sunsets if you let them be. When I look at a sunset, I don't find myself saying, "Soften the orange a bit on the right hand corner." I don't try to control a sunset. I watch with awe as it unfolds.”
It looks like they are moving towards folders as an organizing principle instead of an album abstraction. More information here: https://www.dropbox.com/help/photos-videos/changes-photos
Ebook
Yup. That URL worked during the broadcast, but doesn't seem to be able to replay it. I haven't been able to find a replayable copy.
Live broadcast is now on youtube. Forget waiting for Stanford to email you a link. https://www.youtube.com/watch?v=QTGDG4Ge_xU
Someone once told me that what we need are three lists. A to-do list, a stop doing list, and a don't do list. I don't always end up with three lists, but the principle serves me well.
So much for "Move fast with stable infrastructure"
Arguably, you could the fix OP's issue by improving/changing the domain model. In this example, issue of state arises because the Order relies on the inherent possibility of changes to the attributes of a Product. Adding line items(quantity,price,product_id,etc) instead of direct product associations would provide a more stable representation that's easy to reason about without the additional complexity of REVAT.
Congrats to the Songza team. One of my favorite ways to listen to music by far.
Seems straight-forward to disable toggling when the card is out of range from your phone.
Numbers rivals Excel in many ways
The only use case Numbers performs well is as spreadsheet presentation software with the ability to edit. If you need to work with a lot of data or crunch a lot of numbers, it's not even close. Excel wins.
Just found a Balanced dev last week on API Xchange and he's working out great. Saved a lot of time filtering contract devs for requisite experience or familiarity. Nice.
New York, NY (full-time, RoR dev, designer)
FaithStreet (http://www.FaithStreet.com) is a social outreach and member engagement platform for religious communities. Over 11,000 communities have joined in the last 6 months. The problems we're solving are ancient and ready for innovation.
* Full-stack Ruby Engineer: You should possess equal parts talent and determination. You’re a “maker” and a generalist, stoked to execute product vision. Front-end, back-end, you take big problems and turn them into code.
* Designer/Front-end Dev: This isn't an opportunity to just make things pretty or make pretty things (although we'd like some of that too!). Help us think through ways communities can reach and engage members.
Visit http://www.faithstreet.com/jobs or contact jobs@faithstreet.com