bobburger

I like that they say “outdated” stereotypes like they used to be true but now they aren’t.

Come on people, keep your steroetypes current.

Check out Interstellar

If you’re doing a lot of reporting I highly recommend getting familiar with Quarto. It’s incredibly flexible for writing ad hoc reports, automated reporting, dashboards, presentations, etc. You can use python, R, observable, or Julia.

This Git repo has a list of hidden ESPN APIs that might be useful for automatically pulling data.

Right? I want a PHEV so range isn’t something I really need to think about.

Fun fact: the person your replying to had absolutely no idea that a desalination plant was involved in this process.

Since a lot of people seem to be jumping to extreme conclusions about this based on specious assumptions, here’s how the process works according to the article:

Magrathea — named after a planet in the hit novel The Hitchhiker’s Guide to the Galaxy — buys waste brines, often from desalination plants, and allows the water to evaporate, leaving behind magnesium chloride salts. Next, it passes an electrical current through the salts to separate them from the molten magnesium, which is then cast into ingots or machine components.

deleted by creator

Llamafile runs entirely on your machine. The largest one I can run locally is Mistral-7B and Wizardcoder 13B. They seem to be on par with chatgpt-3, but that’s okay for my purposes.

I use it for exactly the same thing.

I used to spend hours agonizing over documenting things because I couldn’t get the tone right, or in over explained, or some other stupid shit.

Now I give my llamafile the code, it gives me a reasonable set of documentation, I edit the documentation because the LLM isn’t perfect, and I’m done in 10 minutes.

A simpler answer might be llamafile if you’re using Mac or Linux.

If you’re on windows you’re limited to some smaller LLMs without some work. In my experience the smaller LLMs are still pretty good as chat bots so they might translate well.

I love duckDB, my usual workflow is:

• initially read my data from whatever source (CSV, relational database somewhere, whatever)
• write it to one or more parquet files in a directory
• tell duckdb that the directory is my data source

Then duckdb treats the directory just like a databese that you can build indexes on, and since they’re parquet files they’re hella small and have static typing. It was pretty fast and efficient before, and duckdb has really sped up my data wrangling and analysis a ton.

Should include “has duckplyr” which is bad ass in the few weeks I’ve been using it.

Break down of different self driving levels

🤨

A chatbot with a sick mullet

I have a soft spot for Jenkins because it was the first integration tool I ever used fresh out of college.

But today I want to stab the server because a job started failing randomly with a permission error when trying to copy a file.

I have a soft spot for Jenkins because it was the first integration tool I ever used fresh out of college.

But today I want to stab the server because a job started failing randomly with a permission error when trying to copy a file.

First, I’m glad you made it to the fediverse Loon-god, you’ll always be a Warrior’s legend.

Second, anecdotally even the crappy results generated by LLMs have value for me. Writing emails, jira tickets, documentation, etc. are all incredibly painful for me. I’ll start an email and suddenly folding laundry I’ve ignored for 2 days is the most important thing in the world for me. Then the email that should take 5 minutes takes me an hour and turns out being way to long and dense.

With an LLM I give it a few bullet points with general details, it spits out a paragraph or so, I edit the paragraph for tone and add specific details, and then I’m done in about 5 minutes.

LLMs help me to complete tasks that I really really don’t want to do, which has a lot of value to me. They aren’t going to replace me at my job, but they’ve have really upped my productivity.

41% is the number of executives that think AI will reduce their work force, not the number of jobs they expect to replace.

Your point stands though.