If you are able to isolate the text portion corresponding to the company name, you can compute the similarity (based on the character edit distance - Levenshtein) against every item of a predefined list of companies (and their aliases) and pick the best match.
It's only been added to the OpenAI interface. Function calling is really useful when used with agents. To include that to agents would require some redesign as the tool instructions should be removed from the prompt templates in favor of function definitions in the API request. The response parsing code would also be affected.
I just hope they won't come up with yet another agent type.
When I first encountered the Haskell Parsec library, the beauty of parser combinators hit me and I felt I'd never have to write a regular expression again.
This hasn't been the case because I had to work in other languages where usage of regexes was more idiomatic/commonly understood. Parser combinators are great but most of the time, the problem can easily be solved using a regex and we can't really justify adding yet another library in the dependencies for the rare case it would be better suited.
In addition to all the benefits they can provide in terms or readability, re-usability and abstraction, parser combinators can even compete with regexes in terms of performance. https://pl-rants.net/posts/regexes-and-combinators/
I see a ticking time-bomb and the blind leading the blind. Not sure if those are canonical.
About three dozen other vignettes that I definitely can't pin to anti-patterns. Like man-eating plants, teaching magic to rabbits, gearheads, touching a lightbulb... someone please help.
I wish more stuff came with fun illustrations as canonical "covers." Also the file looks like it's probably exactly what they gave to the printers (the left and right margins are different for odd/even pages.)
I really like your explanation, which I find easier to understand. I do appreciate your "real-life" AST example, making clear that your are making a better design through the typing system facilities.
Understanding how GADT works only comes next to understanding how leveraging the typing system during design can be beneficial. The motivation to go through this tutorial stems from the desire to let the typing system strengthen the programs and API. I'm coming from the Java world and I've spent some time learning Haskell for my own culture. At the time, I was trying to use Java generics to encode some restrictions in my design. It was interesting but alas a bit limited by the Java generics implementation and the results were most of the time hard to use or understand.
I'd like to see more articles on how GADT (or any other mechanism) can improve a concret design, with real-life examples. Starting with a native design leveraging only a few tricks from the typing system up to a final version where constraints are properly encoded.
Nice plug in the middle of middle of the article, exactly at the right spot:
> By the way, I write an article like this every month or so, covering lessons learned from growing B2B software startups. Get an email update when the next one is published
This is the closest I got to subscribing to a newsletter.
> This is the closest I got to subscribing to a newsletter.
Almost got you, huh? :)
I've A/B tested various locations and the inline-embed is the best, by far. This is also why many news sites now include related stories in the middle of the article, not at the end.
Wish the rss/atom was better represented, rather than only existing in metadata on your site. I must be a dying breed, but I refuse to sign up for email newsletters. I refuse to hand over that much of my attention.
That’s interesting. So RSS didn’t stick because it didn’t allow advertisers to harvest email addresses.
Which is stupid because you still can’t reach to your audience if you just buy harvested addresses, so if it’s just people who subscribed to your newsletter, you’re just better off letting them subscribe to your RSS. Perhaps the quantifiability of newsletters vs RSS makes email win. If only RSS had embedded ways to count views and see what users looked at.
Pro-tip: create a dedicated email for newsletters so you don't feel like they're spamming you or clogging your inbox. Ever since I did this I really enjoy finding the occasional unique newsletter.
