Time Management, Signal, ACPI Shutdown, Mobile Pay, REST, WebSockets, Data Lake, Telegram
Post date: Jul 3, 2017 8:44:13 AM
- Why time management is ruining our lives - Absolutely execellent questions. Nothing to add. I'm pretty sure everyone has thought about these things over and over, and formed their own opinion about all this.
- Parkinson's law - https://en.wikipedia.org/wiki/Parkinson's_law - - Nothing to add about that too. It's clear that things which aren't necessary to be done, rarely gets done. But that's just optimization, aka lazy evaluation. I like. There's no point of doing something, which isn't required to be done.
- I'm wondering why privacy app like Signal requires so many rights on phone. Afaik, encrypted messaging shouldn't basically require anything else than networking. Everything else should be optional.
- How to make Windows Server Shutdown ACPI Friendly, using group policy or registry.
- Or alternatively you can use Group Policy: In Security Options, Shutdown: Allow system to be shut down without having to log on -> Enabled.
- Lot of discussion on different mobile payments. Technologies how those operate in detailed level. How to launch products. Covering all aspects, design, technology, usability, marketing, support, users, processes, advertising, sales, overall politics, production environments, certification processes, customer targeting, maintenance fees, pricing models, value proposition, technical platforms, etc.
- One client wrote: "You are a valuable worker, I would hire you for the reason how you see the things: You have a free mind, free of ideologies, pure rational thinking."
- Wondered one project, why they've split functions in two. Many things happen over WebSocket interface, but some of the functions are called using traditional REST API. The WebSocket API uses JSON and IDs, so it's completely asynchronous. I don't personally see major benefits why these tso interfaces are split into two. Of course I've got my own abstraction API layer. So my code doesn't care at all, if it's WebSocket or REST API which is being used to get the data. But still, I prefer using single method, if there aren't any good reasoning why to have multiple alternatives. Some messages over REST API are so small, that it doesn't make sense either. I could understand approach where WS is used for 'notification' data, and then REST API to actually push and pull the large data sets. Currently one thread handles the websocket, and then there's thread pool taking care of the REST requests.
- Yes, I'm Full Stack Developer / Administrator / Business guy. Jack of all trades. But can buy, build, setup, configure, develop, run, manage a whole system and business processes and customers, everything alone from scratch. It requires a lot of studying all the time. But I think it's worth of it. Only thing limiting these activities is time.
- Data Warehouse vs Data Lake, What's the difference? - Nice post.
- This week seems to be rant only week: Telegram bugs. I don't get it, some old photos I've shared about week ago in Telegram Secret chat, just suddenly appeared at end of new discussion stream. I don't really get it. It also shows date which is about one week old for those photos. But still those are at the end of stream which starts today. New posts after those photos didn't jump back today, but appears to be one week old also, based on time stamps. I'm just so aww aww aww, about this great technology developed by elite coders. Even more fun, I closed Telegram and restarted and the images were gone. I wonder if they EVER can create anything secure, when the very basic things are so hard they've are desperate to get even those to barely work. - Ding, this applies to just so many programs, platforms and environments.
- I'll be posting in future more details of the integration work I've done. For the documentation I draw some flow charts and stuff, which I can tokenize in suitable way.