TrafOData pivot to become Microsoft was a pretty hard pivot.
1,032 karma · joined October 4, 2017
Software development is in its infancy and has a long way to go. New languages are in important part of that.
The arty passionate person five years later has an entirely new perspective on every single aspect of their venture.
When someone asks me about starting a business, I say, “exactly why?”, “what is is you really want from this, do you know?”. You’d be surprised st how few people are really clear on what they actually want the outcomes to be in a tangible way.
My advice is to create any business that makes money and do your passion as a hobby.
There’s another thing.... people starting their first business generally don’t understand the importance of cash flow. They don’t want to know, they’ve got no reference point in their head to understand it. Nothing you can say will bring them to understand the importance of cash flow. In a years time there will be those who grasped it (might still be in business) anc those who didn’t (out of business).
How does lisp stand in this regard?
You’re surprised? Angry? Indignant? It’s someone else’s fault you had to cheat?
Please.
And they’re clever enough to do it slowly, lots of small transgressions, giving each time to be accepted before moving on to the next quiet domination. Perfect example is taking control of the South China Sea.
And they’re smart enough to colonize in the most modern of ways...... buy the politicians and thereby remove all possibility of government resistance.
In your shoes I’d turn around and make a 1 minute video and upload it to YouTube within 20 minutes, showing what your system is and what these data structures look like.
If you have an Apple Mac, the screen recording is built right into QuickTime, just plug your telephone headset into the machine to record some narrative as you go.
Seriously, why launch without showing people what it is? 10 years coding, not willing to spend 5 minutes to record it and show us?
I’m not interested in reading about the deployment process. Really not.
Sell me on what you made.
I’m not doing the tutorial.
I’m sufficiently interested to give it a 30 second video. If that looks interesting I might look at more involved videos about some aspect.
I hope one day he’ll become a real fan of async as it would be good to have all that skill directed into the async space, which frankly needs him.
Eventually however the bell in your head rings and it all becomes second nature.
At that point you have the ability to do a bunch of things in parallel in an intuitive and robust way.
Also async is good for solving certain categories of problem that are harder in synch, like starting a sub process and reading and immediately responding to stderr, whislt also doing other things, without the issues that comes with multithreading.
What async programming really gives you is event driven programming - the ability just to set up functions to run when certain things happen, as opposed to traditional ... do this step one then do this step two until program finishes. Again quite foreign if you havent done much event driven programming but it’s really powerful.
It is true that certain libraries need to be rewritten to live well in the async world, but that’s ok I think ... it’s not like the 2/3 issue.... you don’t have to go there if you don’t want to.
The other thing that is not immediately obvious when learning async is that once you know what you’re doing, in many cases sync and async style can be naturally interspersed, and while that might sound like a recipe for complexity and pain, in fact it isn’t, because as mentioned earlier, async actually isn’t that hard or complex once you grasp the mental model, and interspersing both just works pretty well. You won’t know how to do that in a simple manner though till you’ve been through the grind of making it hard for yourself because at first you’ll assume that async is much harder than it really is and you’ll be looking for complexity and indeed coding complexity.
I certainly understand the initial distaste that people might have for async because it’s so foreign. It’s made harder in Python because the approach has changed so there’s multiple ways to do the same thing, like “yield from” and “await” which are effectively the same thing. Different ways to do the same thing in a conceptually new and hard idea space makes the hard thing about learning async programming even harder.
BUT, like most things with programming, once you’ve learned it, what at first looked really hard is in fact fairly straightforward, with just a few different rules to follow and that’s pretty much it.
My advice to any python programmer is to invest the time and practice a lot and work hard to master async. It’s not going away, and it will constantly annoy you that this async thing is everywhere but you don’t know it well so you’ll feel excluded and want to disparage it. Get past that and turn it into one of your strengths and a power tool.
It’ll just taste like garden snails while you’re still in that alien learning zone.
Remember that it takes an expert programmer with superior knowledge to know how to do things in the simplest way.
Like flask versus Django.
Straight question, wouldn’t it have been easier to fork falcon and add the batteries?
At first though, learning async programming tastes like eating a garden snail.
Sounds shit to me but I fully respect any system that allows it. These people can probably get on with some sort of life in between their hits instead of spending their lives trying to get in a position to get high agsin.
My question is, is spice an issue in the places where pot is legal?