“Beauty exists only in struggle”
“We want to glorify war”
“We want to demolish museums and libraries”
Tone aside, these documents are pretty different in what they’re advocating for. There’s a shared looking toward the future but I read futurism as a desire for violent overthrow of the past.
How about the alternative capitalist view that they don't have to spend as much time on QA in lockdown mode? Seems like one of those things that could cause all kinds of unintentrd consequences across apps.
It's the kind of thing the owner would probably keep for themselves when selling the car. It's fairly easy to uninstall - just unplug and remove a windshield sticker.
I have the original Comma 3 in my car (2019 Acura RDX), and it's pretty game-changing for long drives. The car already has adaptive cruise control and lane-keep-assist, but you need to keep your hands on the wheel. With the Comma, I can set it up on most of the roads I drive (local or highway) and it'll keep me going at the desired speed in the center of the lane (up to a certain max turning torque, which is a limitation on the Acura LKAS system - if you're in the Bay Area, it handles 101 just fine but will struggle on the 280).
I've logged about 3k miles of autonomous driving at this point and wouldn't hesitate to recommend it if your car supports it, with the understanding that it's a limited system and you still have to pay attention the entire time. Unfortunately, it seems like a lot of the newer cars have tighter security around CAN bus communication, so it may not be easy for Comma to continue to do their thing.
I find it hard to believe that so many people would prefer carbon emissions over free beer, massages, or being the pilot. If I condition this data on being male or female, the results change dramatically too.
The same incentive you'd have to do something for someone without receiving payment - a desire to help. I'd imagine the fact that people in that time had stronger familial ties to others in their village also helped increase payback rates.
One of the interesting things in this article is how OKRs are great for a "Pareto-distribution" culture, where performance can be measured across employees, but not a "linchpin" culture, where employees are exceptionally good at a small handful of things and not necessarily great at doing whatever the company needs. I've frequently seen those two types of cultures clash at the seams between technology and business.
As someone with an EE undergrad and masters degree, you really don't need it to hack on electronics, especially if you'll be starting with off-the-shelf parts or a microcontroller kit. Understanding the basics of voltage, current, and the ability to use a multimeter and soldering iron are probably all you need to make some interesting things.
The author lives in California - I didn't read the article as an "everything sucks and everyone is leaving" piece, it's that it's not great, here are some reasons why, it seems to be getting worse, and if we did something, it could be better.
It seems like the author's main argument is (1) the referendum system, (2) the board of supervisors, and (3) the one-party system are the problem. I understand you can address (2) by defeating them in elections, but structurally there doesn't seem to be any reasonable way to change any of these structural systems without large-scale overhaul to how the city itself is governed.
Getting open-source contributors paid is a real issue, though his particular case has a few unique wrinkles. Seems to me it's very rare for individual maintainers to be able to make a living solely from their open-source work. Given the permissive nature of the licenses at work, that seems to be by design, though I'm encouraged by the rise of open-core projects that seem to be trying to find a middle ground.
Thanks! We considered looking at Git history - churn is an metric that I've seen in other tools, but I don't have a great intuition for whether it's actually valuable. I just ran code-maat on the codebase I've been working on, and I'm not sure if it's that useful.
Our most touched files are our typedefs, package.json, backend routes, feature flags file, and the sidebar navigation component. These are large files that could be refactored, but I imagine I could've found those just by looking at lines of code. I'm curious if you have any stories of this being helpful?
This is great, thanks for sharing. I've been pretty reluctant to use davinci in production due to costs, but the other models seem significantly less capable. It seems like there's still a lot to learn about working with these models at scale.
Isn't the problem that kids (like all of us) are lazy and would rather use tools than their brain, rather than people trying to keep school "just like it was"?
Sure, because you don't know if the 900 people are silent because they're happy or lazy. A 10% complaint rate feels quite high for a typical feature and would tell me that I probably got something wrong.
This is crazy - I've been working on a similar app that ties a daily journal with tasks & calendar (https://daybird.app). There's another one I saw recently called reflect.app as well. Note taking has been around forever, I wonder what it is about this space that's triggering so many new products. Anyways, Acreom looks fantastic, good luck with the launch!
As a developer, we've had to tell users to switch to X11 to use certain features that are unsupported on Wayland (related to screensharing), so I'd disagree that these things are hidden from end users. Wayland is fine for the everyday use case but there's a lot of software out there that is built on tools like xev and xprop that have been part of the ecosystem for decades.
Guessing that this means there are a lot of confounding variables other than gut biome (environment, diet, genetics, etc) that are very difficult to isolate to prove causation, as opposed to correlation.
I interpret "Is it kind" as: "Will it have a desirable outcome" / "Will the listener receive this with the appropriate intention".
Telling someone who made a mistake: "You screwed up" may be true and necessary, but saying something such as "Let's try that again" will likely lead to a better conversation and learning opportunity.
We've been using Storybook for isolated development of state-heavy components and it's been a nice productivity booster, compared to testing inside the actual app.
As a bonus, the stories that get created live in your codebase and can be integrated into several different types of testing - jest test suites, visual regression testing, and puppeteer / Selenium.
There's certainly an overhead for mocking data properly, but I tend to see that as part of the general challenge of testing frontend / JS code.
We're using Elixir on the backend, which is great for real time communication. It's also a very stable backend platform in general. I agree, doing shared message passing on Node is quite challenging.