_virtu

Thanks for the clarification on suicide vs assisted suicide. Yes, I do agree that the discussion in the book is about assisted suicide. It's been about a year since I've read it, so those details evaded me.

I do understand where the author was going with the discussion regarding assisted suicide, but the timing of the argument and the amount of time spent on it at the point in the story is the root of my main objection with presenting it.

Throughout most of the book, there's very little regarding ethics at least with the amount of painstaking detail that it's presented in, in comparison to the assisted suicide discussion. The discussion felt bolted on as it was presented around the fever pitch of the story just before a global nuclear war is about to break loose, we get bludgeoned over the head by a priest that's fervently against assisted suicide. The placement of the argument and the timing is just awkward in my opinion.

Again, this book touches on a lot of interesting ideas ahead of its time but the execution feels weak and confused. I would have preferred that each part remain completely separate honestly.

And of course, all of this is based on my taste. I recognize that this is considered a seminal piece of science fiction. In general I find myself fairly forgiving when attempting to read something I normally wouldn't, but this took the cake for me in regards to the amount of pain per page I suffered while trying to make it through.

I absolutely understand where you're coming from. I don't need every thread tied up into a nice bow. However, it felt like a shotgun of ideas that caused the main plots to feel less meaningful.

I’ll go against the grain here and say that I was not a huge fan of this book.

I do understand that this is one of the first times the nuclear apocalypse was covered in sci-fi. My main gripe was the writing and how poorly strung together the story was.

Overall the book touched on a lot of great ideas, but the writing felt like it was the first time the author had written a book. A lot of a storylines were touched upon but never completed.

The thread that is drawn throughout the story just isn’t rewarding enough in my opinion. And don’t get me started on the terrible foray into the ethics of suicide that came out of nowhere.

I’m all for reading books that are challenging and fall outside of your traditional tastes but I struggled to make it all the way through this book. I celebrated when I was able to finally put it down.

In the future, we're not going to have common tv shows or movies. We'll have a constantly evolving stream of entertainment that's perfectly customized to the viewer's preferences in real time. This is just the first step.

I wish the headline read "Norway wants advertising banned across Europe". I wish society would revolt against the idea that advertising is something that should be allowed. It's an affront on attention and we now have alternative ways of discovering products and services that we want that weren't possible when advertising first started.

Check out arwes.dev for some really dope sci-fi components.

rewind.ai feels like a super power.

I think one other feature that's missing from the article is the ability to map multiple blocks of time to a task.

So something like rescuetime that exports data from your active programs to a calendar/event timeline visualization a la the spotify example from the article?

I'm building a time block calendar app for some of the reasons mentioned in this article. Retrospective is the first big feature I would like to add so users can see what they have been doing on specific days in order to understand what types of interruptions they face.

I’ve been building a kinopio.club clone in Phoenix LiveView and the problems the author faces align with my experience from working with uis that require explicitly setting element position for the document. Having to manage all of the imperative handler logic was a huge pain on the JS side. I had also given myself the limitation to not use React for more complex Phoenix Hooks. It’s all native document rendering with the only dependency being x-state.

Moving the mouse event handler logic out into a state machine was where I found myself going in comparison to this author’s approach. I was pretty tickled by how much more maintainable it had been than the first time I had implemented it. x-state was by no means a requirement but it had a handful of features I didn’t feel like building for the current project.

I can absolutely believe that this is worth the effort, especially considering the fact that the team works with maps so much. The mental model presented in the article would be far easier to grok when working in the codebase than having to deal with the somewhat tricky to remember Event api provided by browsers for these types of use cases.

Others are mentioning fighting the framework but this is still a pain without React. But of course adding in React on top of all of this would make it harder.

I think that hacker news has become too popular. It used to be a little niche on the internet that few people were aware of. Like indie hackers, the site has been infiltrated by business lizards and marketers along with more of the masses leading to a lower signal to noise ratio.

Worked at a startup for the last nine months as a founding engineer building everything in Elixir + Phoenix and LiveView. I was able to ship more features and fix more problems faster than I ever have. The startup is out of runway and it breaks my heart to think I might have to go back to the painful world of node.js.

Yes, yes I will. If that helps to expose the truth, sure. Whatever that truth may be.

I've finally made the full jump to neovim after using vim bindings in all of my other fully fledged IDES. I've recently been looking at Helix, but the lack of plugin support along with fluid git support is where I'm still stuck. I use lazygit for all of my git operations inside of neovim and it's hard for me to give that up. Anyone have good recommendations for workflows that worked for them regarding these two issues?

That's such a shame. Namecheap was so great. Time to move on. Until then, I would recommend sending a feedback ticket to let the corporate overlords know. I doubt it'll do anything.

