wspeirs

Plus the CBD one appeared when I had the "Kid Friendly" filter selected :-|

Love the site and the idea, but struggling to understand the criteria needed for a +EV bet. Would one site need to have a positive moneyline bet on team A, then another site have a positive moneyline bet on team B... assuming team A & B are playing each other?

I had a different idea, but the goal was basically the same: https://www.researchgate.net/publication/4133971_Making_the_...

Basic idea is to have a system call that allows library writers to get the bounds of a pointer. This way they can ensure they're not writing too much data to a location.

Another idea I've implemented in userspace is to create an allocator that allocates a page (via mmap) then set protections on the page before and after. The pointer returned aligns the end at the next page. If a write goes beyond the end of the pointer, it bumps into the protected page, and causes a fault. Then you can handle this fault, and detect an overflow.

A even more strict version of this is to add protection to the page the allocated pointer is assigned to. On _every_ write you get a fault, and can check that it's not out-of-bounds.

All of these methods are slow-as-hell, but detect any memory issues. While slow, they are faster than valgrind (not badmouthing it, it's an amazing tool!). So the recommendation is to use it in testing and CI/CD pipelines to detect issues, then switch to a real allocator for production.

Highly depends what you're trying to do

"Talk benefits, not features" doesn't work!

I don't think this is true... It's more nuanced than this. Developers are much more skeptical of a "benefits" pitch, and care more about a "features" (and limitations as mentioned above) pitch. However, if you're just pitching a developer, you're probably only pitching the user, not the buyer. The buyer VERY much cares about the benefits, otherwise they're not buying. The buyer won't using a single feature, so that type of marketing is lost on them.

This is the challenge: the right message (features or benefits) to the right person (user or buyer) AND at the right time!

For example, you cannot easily perform the equivalent of the following command: cat /log/file | grep some-string | my-custom-script-for-analysis

You can with log-store[1], as it allows you to run custom Python commands to do _exactly_ this!

[1] https://log-store.com

Centralizing logs can be a HUGE help... You just have to use a tool that doesn't cost what Splunk charges. At the risk of over-selling, log-store.com caps charges at $4k/month! That's still a lot of money, but way less than what Splunk and other SaaS providers charge!

Fair enough... if you're monitoring "response_time", and a developer changes that field to "time_taken_to_send_the_bits" you'll probably have a tough time monitoring the service. However, if the dev communicates that the value has changed, with the right tool it isn't hard to have something that covers both fields.

At the small volume of data where you could "just put stuff in S3 and search it later"

I was arguing exactly the opposite... leverage S3's near-infinite storage so you can store whatever you'd like. Searching through it _can_ be fast with the right tool.

If instead of detecting the smoke (e2e) you try to monitor all the data like pressure in gas pipes, all the pipes fittings, how many lighters are in the building and where, etc, you will wake up every night 10 times for nothing

Without this you'll always be awoken by smoke, and at that point it's too late... there's already a fire. However, if you can monitor other things (gas pipes, lighters, etc), you might be able to remediate a problem before it starts smoking or burning.

There's no one-size-fits-all. Start with some obvious failure (e2e tests/checks; aka smoke), and when you root-cause, add in additional checks to hopefully catch things before the smoke. However, this also requires you update (or remove) these additional checks as your software and infra change... that's what most people forget, and then alert fatigue sets in, and everything becomes a non-alert.

You just need a tool that's adaptable and will let you parse-as-you-search. Without a schema, your logs can change whenever, and you can still easily derive value from them.

Cost, which still isn't solved yet.

I'd argue it _is_ solved... store your logs in S3. At ~$0.02/GB you can store a _lot_ of logs for like $20. The problem is that _most_ solutions (Honeycomb included) are SaaS-based solutions, and so they have to charge a margin on top of whatever provider is charging them.

You just need a tool (like log-store.com) that can search through logs when they're stored in S3!

Instead of “ingest all the metrics/logs” we have guides showing, for example, how to set up the most minimal possible Prometheus / Alertmanager, with the smallest footprint of CPU/memory/disk requirements. [2]

I'll bite... why _not_ "ingest all the metrics/logs"? I see 2 possible reasons: 1) don't have enough resources (CPU/memory/disk) to consume "all the logs"; 2) you won't be able to find what you need.

