ducharmdev

I was about to recommend the same book - lots of good nuggets of wisdom in here, without the dogma you sometimes find in this kind of literature.

Re: your experience teaching synths in university, do you feel there is certain knowledge/concepts that are difficult for those self-teaching sound design?

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.

That sounds like my ideal job. The longer I've been a developer, the more I've come to dislike work that doesn't address problems faced by end-users/the org.

This is a coldly economic take. Does the sole motivation of writing have to be for the consumption of others?

Two economists are walking in a forest and they come across a pile of shit.

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!"

I was not expecting panpsychism to pop up on HN. Years ago I explored the topic out of curiosity; at first it seems pretty absurd, but you can find some interesting discussions and insights about it. At the very least, it can encourage you to think differently about consciousness, and perhaps even question some of your own assumptions about consciousness.

It's odd to me that you chose color as an example of something objective, since so much about perception is subjective.

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.

Sometimes I wonder how many criticisms of JavaScript frameworks are driven by a nostalgia for an internet that no longer exists. Not this post per se, but many seem to forget why the industry landed on React in the first place.

I would guess that you're either not around junior engineers, or people are very good at hiding their confusion.

Minor nitpick, but I wish this post started with defining what we mean by logging vs tracing, since some people use these interchangeably. The reader instead has to infer this from the criticisms of logging.

This or bran cereal are both good options in my experience. Just make sure to watch for how much sugar is in it; some brands will sneak in sugar even in granola.

You're setting up a binary between advanced/primitive; I would hesitate to speculate that they would conform to our ideas of these concepts.

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.

On a higher level, software development is a process of converting unknowns to knowns. We can't estimate or act upon what we don't know; as we uncover details, we can more accurately gauge level of effort and what the best solution is for the problem at hand.

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.

How is being “leaky” in any way bad or even good?

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.

Thank you for the context - I thought that sounded off.

I know this is just an example, but is this an accurate representation of what these arguments are like?

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.

I wonder if the speed/frequency of discourse has soured some of the potentially good ideas that critical theory can put forth.

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.

100% agreed. On reddit, I've always felt there was an inverse relationship between the quality of content and the number of users on a subreddit.

Personally, interactions feel more significant in smaller communities, too.

Happened just this week:

https://www.forbes.com/sites/conormurray/2023/07/27/twitter-...

When I used Python for Advent of Code a few years ago, I found that Python makes unit testing fun.

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.

I wish I remembered the exact error; it was just with podman though. Podman desktop being newer, I hadn't really tried it out much.

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.

I switched from podman to Rancher Desktop at work recently, and it's been a very smooth experience - thank you for your work!

To me, docker compose is simply a more readable way of running docker commands; anything you can do with the docker cli, you can run as a docker compose file.

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.

At work I was initially using podman on an M1 MacBook, but switched to Rancher Desktop + dockerd a couple months ago after having too many issues with podman. Many in my org are also moving away from podman for similar reasons.

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.

The beginnings of a western WeChat?

Such a fantastic film

Do you see any irony in the fact that you're voicing your disagreement... in writing?

Yeah, comments like what you describe should simply be removed on sight. I think they are most useful in describing domain-specific context around some logic, that may not be obvious by reading the code alone.

I guess what I was getting at, when you are logging lots of data in something like Azure app insights, Splunk, etc., you don't have the luxury of being able to just scan your logs with your eyeballs, because there's simply too much information. Instead you log objects, and are querying logs almost like you would SQL.

On a smaller time scale, is rate of growth that meaningful?

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.