Recent submissions

Comment · 4 years ago
what do you think about plumbers and carpenters not being considered engineers?
Comment · 4 years ago
The reason it is easier for programmers to transform into software engineers is the same reason we are having this conversation. For the most part, I think this is because software is so cheap and accessible. Anyone can become a software artisan with just a laptop and time. For traditional engineering, you need resources. Here's a quote from the second post: "When it comes to things like making circuit boards, it’s pretty common for things not to work the first time. You have to do it again, and you have to send it out to the factory and do it again. You know it costs you another however many £1000 and another two weeks on the schedule. -Mike (electrical)"

If building software was expensive like engineering in the physical world, we wouldn't have to have this argument. It's too bad that physical engineering is so expensive, because we'd probably have a lot more people trying it out.

Comment · 4 years ago
I thought I was over this argument because it always hits a dead end, but Hillel took a really entertaining approach with this series. Looking back, I'm almost always having this argument with other software people, but never traditional engineers. I hadn't thought much about how our stereotypes are wrong.

A great example from the second post in the series is how software people don't have experience with the unpredictability of traditional engineering projects: "Part of this misconception comes from us seeing the results of the engineering process, not the process itself. We don’t see the friction, the overruns, the delays that happen because someone built the wall one inch to the left, or when a critical supplier goes out of business. To assume that software is uniquely unpredictable is a special kind of arrogance."

This has me wondering why the software world is so unpredictable in the first place and why we aren't working on that? Or at least getting better at dealing with it. Also, why are we so inclined to think the physical world is so predictable? Probably because we spend so much time on our computers...

excited to finish the rest of this series

Comment · 5 years ago
Comment · 5 years ago
Have you shared the code or any more details for that custom search engine anywhere? I'd love to see how you did that. I'm considering doing the same thing soon
Comment · 5 years ago
my biggest problem with this idea is that many people are already hesitant to write/post online. limiting the number of posts they are allowed to make might make their post anxiety even worse.

i do like the sentiment behind it though

Comment · 5 years ago
I'd love a high latency app as well, but there is undeniable magic in instant communication. My best writing is often when I'm "hot" on a topic and can quickly go back and forth with others on the idea. Steam could quickly run out for that type of thing without instant communication.
Comment · 5 years ago
my experience is exactly like this, but wayyyyy slower
Comment · 5 years ago
Comment · 5 years ago
Thanks!

Turns out an easy google search answered my question as well... this post https://medium.com/distributed-computing-with-ray/ray-for-th... does say that ray uses the actor model, and ray is listed on The Actor Model wikipedia page as an Actor Model library.

Comment · 5 years ago
Pony actors look similar to the python ray package actor api.

If anyone from the Pony teams sees this, are actors in Pony conceptually similar to actors created with ray?

Comment · 5 years ago
Snapchat also has some sort of phenomena that makes it feel like a much lower barrier to entry than a text message.

Snapping a new person is much lower pressure than texting them.

Pictures also make it much easier for people to be involved, because you don't need to be so descriptive with your writing. That is part of the reason snap groups tend to be so much more active on snap than text groups.

Comment · 5 years ago
There really needs to be some sort of mix between chat and a collaborative note-taking app.

How can we transform chats into a reasonable, permanent reference materials?

Maybe it would be possible to build a slack-bot that could identify which part of these threads are the most important, and even move them to a more permanent storage.

Or, slack channels could add functionality to allow users to vote for which messages are most pertinent, or should be moved to longer-term storage or a featured position for everyone.

I think there is probably value in these rapid fire IM's, but I feel the Mike's (the author's) pain. I skip over threads everyday because reading them never feels worth it.

Comment · 5 years ago
Seems like there is just a general lack of emphasis on the improvements that have been made.

It makes sense that progress cycles from a big breakthroughs to years of seeing how far we can push it.

Even so, the world is significantly different than it was in ‘96. “Stagnation” doesn’t feel like the right word.

What about advances in quantum computing? Is that not a large enough paradigm shift for the author to acknowledge?

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton