“Me too!”

😭

Obviously I think dark mode support for documentation is the hot new feature, but Prefect 2.6.7 has some other cool enhancements… that you can read about in dark mode in the docs.

I have a little data I made it from arrays When analyzed & ready Oh data I’ll display My data is so playful It loves to DAG and jin-ja It’s time to blame the data Complain now let’s begin-ja Oh data data data I write SQL all day And when it’s DRY & ready Syntax error on line 8

lots of ppl are angry that they can't buy whatever they want for the lowest possible price, and use economic class to justify their positions (e.g., "you hate poor people"). but taking a hard look at how much things *should* cost is good for labor and the environment.

All contributions matter!

If “returns are made in good times, and reputations are made in bad times” then a lot of VCs are about to cement their reputations with how they support startups exposed to SVB.

I spent a lot of last night working with founders in various stages of preparedness and exposure for the SVB fallout. It is becoming increasingly clear that the question isn’t *if* deposits will become available, but *when*. In situations like this, the most important thing is

Is your code well documented? ArjanCodes explains how to improve the docs in your code. Tip for using LLMs: CoPilot makes good suggestions. With ChatGPT, be thoughtful about prompts. 5 Tips for Writing Great Code Documentation youtu.be/L7Ry-Fiij-M via YouTube

UX tip: Work hard on error messages. They help users recover from their lowest point. Bad errors: • pass the blame • use inappropriate tone • are generic • use technical jargon Good errors: • are clear • explain why • help users fix it • provide reassurance