jsherer's comments

Good question. Indeed, I prioritized improving my vitamin levels for health reasons, including the possibility that it may reduce my headaches, rather than running a purely scientific experiment. If the migraines come back while I maintain normal vitamin levels, I'll continue my experimentation!

March: 0

April: 0

Back in August of 2021 I started tracking my headaches. I was experiencing 10+ debilitating migraines a month and had modified a number of variables in effort to reduce them (sleep, stress, water/caffeine intake, etc).

In September I got a blood panel from my GP and noticed low levels of essential vitamins. In October, I had 12 migraines. I started supplements for B12, Vitamin D, Vitamin K, etc. The migraines decreased each month: in November to 9, then 3, then 1. In February I had my first migraine free month in years.

Neurology is complicated. Migraines/headaches can be caused by a variety of factors. I chose to rule out things in my control (diet, exercise, stress, sleep, and finally vitamins) before taking daily use migraine medicine.

I'm working on the next version of JS8Call[1], a digital mode for amateur radio, that enhances the mode by using some of the latest RF research (LTE/5GNR/Turbo Codes/Polar Coding) for sending reliable messages over weak signals/links.

[1]: http://js8call.com/

You will not usually have nor do you need line of sight for HF radio. The radio waves are reflected by the ionosphere at various angles and heights, allowing the signal to be received at many different distances at once. Radio waves at the correct frequency hit the ionosphere like stones skipping along the surface of water.

Awesome. Hope to see you on the air sometime :)

Great to hear Ryan. See you on JS8 :)

Yea, Metcalfe's Law at work. Give 40m a try.

Glad you found me :) Here's the main site where you can learn more: http://js8call.com/

And a video walkthrough I did just a few months ago: https://www.youtube.com/watch?v=rz0Cpkaol-o

This is not my proposal, but I think this is one that I like most with regards to Go and metaprogramming/generics.

> Blocked a lane of traffic for 40 minutes

Curious on the 40 minutes here. Why'd it take so long to recover?

This looks like an interesting finding. Unfortunately, the trade-off for this type of efficient small data storage is real:

> Note that LSM-trie uses hash functions to organize its data and accordingly does not support range search.

Range search, while not directly applicable to all data sets, is an important feature of the LSM data stores compared (LevelDB & RocksDB).

The authors acknowledge this and say:

> There are techniques available to support the command by maintaining an index above these hash-based stores

So, don't plan on using an LSM-Trie for a direct replacement for your LevelDB or other LSM-Tree based projects that rely on Range searches without considering the additional complexity of building and maintaining an index to perform those Range searches.

Application Reliability Engineer | Zapier (YC S12) | Fully-Remote Team (Work Anywhere) | Full-time

We're looking for someone to join our fully-remote Engineering and DevOps team at Zapier to help scale and automate the billions of tasks.

Here are some things you'll get a taste of:

* Be an important member of our Engineering and DevOps team, working to scale our fast growing and unique system

* Write application code to support new features

* Build tooling to increase visibility into our running production systems, measure performance continuously, and act upon changes

* Automate disaster recovery efforts, including introducing random "chaos" into the system to test and improve overall resiliency to failures

* Tune the engine that supports hundreds of thousands of users every day

Sound like a good fit? Give this a look over and get in touch! We'd love to hear from you:

https://zapier.com/jobs/application-reliability-engineer-spr...

Would be good to start off your landing page with a headline and some copy explaining your product. I didn't quite get it at first.

You need something like...

    Lanes is a simple to-do list with a built in pomodoro tracker designed
    to help you stay focused during your day.

    -- Insert screenshot of Lanes in action --

    Here's how it works:

    1. Build your to-do list for each day

    2. When you're ready to work, start a pomodoro tracker.
       The top task for the day is what you should be working on.

    3. Once your pomodoro is up... stand up, stretch, and if you've completed
       your task, mark it as done.

    4. After your short pomodoro break, goto 2.

    -- Insert testimonials about how lanes helped your customers save X
       amount of time or get N things done or achieve 100% increase
       in tasks completed --

    What are you waiting for... you should sign up
    for Lanes and start getting things done!"

I had the same though and looked into it. It seems that CoreCLR isn't the limitation there. It supports a variety of platforms: https://github.com/dotnet/coreclr#build-status

Looks like the authors are focused on Windows for their initial prototype development.

> There are a few minor quirks, but generally it works well

> As ever, support for Broadcom wifi and Nvidia graphics is nonexistent.

This is exactly the big issue with adoption of any *nix system on laptop or desktop. No user wants to have to live with quirks. Users just want their system to work.

For what it's worth, I think your website headlines need a lot of work. In the first few seconds of visiting your site I should know exactly what quasardb is and why I should care (i.e., whether or not the solution/service/product/whatever relates to me and my problems). Your current headlines tell me nothing.

I have some suggestions for a better marketing message, so shoot me an email (address in profile) if you want to discuss further.

Given that the title of the project is called Shiny, I wish it had some screenshots of the look and feel of the web-based UI. Seems like that could be a selling point.

Odd: "This implmentation (sic) currently does not implement the counter feature."

I agree. I'm going to try to narrow down what might be causing the issue by comparing a 1.4.2 profile and a 1.5 profile. Hopefully it'll be clear what changed and I can write a reproducible test case for it. Either way, I'll probably be posting to the mailing list soon.

This is interesting. I'm experiencing the opposite results for my long-tail latencies. Maybe it's to do with the way I have structured my system (too much reliance on the GC?), but switching to the Go 1.5 release in my testing has shown my 99th percentile latency to triple and my maximum latency across 1M requests jump 10x.

While I certainly don't have billions of requests per day, the millions of requests I do process are important and these results show that I need to do a bit more profiling to figure out what's going on inside...