Feedback form: https://support.namecheap.com/index.php?/Tickets/Submit/Rend...

With all bad news comes a silver lining. At least with the cancellation of Everyone & Their Mom, I won't have to hear Emma Chee ever again.

In the scheme of things, those aren't even nice notebooks. Check out anything with Tomoe River paper.

Amazing Marvin

Dracula Pro

I would personally choose fly. But that’s after years of wasting time yak shaving my spare time to use AWS/GCP/Azure.

Go check out the elixir slack. There’s a fly.io channel you can ask questions about pricing in. It’s a breath of fresh air compared to the alternatives. You can also hit me up if you have any questions. I would love to help.

I hope this puts remarkable in their place after gibbing their loyal early adopters with a subscription model. I am aware they’ve reverted it but at this point I have no sympathy for them.

Biggest desktop organization hacks

- Asymmetric desk

  - Shift your workspace to your non dominant hand side. This frees up space for reference material, and for writing on your dominant hand. When I previously worked on site, it was also a great place for having other engineers bring their laptop to sit next to me while we were working together.

- Under desk mount everything. This saves space and indirectly causes your compute hardware to collect less dust.

  - You can 3d print rails for a laptop so you can mount it under your desk

  - You can purchase under desk mounts for large desktops. I have two computers under my desk. One gaming pc and my work macbook.

  - You can also 3d print mounts for things like dacs, and amps to save even more space

- USB C hub + usb switch or kvm

  - As above I switch between my work and gaming pc with a switch

- You don't need multiple monitors, your switching technique is just wrong (if this doesn't mesh with you, that's okay, maybe I'm wrong :) )

  - Keyboard maestro + activate application + 1 / 3 splits of windows is all you need on a decently sized monitor: 27 - 32. Being able to hit hyper key + letter to bring up or hide an application makes viewing things trivial.

  - Bonus points if you map your 1/3 splits to keyboard maestro.

- Get a face light for calls. It makes a huge difference in image quality.

- Drill a hole in your desk in front of your keyboard

  - You can put any wires directly into the hole vs running them uncomfortably to the edge of the desk.

- You don't have to use your stand desk only for standing. You can also have settings for writing height so you're still sitting but you have a more comfortable setup for extended periods.

- Use a split ortho linear keyboard. Push your chair in as close to the desk as possible so you don't have any breaks between your elbows and the board.

- Once a week, on Friday, make time to clean your desk. Organize it for your future self, so Monday you feel good coming to execute on work.

- Make it obvious. Put things that are habit based in front of you. You'll be surprised how much easier flossing becomes by doing this.

  - Put your medication on your desk in front of you

  - Put flossing material in front of you

Alexa is trash.

Eh, not so much. See my other comment to the sibling thread in regards to this discussion.

There are two parts to this discussion that people are pointing out that I could have done a better job explaining.

First that I’m confounding the trolley problem of killing a baby with abortion. I’m well aware it’s a thought experiment that’s used in philosophy. I understand that killing a baby is different than abortion. My main point which wasn’t articulated at all in the first thread was more from an anti-natalist perspective. The society I live in primarily assigns more value to the fetus and or baby than they do the people that already are living.

A lot of the argument comes down to whether or not the child will have a chance to do great things and to experience life. Killing the baby means stopping them from having this opportunity. However I look at it from the perspective of potential suffering and current ability to feel and think. Killing the baby really doesn’t stop the baby from thinking because well, baby. And more importantly killing the baby stops a lifetime of suffering.

Second, my worldview doesn’t contain that mentality. Abortion isn’t about killing babies. To me it’s more about stopping potential life. Whether or not that life has potential that is actually good is the part that I disagree with most of society.

I think of it from more of an anti-natalist perspective. The child will have a far greater chance of suffering while the adults will have a chance for less suffering due to their expected lifespan. That’s why I thought about it in the frame of abortion. We’ll typically assign the notion of having a life positive value, but from my perspective that’s just a chance for more suffering.

The question regarding baby vs old people was really telling. It’s practically the argument for / against abortion. What’s strange to me is that someone would choose to kill five people who are capable of thought instead of an undeveloped human being. But I suppose that’s why we’re seeing the reversal of Roe v Wade being supported. Sigh, fuckin religion.

Having worked at a startup that was beholden to a very large client in the space. I too can agree that this is more like what actually happens. The tail wags the dog.

Yes

Ecto the database driver for Phoenix is probably the most amazing piece of software I've used. Elegant dx, performant and just enough of an abstraction on SQL.

[1]: https://github.com/elixir-ecto/ecto