I used to feel this was true for me, and to a large degree still do. But lately I’ve been wondering to what extent this is a self-limiting belief, and how much I can train myself to remain productive in the face of interruptions. My life is more complicated now than when my career started, and the interruption causers seem to be multiplying, so I’m seeing it as something I need to learn to deal with if I’m going to be able to stay in the field.
Possible, yes, and frequently used I’m sure, but entangles the retirees financial future with the business’s future — the retiree loses if the new owners make bad decisions, overleverage, and end up defaulting / bankrupting themselves. I don’t think it’s reasonable to force all businesspeople to retain this risk after disposing of the business concern.
Building inspections are not really the same as purchase inspections, or at least don’t seem to me like they should be. Purchase inspection generally might not see a partially-constructed building or blueprints or otherwise be able to verify the engineering plan is being followed—They’re looking for broken/nonfunctional appliances/mechanicals/systems, clear fire hazards, mold, infestations, and the like.
The outcome of a building inspection is a certificate of occupancy where the authority is stating the home is safe to live in, the outcome of a purchase inspection is a report of things to ask for a discount on, part of the purchase negotiation.
The Chatham County thing is crazy, I’m hoping the family manages to find someone accountable in that mess — clearly either the original architect, the builder, or the county let them down somehow. I’m just not sure it’s really an indictment of the “inspector” profession as discussed in this thread.
I had a manager — who I basically loved — that loved to say “assume positive intent”, perhaps from teammate $T
And I tried!
But my priors were that teammate $T has rejected ideas from most of my design documents for (imho) inconsequential reasons — Eg there were framework scalability concerns of using a framework that handles 1x-1000x the projected growth of the current project.
Telling me to “assume positive intent” from feedback saying it wouldn’t work “because scale” (when we were comfortably 4-5 orders of magnitude away from those problems) felt pretty empty.
More honest pushback would essentially be “this solution didn’t need this scale yet”, or “we can afford to re-architect this right now” — “finding deals” becomes a rent payment from someone figured
I use a similar setup to store code snippets (certain Java annotations for integration/unit tests, various things like that), vehicle license plate/vins, internal (but nonsensitive) ids for test accounts, tons of things like that.
Honestly a password manager would probably be technically better—or a bunch of flat files lol—but there was a certain charm to having it displayed / function exactly as I like it, and lightning quick with nothing I didn’t need.
IDE would be another natural place for a lot of my usages, but I kept finding I needed to leave it in a pull request review or slack conversation or similar, not necessarily programming myself.
Really neat! I’ve been wanting to make something similar for _years_ to be a standardized data modeling testbed as I explore/experiment/prototype some new feature or problem space or even doing ad-hoc fixes. I think this is a much better starting place than spreadsheets/similar.
Good luck with the project! Seems like you’ve got some good interest :-)
The original seems to have been designed with different goals in mind. I have no doubt that the new ux better optimized their new goals, I just don’t agree that the new goals were as useful to me personally.
I am SUPER worried about this when it affects something really important, like getting the client/customer/merchant/cardholder their money. It seems like the world has moved on without me —- “ohh, three nines is enough”… “hrmmm maybe?…”
Really interesting. I've been on Adderall for almost 10 years and am constantly accused of being overly optimistic, which sounds a lot like the "the brain to fix its attention on the benefits, rather than the costs, of completing difficult tasks." from the first paragraph.
So that when I CTRL-R for my-command it automatically reminds me.