My initial reaction to the term prompt engineering was skepticism that anything of the sort could be called engineering. Having now spent a bit of time using LLM AI to produce a solution to a small content generation problem, I’ve arrived at a few takeaways, some of which have pushed me to be less dismissive of this notion. ...
I was recently prompted (perhaps by a voice in my head) to come up with my own set of engineering values. What follows is surely incomplete, but it arrived with an odd clarity. ...
There is something about mindfulness meditation that relates to the game of chess and what it takes to play the right move in any given moment. Checkmate sunset, @jachymmichael I came upon this idea while struggling through one of chess.com’s many puzzles and questioning the utility of practicing them. The puzzles on chess.com present the solo player with a single board configuration and ask the player to find the next best move for whichever color’s turn it is....
I wonder if these marches manage to convince enough people to reduce their meat consumption to offset the ill will that they possibly sow. While wandering around in London’s Piccadilly Circus neighborhood, I stumbled upon what I later learned to be the National Animal Rights March. A sizable gathering of colorful and impassioned people, young and old, were marching down the street with signs and banners, advocating greater sensibilities for the treatment of animals and a wholesale prohibition on the consumption of animal meat....
Generally speaking, my advice on this topic would be: Don’t write comments to describe what the code is doing. Code written in an imperative way can be read line by line to determine what processing is being performed. Re-stating the logic or steps of execution in a comment runs the risk of the comment falling out of sync with the code and becoming outdated. If a section of imperative code gets big, unwieldy, and hard to read, that’s probably a sign that a refactoring is needed and some abstractions need to be introduced....