98 karma · joined May 5, 2017
I think if a company is serious about a mix, there needs to be optimization around this. Like, remote Mondays and Fridays, if you want to be remote. Meetings on Tue/Thu. Something like that.
Does Pony have such ambitions (I mean, the Pony team)?
My UC is an actor system in the browser and the ability to create a DSL created using the same language used in programming the actor system.
Pony is not dynamic but statically typed? Maybe it can be overcome by substituting actors since any actor can create any other actor?
Plus I'm interested in graphics. I googled but didn't see any examples of integrating either web or desktop graphics, like Skia.
The reason I answer is because I just had an idea. This doesn't help you, personally, right now, I suppose.
Google had a 10% rule (not sure if they still do) where 10% of the time, an employee could spend time on personal projects.
What if a company said, 10% of the time, you mentor. Those who seek a mentor can just apply to the company and get in line and wait.
Possibly, these mentored people could be future hires, and the employees are improving their abilities/knowledge by having a "teacher" role.
If I was Google's or any company's CEO, I would try this!
If you receive Stock options, you pay taxes over the gains, i.e. the money you would have made if you exercised on that date. Even if you have not exercised. So the options were free, but suddenly you have to find a lot of money to keep them. Or you exercise a part of them.
What about a projector that shoots an image to a persistent sensitive surface. That would be reinvention of photography! Let's say, reset with one frequency of light, then flash with an image that holds for > 24h.
Hm!
When you pet a snake and get bitten, you don't pet snakes anymore. But since you already were afraid of snakes (who isn't), you don't have to test petting it to find out it bites.
So the author doesn't have the eBook instinct. e-book. In other words: "electrified book", "less of a book", "not a real book".
Then, he's not using standard tested consumer channels like Amazon Kindle etc, so then he's on his own. He doesn't need to brag about having to set up a VM and going to darknet to hire a Korean hacker gang and buying a DM cracking botnet to crack DRM. He was just being cheap.
To make it not become a tour-de-force, I start with a golden path, then various aspects (validation, additional operations on data besides rendering, etc). If the data doesn't exist yet, it's mocked. Then later, it's implemented (or made 'live') according to the mocked "schema".
It's not exactly TDD (I rarely write a test except for integration tests or the occasional "let's make sure it's not off-by-one"). It's not top down either, exactly. Perhaps you could call it "needs driven development" or "user driven development". You need it from the start and you use it as soon as possible. From then on, it's just improvements.
If you work back-to-front, you won't have anything working until late in the game. You're constantly imagining all the non-consequential "what-ifs".
But in a way, front-to-back is like TDD except you're not testing via unit tests. You're testing by using. And you will be using it so much that it will be tested thoroughly. You iterate continuously while the top layer / front end keeps working.
Sure, there can be an overarching design. There can be an architecture. There should be. But after that, it's about slowly molding the system towards that design. If you have understood the design, you know when you're veering off course. For sure, it's not like building a bridge.