I post whatever comes to mind, kind of just what I'm thinking about at the moment. Tends to break down ~ 50% tech, 50% whatever. @thepanta82 at twitter.
https://pantas.net
The jihad has began.
The jihad has began.
The reason: pg collation is subtly different on mac vs linux, where your actual stuff will be running.
Run db in docker or remotely instead.
The reason: pg collation is subtly different on mac vs linux, where your actual stuff will be running.
Run db in docker or remotely instead.
ANY context switching can kill the flow. Even between projects, or different types of work.
It's just that most corporate devs only do one type of technical work, so all their experience with flow interruptions is centered on meetings.
ANY context switching can kill the flow. Even between projects, or different types of work.
It's just that most corporate devs only do one type of technical work, so all their experience with flow interruptions is centered on meetings.
Your visitors will probably never notice it glitch out once every 10 minutes.
Your visitors will probably never notice it glitch out once every 10 minutes.
And if not, don't you just end up with a lot of broken project snapshots in git history?
There's gotta be a better way.
And if not, don't you just end up with a lot of broken project snapshots in git history?
There's gotta be a better way.
But computers are now getting old enough that we'll learn if OSS can improve like science - one funeral at a time.
But computers are now getting old enough that we'll learn if OSS can improve like science - one funeral at a time.
Every increase in productivity comes at a cost.
Every increase in productivity comes at a cost.
Generally, any rule that's used as a passive-aggressive replacement for communicating with other team-mates is a good candidate to get turned off.
(still trying to figure out how to make "consistent-return" work well)
Generally, any rule that's used as a passive-aggressive replacement for communicating with other team-mates is a good candidate to get turned off.
(still trying to figure out how to make "consistent-return" work well)
git-scm.com/docs/gitrevi...
git-scm.com/docs/gitrevi...
This is some early 2000s web era stuff.
This is some early 2000s web era stuff.
Instead of warning you ahead of time your prompt is too long, it lets you submit it and THEN errors out.
And then, IT DOESN'T LET YOU EDIT THE PROMPT.
So you have to rewrite everything into a new tab. Ugh.
Instead of warning you ahead of time your prompt is too long, it lets you submit it and THEN errors out.
And then, IT DOESN'T LET YOU EDIT THE PROMPT.
So you have to rewrite everything into a new tab. Ugh.