292 karma · joined April 17, 2014
Therefore, even if other languages are better for certain tasks, the Python programmer is rarely ever forced to go looking for them.
This is what I've been thinking about for my own life, anyway. YMMV.
I don't know which view is right, but the philosophy is fascinating.
No, it's a matter of philosophy. The newbie who has learned to code without ever being taught SQL, and the employee of an "agile" app sweatshop who doesn't care about the quality of his code or data, may prefer ORM for its' quick-and-dirtiness, or may use it by default because he knows no better way. I'm not saying that's wrong, but, there are other philosophies. There is the whole "craftsmanship" idea out there, that we should actually care about making things well. Jobs and Wozniak for example supposedly were adamant that the insides of Apple computers were designed well. If you care about your database and want to use special features like triggers, procedures, recursive queries in Postgres, etc., then ORM is about as helpful as clamshell packaging.
I can see using Django to rapidly prototype some kind of CRUD app, but on the other hand, you could just use Wordpress for that. Flask seems like it would be a superior platform for engineering anything non-trivial, especially if you care about how it works.
So my unsolicited advice is that you need to come up with a way to see yourself differently. Maybe as a man of faith. Maybe as a mountain climber or something. Consider giving yourself a mission that will get you the heck out of your apartment and take up all your free time, so that your addiction becomes an annoyance that you won't want to bother with.
And good luck!
However maybe forward time travel (faster than usual I mean) could be possible. But... how would it make any money? As soon as you've delivered the service, the deadbeat customer may not be back in town to pay his bill for decades or centuries! And 30-day jumps just seems silly.
The probe would have to be self-navigating to a certain extent, because we can't locate and measure the exoplanets with precision and won't be able to communicate in near-real-time to guide it in. It would have to be built for long endurance and have the capability to repair itself, too.
The final practical problem is that we wouldn't know for decades whether the probe had been successful, partially successful, or a total waste of time. It could land on an exoplanet and do wonderful science but not be able to communicate due to a broken radio. Or it could blow up in year one and we might not notice.
I suspect the first insterstellar probes instead will be inexpensive and disposable "fire and forget it" types launched with a booster rocket (maybe like the one Elon Musk is building) and no intention of decelerating or landing. They might spend centuries in flight and be designed to send pictures and data back to whoever might be listening in the future. If they're cheap enough and we have extra thrust, I could see rich people and governments launching these in hopes of a sort of future glory, knowing that each individual probe faces long odds but a thousand of them should produce at least a few winners.
Technical skills can be learned and demonstrated, but being 19 years old carries some doubts along with it. Maybe you would need to prove yourself by putting in some time at the IT help desk just to show that you are mature enough to handle responsibility.
Still, I don't know if it's fair to pick on a technology that's so new. In a way, they're still learning, and they're following the advice that many in the design thinking movement would give: make a prototype, even if it's not perfect, and try it out with real customers.