Entirely my opinion, but I believe that there are breakpoints at multiples of 1,2,5. So, changes in org structure are needed to adapt at 10,20,50 (and further at 100,200,500) counts. More formality, more processes, more tools, more variety of roles.
If someone is doing a task which takes 4 hours a week, in a team of 10, on scaling to 50 it likely becomes a half FTE level work. Not everything scales that way, obviously, but it's a good way to model new roles needed.
dBase was the gold standard for this back in the 80s, early 90s. Great tool. Both the "dev" part and how it could be made available to non developers. The freedom of spreadsheets when developing and the constraints of a TUI (or just UI in those days) for users.
I find that, when I lie down, my glasses slip back closer to my eyes just enough to make things go out of focus at reading distance. The weight of the prisms could make it worse. Have you figured out some solution for this? If you have, it could be a game changer for me!
I haven't tried it, but maybe some larger nose bridge pads with a bit of friction, that would maintain the distance?
Might require you to use a dedicated pair of glasses just with this, if you need some kind of spacing/padding element affixed that you don't need otherwise.
Nostalgic! Turbo C was my preferred IDE over many years in the late 80s to mid 90s. What an amazing tool! Those key bindings, used in so many other IDEs since, are burned into muscle memory. Even after decades of not using them, they bring a smile back. CodeWarrior, the debugger, helped me understand what happens when you run a program more than literally anything else I read or was taught.
This looks awesome. Would you have any data on the performance of large number of invocations of small scripts? I am wondering at startup overhead for every script run. which the 500kloc/s may not capture well.
It depends on your exact usecase, I'm not 100% sure what you're asking. There is some overhead for invoking the compiler on a per-script basis. If you're parsing once but running a script many times, Bolt provides some tools (like reusing a preallocated thread object) to ammortize that cost
We have a server which uses Lua based script plugins. They are usually a few hundred to a few thousand lines and get invoked via APIs. I was trying to figure out how Bolt will behave in such a context and whether we could replace the Lua based plugin engine with this.
You can absolutely do this in India. Every card based subscription requires an explicit authorization to set up. And every such authorized subscription can be seen in the bank app/site. You can choose to cancel those subscriptions at the bank end and the subscribed services will fail their next renewal. This is not just a service specific thing and is required by regulation for all recurring payments, incl utility bills, insurance premia, entertainment service, cloud services.
Anecdotal, I have been using 10, 20, 50, 100, 200, 500,... as the 'break points' where organizational structures need a rethink. So far, it has worked for me. These also match the lines on a log graph.
I used to think of building something related to let a mic pick up a single person to handle questions from the audience, during presentations. Will save the hassle of passing around mics.
This looks like it could do just that with the headphones feeding directly into the mixer and behaving like a focused mic.
If someone is doing a task which takes 4 hours a week, in a team of 10, on scaling to 50 it likely becomes a half FTE level work. Not everything scales that way, obviously, but it's a good way to model new roles needed.
reply