durub
Joined 12 years ago
Joined 12 years ago
I'm pretty sure he has a better than average grasp on what it means to learn and how to improve the process. And even more importantly, he's trying to! If not him, then who should we listen to?
I don't have a clue why GP reduces Sal to "good at explaining things" when Khan Academy is so much bigger than just him for a long time now. And I, for one, am very grateful that he exists. People in first world countries can't imagine the impact that free access to great education resources has in the rest of the world, like in my case.
> At the gym, people assume anyone with big muscles must be an expert in medicine. Let's not make the same mistake here.
The gym analogy falls short to me. The mistake here is assuming that someone that worked in education for almost two decades, and has achieved extraordinary results in the mean time, doesn't have any clue about education in general.
I believe what you are looking for is a product lifecycle management (PLM) software.
I'm not certain at which scale it makes sense, but the team was looking at Teamcenter from Siemens at the time: https://www.plm.automation.siemens.com/global/en/products/te...
It seems expensive but very complete.
We shipped around 500-1000 units per year and as the devices were sensors/actuators connected to the internet which we continuously supported, we kept device information in a RDBMS on our backend. We registered them via NFC after they left the factory and configured them afterwards on installation.
If you're looking more for post-sales servicing, depending on the team's skill set and device service volume, I reckon you could wrangle all this in Excel/Airtable.
We had the same problem here. What we implemented is:
1. Have a separate step on the project management board describing "In Review" (QA) and "Deployed" (in production)
2. Interested parties (sales and marketing teams, for instance) should have "Observer" access in the ticketing system and follow relevant issues
Alternatively, you can ditch the Observer access and do the release notes based on what was "Deployed". If learning how to navigate the ticketing system generates friction for your interested parties, this can work better. Not an issue for us as everyone uses the same system to track their tasks.
I "discovered" this some a few weeks ago while watching my co-founder sell very well. Afterwards, we were discussing it and I said, "man, you should see my brain when I'm programming, it's kind of amazing!" and then it dawned on me what was happening. A mixture of a visual language, with elements from both English and Brazilian Portuguese, and the abstract CS concepts.
When he sells, I'm sure he has his own internal language to do it. He doesn't think about objections, how to answer a specific question, etc. anymore. He just does it. It's kind of fascinating, and the universe is fascinating too. Learning every day!
I'm the one who has to thank you for sharing -- good luck too!
- though
- through
- rough
- cough
- thought
Thanks for the link, jjgreen. Very interesting, and certainly tricky.Being there is the first step. If you aren't "there", paying attention, everything is way, way harder.
If you don't focus on what your tongue, mouth and the air is doing, how are you going to learn to pronounce better? We just try a bunch of things and see what sticks -- not very efficient.
Thanks for the comments, they made me reflect a lot.
I totally agree about (1), and glad to know your experience with shadowing was helpful. How did you do it?
Very happy with it so far. It's free up to 10 users.
I'm also doing an startup -- we've been working on the product for only two weeks and we just released access for our first pilot customer, with an initial feature set we are very happy with. Apart from the productivity, it's been a long time since I loved programming. Keep in mind I was doing embedded C development for a few years, so my web-fu is a bit rusty lately.
The only thing I miss sometimes is types, especially when refactoring. Java with IntelliJ will spoil you, I guess. I was thinking about going with Kotlin because of this, but I was really digging the Phoenix project structure and I love Ecto.
All in all, a great experience.
Currently building Callrox: https://callrox.com