But as much as I’d like to switch to daily/weekly billing, it feels like I would never allow myself to leave the desk to run errands, play with the kids etc - because I promised to work the (whole?) day/week.
Even if you don’t actively tell clients when exactly you do work, clients can see your away/offline status in Slack/Teams, or they might call you out of the blue, which would feel to me like being caught with pants down - talking about a failed deployment on the phone in the supermarket?
And I’d be worried then that the client comes to the conclusion “Oh that guy, bills the whole week but doesn’t even work in the afternoon. What a slacker!”.
How do you or other people handle this?
Location: US
Remote: Yes (only)
Willing to relocate: No
Technologies: Many since first touching unix in 1989.
Resume/CV: Email me for it.
Email: mikeegg1@mac.com
I have a side project that includes MySQL, PERL and AI(/ML). I've done unix for 34 years. I've done lots of things in those decades including building compilers, debuggers, subclassing X widgets and writing databases. I've written production code in 40 languages. I can and have done lots and still have lots to learn. I live in an RV and can go anywhere and I have a Secret and Security+.
As the years go by one realizes that even these “features” like Org, Dired, etc are just illusions in some sense. They’re just Elisp code someone else wrote and put a name on. You can take or leave them or write your own code that changes/advises/customizes them.
It’s all up to you. You don’t need a blessed “plugin” architecture, some PM at IntelliJ’s permission etc
At some point one realizes the “visual shell” nature of Emacs. Every single piece of text on screen can be programmed to “mean something” (see also: “recognizers” from human interface research) and have actions taken on it either by the editor itself, or external processes / scripts you call with a command. If it’s common enough, make a key binding. It’s your house, do what you want
Depending on how you set up your environment, you may never have to look at text again that you do not have this level of power over. You are no longer at the mercy of “application developers”
I’ve been using it since 2005. Guess how many of 2005’s popular editors even still exist
My recommendation to anyone trying to actually learn is start with the full vanilla config, weird default keybindings, etc, go through the built in tutorials, and only add things to your config that you write and understand yourself. Understand it in its own terms. The plethora of packages, etc have “cool features” but impede learning by adding mountains of complex dependencies that are opaque to the beginner and cause confusion IMO