Kenny (@luzm) header
Kenny (@luzm) profile picture

Singapore University of Technology and Design, Computer Science, Phd, National University of Singapore.

Singapore
Joined September 2008
Photo by Kenny (@luzm)Photo by Kenny (@luzm)Photo by Kenny (@luzm)Photo by Kenny (@luzm)Photo by Kenny (@luzm)Photo by Kenny (@luzm)Photo by Kenny (@luzm)Photo by Kenny (@luzm)Photo by Kenny (@luzm)Photo by Kenny (@luzm)
Kenny retweeted
So, someone came up with an AI-generated formal proof, in Lean, of a solution to the Collatz problem, and it turned out that the “proof” was merely exploiting a bug in the Lean kernel (allowing you to prove anything).
93
193
88
4,011
321,488
I asked opus4.6 to prove causality consistency is implied by sequential consistency, it is a well known and studied result in distributed system. First iteration, it gave me some agda code with syntax error. I asked to fix it, it gave me a compilable proof with some postulated.
1
39
Second iteration: Instead of continuing with the development to provide concrete implementation to the postulated lemma. I stopped the agent and asked it to explain the code/proof it generate.
1
11
3rd iteration: I probed further. I hit the infamous "you are absolutely right" sign of the model is reaching its dumb zone.
7
My friend from Microsoft is looking for a GTM manager to drive Azure in ASEAN. With 10 years of sales marketing experience. JD for reference: jobs.careers.microsoft.com/g…
1
1
51
𝗪𝗵𝘆 𝗱𝗼𝗲𝘀 𝗚𝗼𝗼𝗴𝗹𝗲 𝗿𝗲𝗰𝗼𝗺𝗺𝗲𝗻𝗱 𝗠𝗼𝗱𝘂𝗹𝗮𝗿 𝗠𝗼𝗻𝗼𝗹𝗶𝘁𝗵𝘀 𝗶𝗻𝘀𝘁𝗲𝗮𝗱 𝗼𝗳 𝗠𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀? In the last decade, we have seen a massive trend of using microservices everywhere. We were building systems for a few hundred or thousand users and wanted to know how to make a system for millions of users. This was over-engineering and needed to be corrected. Why it was wrong? Because the development lasted long and we created incredibly complex systems, hard to maintain. This is especially true for startups that must go fast and stay simple. A recent paper by authors from Google found that most of their developers split binaries for one of the following reasons: it improves performance, fault tolerance, and abstraction boundaries and allows for flexible rollouts. Yet, splitting applications into microservices has its challenges: 🔸 𝗜𝘁 𝗵𝘂𝗿𝘁𝘀 𝗽𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲. The overhead of serializing data and sending it across the network is increasingly becoming a bottleneck 🔸 𝗜𝘁 𝗵𝘂𝗿𝘁𝘀 𝗰𝗼𝗿𝗿𝗲𝗰𝘁𝗻𝗲𝘀𝘀. It is incredibly challenging to reason about the interactions between every deployed version of every microservice. 🔸 𝗜𝘁 𝘁𝗮𝗸𝗲𝘀 𝘄𝗼𝗿𝗸 𝘁𝗼 𝗺𝗮𝗻𝗮𝗴𝗲. Rather than having a single bi-nary to build, test, and deploy, developers must manage 𝑛 different binaries, each on their release schedule. 🔸 𝗜𝘁 𝗳𝗿𝗲𝗲𝘇𝗲𝘀 𝗔𝗣𝗜𝘀. Once a microservice establishes an API, it becomes easier to change by breaking the other services that consume the API. So, they proposed the following approach: 𝟭. 𝗪𝗿𝗶𝘁𝗲 𝗺𝗼𝗻𝗼𝗹𝗶𝘁𝗵𝗶𝗰 𝗮𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 that are modularized into logically distinct components. A component is a long-lived agent, similar to an actor. 𝟮. 𝗟𝗲𝘃𝗲𝗿𝗮𝗴𝗲 𝗮 𝗿𝘂𝗻𝘁𝗶𝗺𝗲 𝘁𝗼 𝗱𝘆𝗻𝗮𝗺𝗶𝗰𝗮𝗹𝗹𝘆 and automatically assign logistical components to physical processes based on execution characteristics. So, if both components are in the same OS process, they are called regular method calls, but if they are co-located, calls are executed as RPCs over the network. Runtime decides whether these modules should be collocated or moved to different machines (and scaled, etc.). 𝟯. 𝗗𝗲𝗽𝗹𝗼𝘆 𝗮𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 𝗮𝘁𝗼𝗺𝗶𝗰𝗮𝗹𝗹𝘆, preventing different versions of an application from interacting. This approach consists of two main parts: a programming model with abstraction that allows developers to write modularized applications and a runtime for building, deploying, and optimizing these applications. They claim that it reduces application latency by up to 15x and costs by up to 9x by simplifying application management and deployment. If you want to check the framework implementing the approach from the paper, check https:// serviceweaver. dev/. What do you think about this approach? Does it look like EJBs or CORBA? #microservices
66
761
65
3,391
459,192
> Language Models are gullible. simonwillison.net/2023/Dec/3… I think *complaisance* is a much more pressing problem "You're absolutely right, my previous statement was incorrect." "Thank you for catching my mistake!" ... to the point of being useless ...
3
16
2,881
Donald Knuth advice to young engineers - - Follow your own instincts. - Prestige comes from doing good science, not just popular science. - Deep knowledge builds confidence. - A liberal education involves learning everything about something and something about everything.
8
227
10
1,072
98,360
I am starting a new module "Compiler Design and Program Analysis" in SUTD this coming winter term. I am looking for a guest speaker from the industry who would like to share some industry experience of the using DSL, program analysis or type system etc.
1
1
46
If you are interested to share your experience with the students. Pleaes PM me for details.
22
Police appeal for information on 13-year-old girl missing since Aug 12 channelnewsasia.com/singapor…
2
7
9
Pilot records 53-sec video of strange UFOs lights over South China Sea https://xitter.gq/t.co/82CiDCTqb9
3
19
7
51
Dear community, we know that you are eagerly waiting for the release of the Turing Pi 2. But, our hands are tight by @PayPal. For almost a year they keep frozen our funds necessary to continue operations and launch TPI2. Please share this thread to raise awareness...
105
385
86
491