524 karma · joined July 8, 2021
In this case, it is pointless though, since the precision is actually known.
1. You get passive cooling in the summer 2. The greater the temperature difference is the more efficient the pump becomes so they are more efficient even in not so cold weather 3. The maintenance costs of the system are significantly less. You need to clean and replace blower fans. Cleaning has to be done yearly or twice yearly depending on environment. Ground source, you only need to maintain the pump and coolant which needs replacing cca once every 20-30 years.
I think all this software that we will create will end up being used to optimize a lot of processes such as power generation, agriculture, and manufacturing. We will have specialized software for recycling things, leading to a much more circular supply chain. Right now it doesn't make sense to sit down and figure out how to clean, test and repurpose objects, but it will make sense once computers get smart enough.
In terms of jobs outside of computer science, as everything on the production side gets more and more automated, we are going to see much much more paid emotional labor. More people working in coffee shops, bartender/therapists, paid pen-pals ect. We will also see a huge growth in the services for end of life. Now, people who are dying often lay uncared for in group homes, alone, sad and frustrated. In the future, there will be people reading novels to them, and doing finger painting with them.
Every child will have the opportunity to have private tutors.
Medicine will start to work and biological mortality will decrease.
We'll go to the stars.
Maybe I'm just dreaming...
Hello, would you please check this email for typos and provide general point by point feedback:
<body of email in Czech>
It responds with something like:
Thank you for your email. Here's my feedback:
- The opening greeting "Dobrý den" is appropriate for formal communication in Czech, but it's not clear who the recipient of the email is. It's always a good idea to include the name of the person you're addressing to personalize the message.
- "napad" should be "nápad" with an accent mark.
- "Uvažuji o možnost kombinace nerezové časti se tradičný deskou tak že by byla dva kusy tradiční desky které bych vzal ze bauhausu a jeden kus nerezu se dřezem." This sentence is a bit long and complicated. I would suggest breaking it down into smaller sentences for clarity. Also, "tradičný deskou" should be "tradiční deskou" with an accent mark, and "nerezu" should be "nereze" with an accent mark.
- "Mohu poptavat nasledujici:" could be phrased more clearly. You could say "Můžete mi prosím zaslat následující informace?" to ask for the information you need.
- "Deska se dřezem 230cm dlouhé (trochu jsem opravil i velikost dřezu)." This sentence is not clear. It would be better to rephrase it to something like "Potřebuji desku s dřezem o délce 230 cm. Změnil jsem trochu velikost dřezu."
- "2x nerezový lem pro připevnění na klasickou desku aby lem byl ze stejného materiálu a vyšky. 211,5cm a 41,5cm." This sentence is also a bit confusing. It might be clearer to say "Potřebuji 2 kusy nerezového lemu o rozměrech 211,5 cm a 41,5 cm pro připevnění na klasickou desku. Lemu by měly být stejného materiálu a výšky jako deska."
- The closing "Děkuji" is appropriate, but it might be nice to include a closing statement or a salutation, such as "S pozdravem" or "S úctou."
I make my changes and we go back and forth about 4x before we're both satisfied. It is much faster than bothering friends and relatives and the results are perhaps even better since it gives me more freedom to keep my own voice (friends and relatives often have hard headed opinions on how to communicate which are unrelated to language).
I can Transform Your Legacy Codebase into a Valuable Asset
Hello. I am a consultant specializing in old and poorly documented code bases. I have been writing code for over two decades and have worked with over a dozen languages including: Python, Rust, golang, C, Java, Javascript, Typescript, Haskell, and Elm. I can dive into an unknown and poorly documented code base, document it, write tests and provide professional on-boarding videos to get your team up to speed. I provide comprehensive training and documentation to ensure your team can effectively maintain and enhance your legacy codebase long after our engagement is over. I can also diagnose, reproduce, and fix hard to understand bugs in complex systems. By bringing old code bases up to modern standards I can help you harvest the valuable IP assets you already have, driving new growth and stabilizing the technologies upon which existing revenue streams rely.
I work with companies of all sizes, from startups to established enterprises, who are looking to modernize their legacy codebases and improve their technology stack.
With my help, I can transform a stagnant legacy product into a proven technology which you can believe in and sell.
Past projects include:
- Updating and documenting a legacy telecom diagnostics system which processes hundreds of gigabytes of Netscoute data every day
- Upgrading [django-helpdesk](https://github.com/django-helpdesk/django-helpdesk) to use class based views and performing a security audit on accessible endpoints
- Migrating a mid sized organizations server infrastructure from a diverse set of hosts: EC2, Heroku, VPSes to a unified kuberentes cluster, implementing a fully automated and rollback friendly CI/CD system.
- Maintaining, developing and administering a large Django application used for a bike to work event
- Design and implementation of the POSIX device subsystem for Docker 1.0
- Diagnosing a critical and hard to reproduce bug in Elm-lang's runtime.
- Author of [subuser.org](subuser.org]
Find me at https://hobbs.cz or book a call at https://cal.com/timhobbs/longer-meeting
I can Transform Your Legacy Codebase into a Valuable Asset
Hello. I am a consultant specializing in old and poorly documented code bases. I have been writing code for over two decades and have worked with over a dozen languages including: Python, Rust, golang, C, Java, Javascript, Typescript, Haskell, and Elm. I can dive into an unknown and poorly documented code base, document it, write tests and provide professional on-boarding videos to get your team up to speed. I provide comprehensive training and documentation to ensure your team can effectively maintain and enhance your legacy codebase long after our engagement is over. I can also diagnose, reproduce, and fix hard to understand bugs in complex systems. By bringing old code bases up to modern standards I can help you harvest the valuable IP assets you already have, driving new growth and stabilizing the technologies upon which existing revenue streams rely.
I work with companies of all sizes, from startups to established enterprises, who are looking to modernize their legacy codebases and improve their technology stack.
With my help, I can transform a stagnant legacy product into a proven technology which you can believe in and sell.
Past projects include:
- Updating and documenting a legacy telecom diagnostics system which processes hundreds of gigabytes of Netscoute data every day
- Upgrading [django-helpdesk](https://github.com/django-helpdesk/django-helpdesk) to use class based views and performing a security audit on accessible endpoints
- Migrating a mid sized organizations server infrastructure from a diverse set of hosts: EC2, Heroku, VPSes to a unified kuberentes cluster, implementing a fully automated and rollback friendly CI/CD system.
- Maintaining, developing and administering a large Django application used for a bike to work event
- Design and implementation of the POSIX device subsystem for Docker 1.0
- Diagnosing a critical and hard to reproduce bug in Elm-lang's runtime.
- Author of [subuser.org](subuser.org]
Find me at https://hobbs.cz or book a call at https://cal.com/timhobbs/longer-meeting
https://hobbs.cz/wearable-computing/adventures.html
Obviously it's important to make sure you aren't bothering other people in a way they cannot easily ignore. You shouldn't make too much noise, especially at night, or create too much smoke or other bad smells. But being weird hurts no one. Why should I limit my own freedom out of fear of being weird? If it seemed to have a negative effect on my job prospects I might be less weird, but I find the opposite is true. Being weird has probably had a negative effect on my dating life. Then again, I don't want to date someone who is going to restrict my creative freedom by hating my weirdness anyways. Being a coward is far worse when it comes to finding dates than being weird, and being weird in public can help you learn not to be a coward.
I also see letting it all hang out publicly, warts and all as being a sort of protest. If the only ones publishing coding streams were the [Jon Gjengsets](https://www.youtube.com/c/jongjengset) of the world, people like me might simply give up. Surely I'm not the only imperfect coder. Surely I'm not the only one in the world who has spent 10 hours bashing my head against the wall because of a silly typo. I'm here to shout from the hilltops, that it's OK to play amateur football. We don't all have to bend it like Beckham to have fun!
I guess the main thing though is, that I don't really believe anyone will watch all my videos, so I don't feel self conscious doing them.