theIntuitionist
Joined 19 years ago
Joined 19 years ago
We had our place professionally tested, got negative results, then tore the place down to the studs anyway (eventually, after the Petri dish tests described above) and found all sorts of mold.
We are going through this now. It’s no fun at all. We have the house ripped down to the studs. A couple times the plates saved us, showing there was more mold then we’d thought. We’d rip out some stuff we’d found, run the test, find too many colonies on the plate then dig some more only to find more issues. Finally, we are getting clear plates, and I feel much better.
If it does turn out to be mold and fatigue caused by the mold feel free to contact me as I have been through it and am now on the mend. It’s a long difficult process with only the vague signals you mentioned to guide you.
Anyway, I have a real soft spot for the sort of software the author talks about. I think of shops who build software like this as “design build”. Like in the construction world where design build means a small shop focused on overall quality and fit of the home to its owner, not scale or economy, etc. maybe that is a phrase that works?
Not to dismiss the psychological safety point the article makes, which i believe is very valid.
I’m not making a point for or against employing emotions in problem solving, I’m advocating for an awareness that all “logical” thought fits into a larger emotional context- just the opposite of op who structures their process as a pure logical process. Ironically, I’d call the notion of a purely logical process devoid of emotions a fantasy.
Is choosing a life partner a "problem"? What about something as simple as choosing what to wear in the morning or what beer you want from the bar? Even within traditional engineering problems so much of our decision making process can only be evaluated subjectively. Some examples are: naming variables (your compiler doesn't care what you name them), making choices around encapsulation (there are very often many possible ways to do this. we frequently chose the "simplest"- a subjective assessment), choosing a framework or language (a decision which is one part right tool for the job one part joining a likeminded community), etc.
At the root of it, we're emotional beings, not logical ones. Outsource the logical problems to computers, machines, institutions and focus on what makes you human. Otherwise somebody else will make the important choices for you in ways you certainly wouldn't chose for yourself.
- Remote: yes, preferred
- Willing to relocate: probably not
- Technologies: Javascript and Typescript front and back end, NextJs, React, Ruby on Rails, RAG AI
- Résumé/CV: https://www.linkedin.com/in/jason-libsch/
- Email: [email protected]
I've been building software for 25 years, with experience scaling to several million users, running teams of 20+ people, bringing legacy software up to modern standards, building green field startup apps that successful sold. I've built AI (RAG) into a couple systems now. I am mission driven, with special place in my heart for civic software or software for the creative world, but am open to all sorts of configurations.
I'm looking for contract work, and can do anything from quickly iterating on getting a prototype built as a one person team, to fractional CTO work or anywhere in between.