893 karma · joined October 2, 2020
I do the same "no presets rule", with most being the result of random experimentation and fiddling of parameters. This does a good job at "creating never before heard, totally out there sounds", but I imagine it's trickier the more specific your end goal is.
The first economist says to the other “I’ll pay you $100 to eat that pile of shit.” The second economist takes the $100 and eats the pile of shit.
They continue walking until they come across a second pile of shit. The second economist turns to the first and says “I’ll pay you $100 to eat that pile of shit.” The first economist takes the $100 and eats a pile of shit.
Walking a little more, the first economist looks at the second and says, "You know, I gave you $100 to eat shit, then you gave me back the same $100 to eat shit. I can't help but feel like we both just ate shit for nothing."
"That's not true", responded the second economist. "We increased the GDP by $200!"
Even if we think about it in more quantitative terms, with red being defined as having a dominant wavelength approximately 625–740 nanometres, it's a bit of an arbitrary definition isn't it? If we observe a wavelength of 624, objectively we might say it's not red, but someone may still observe it as red considering how close it is to red. Or someone with protanopia won't see anything in those bounds as red either.
The other thing to consider is, we might perceive some actions as violence, while the other species may not view it at violence at all. We may simply be materials that can be reallocated for other purposes, just like how humans often view living things in our environment.
If they're nontechnical, they may not care about how it's done at all, but they will care about timelines. They may have agreements with others that depend on the product, or may have stakeholders they need to communicate with.
As developers we usually focus on our direct communication with the business owner, but I think it's helpful to imagine the second order communications that will result from how we communicate progress on our technical solutions.
For example, if we convey confidence to get a certain piece done by x date, the founder may in turn pass on that confidence to shareholders. But if we later backtrack after realizing that it will be a bigger lift than expected, the founder may have to walk back those expectations.
Information-gathering is a common early step in any attack against a system; knowing the language & libraries involved (especially their versions) allows you to search for any existing CVEs that apply.
> Are you advocating “security by obscurity”?
I don't think OP was implying that security by obscurity alone is sufficient, just that it's unwise to advertise information that's not relevant to end users, that could help would-be attackers.
> Western societies are structured on Enlightenment-era philosophy that fundamentally does not value Black people as people, and defines them as slaves. Even though documents like the Constitution have been amended to end slavery, it created a society that is rotten to the core, and the only way to fix it is to burn down civil society.
I found this particular one strange because it sounds like essentialism, which is both a hallmark of Western philosophy and a common target of critiques by critical theorists and poststructuralists.
In college I had a deep interest in critical theory, but I recall most of my time with it spent simply thinking: reflecting on the ideas and critiquing them myself. We didn't exactly debate the ideas, either - it was more akin to collaborative analysis of their strengths and weaknesses.
As you suggest, I think allowing this ebb and flow made the experience a more fruitful one.
Personally, interactions feel more significant in smaller communities, too.
https://www.forbes.com/sites/conormurray/2023/07/27/twitter-...
Coming from .NET 6 development, I'll do what I need to do when it comes to fleshing out unit tests, but the brevity of Python unit tests was real pleasant to work with.
FWIW, it could simply be chalked up to M1 weirdness. We have an ongoing list of various workarounds for the M1, whereas those using Intel MacBooks seem to be mostly fine.
Just like how a shell script is easier to manage than stringing lots of commands in the terminal, defining services in yaml is easier to manage than adding a million flags to your docker commands.
Of course at a certain point you may need further abstractions, but I agree with you that these should only be used if they're actually needed.
I could never get bind mounts working consistently, relying instead on volumes, which are more awkward/less explicit when persisting local DBs used when testing.
I've had zero problems with Rancher Desktop + dockerd - definitely recommend it for M1 users that are having issues with podman.
I guess I'm just thinking, until we see the how this all pans out over the next decade, we don't really know if the current rate of growth will hold, or if it'll plateau/slow down.