I think both are a failure of the tools in the space.

Agreed! Few things anger me more than when a program simply reports, "File not found"... OK, which file? Where were you looking for said file?

I know how we get here, people simply report the error from the OS w/out adding context. This is why I love anyhow reporting in Rust, you can attach context (like the file name and path) to the error.

In log-store.com I report the default name of the config file (you can specify it via cmdline if you want), and the 3 locations and order searched, if the config file isn't found. I also have it report the file being used, so if you expected the file in /etc, but you accidentally had one in your home directory, you'll know on startup.

These things seem like table-stakes in 2023.

Agreed... I wanted to understand what it was all about, but really struggled to follow. They talk about the whole thing taking around 24 hours, but some part took over 30. Also that it ran on a 4GB of RAM machine, but they needed larger ones to do all the parsing.

Also in the end, unsure of what the actual results are. Maybe I missed clicking on something.

Same... very intermittent

I wouldn't give or do a take-home test, I respect people's time too much. Again, I would sit with them and have a conversation about your code, and their suggestions. Hiring someone is more than what code they produce... Can you work with this person? Are they receptive to feedback? How do they handle conflict/being challenged?

the company is in a difficult position and everyone is doing layoffs

Is Google really in a bad position? Microsoft? Others who are doing layoffs? Or can they do them, bring down expenses, and juice the stock price under the cover of "everyone is doing it"? I don't know, but it is a bit head-scratching (to me at least) that profitable companies would be doing double-digit percentage layoffs

We are hoping to add someone to the team that can improve the quality of the work we do

I think that's your answer... Show them your existing front-end code, and ask them how they'd make it better. If they're experienced, then they should have some very concrete ideas. Then ask them "why" for their ideas. If they can't fully explain the "why" behind the "what" they're probably just regurgitating things they've read, but don't actually understand the tech.

destroys morale and fills employees with fear for their own jobs

I'm not sure layoffs prevent this

Is there an example of this service somewhere?

I would think you'd need to identify your target customer. Build a profile of them. What do they like to read? How do they find new products? Is there a magazine (old skool) or trade show or are they government customers or universities. Then copy how others are marketing to them.

Which company? What software?

I'm the father of 2 children.

It's interesting though that both radio and TV switched to pay models: cable/premium channels and Sirius/XM for radio. Billboards are providing anything to the user, they're just giant signs that say "go buy this"

Yes, Brian's plan was to fold encryption into ZFS after 0.7.0. It was simply too large of a change to do in one shot.

Don't know if you can use it on FreeBSD yet, but tcaputi added it to Linux here: https://github.com/zfsonlinux/zfs/pull/5769 Matt Ahrens approved the changes, and hopefully it'll get rolled in ZoL soon.

Full disclosure, I work with Tom at Datto.

Datto, Inc. - First CT unicorn, started in a basement and made it very far before taking VC money: http://www.courant.com/business/hc-datto-startuprecovered-mo...

I work with Tom at Datto. He presented all of his design decisions at the OpenZFS developer conference here: http://open-zfs.org/wiki/OpenZFS_Developer_Summit_2016#Prese...

Slides: https://drive.google.com/file/d/0B5hUzsxe4cdmU3ZTRXNxa2JIaDQ...

Video: https://youtu.be/frnLiXclAMo

3 Floyd's Alpha King[1]... best IPA/Pale Ale ever. Let the flame war begin!!!

[1] https://www.3floyds.com/beer/alpha-king/?age_verification=e7...

Any know the difference between Copper Glycinate and Copper Citrate?