Nurlan Kanapin

This is an excellent blog comparing the streaming ingest of row-level operation comparison among the LakeHouse formats. https://lnkd.in/dsCN66_5

1

Today I have applied for the participation in Junction 2024 - back offline hackathon. It’s me, Igor Vernichenko and Aarni Pavlidi who will try to come up with something super exciting for the second time. Or have just fun as we did last time. #junction2024 #helsinkievents #backoffline #hackathon2024 #junction #hackathon

21

3 Comments

The policies being driven forward by Thierry Breton around the EU AI Act have been utmost damaging for the European tech industry, and they need to be revised as soon as possible. We need to better balance driving European innovation through data collection and modeling with conflicting needs such as data protection and safety. We need to ensure we can turn these developments into businesses that can be the pillar of the next generation of companies that provide productivity growth in Europe. We have no other choice - either we do this here, or we will have to take over products developed in the US and in China, as it already happened with search engines, cell phones, and social networks. We wouldn't want to let this happen with AI applications in robotics or digital assistants. #euacc #euaiact #aiact

9

So I became fascinated by C++ coroutines late last week, and have spent a good portion of the weekend figuring out how they work. The TL;DR of my discoveries so far is that C++20 coroutines: 1) follow the best and the worst of C++ practices, and 2) are a really clever way to decouple stackless functions from their execution model. For (1), well, it's C++. No crisp & clean syntax, lots of weird compilation errors, and even weirder runtime errors. I hated them with passion for the first several hours. But then they grew on me, because the flip side is also true. The flip side is backwards compatibility and "only pay for what you use". And introducing a totally new concept — the stackless execution model, effectively, [proto-] green threads — into a mature and complex language is one hell of a pain! For (2), I do believe it's a genius solution for the language to separate stackless functions from their execution model. And C++20 did exactly that. There is literally no event loop in C++20! The claim (as I understand it) is that a tiny microcontroller may want to use C++20 coroutines, and the authors of the Standard are very explicit about not constraining possible runtimes. All that C++20 coroutines do is introduce stackless functions into the language as first-class citizens. And yes, stackless immediately implies resumable. So it is one step about the most-clever-possible syntactic sugar over `setjmp()`. Full one step. But not a millimeter more than this one step. Whether you "execute" your coroutines in a dedicated single-threaded event loop, or a thread-pool-based event loop, or by individual steps via some timer event or even a network packet — that is entirely your call. The stackless functions are there, `co_await` (as well as `co_yield` and `co_return`) is there, no callback hell is needed, and all the RAII and scoped initialization/ownership model is fully intact. Now, I'm still elbows deep in my experiments, but here's the first big LinkedIn-worthy question. Why don't we write our C++20 [unit] tests as corourines? Say, you want to limit some test to five seconds. And fail it as "timed out" within these five seconds. Before coroutines, doing this without instrumenting the very code of the test involved `fork()`-ing the process, effectively relying on the operating system's primitives to ensure proper resource deallocation. With C++20 coroutines, as long as the slow test is slow on non-blocking I/O (i.e. not in an infinite loop, but on something that `co_await`-s stuff), it is possible to time-box each individual test to some five seconds very much organically. Because a coroutine frame, unlike a stack frame, can be `.destroy()`-ed safely and cleanly. So, are we doing it yet? If no, why not? If yes, what would be some next-gen `gtest` to look into? Also, I'll be writing some code and blog posts on C++20 coroutines soon. If you are reading this text and are an expert, DM me pls — I'd love to pick your brain!

19

4 Comments

Check out the blog post written by Tomasz Richert (Manager, Engineering at #AllegroTech), which is a case study of how we improved stability in our critical application. It’s mostly a technical analysis of what happens in fresh #Java based instance, how JIT Compiler toyed with us at application start and how we learned to control it. Enjoy reading on: https://lnkd.in/d_BP4g8i #microservice #performance #JVM #compiler

4

1 Comment

Here are the slides for my GopherCon.EU talk: How to Win Frames and Influence Pointers https://lnkd.in/d7byRQfu #gopherconEU #golang

72

4 Comments

🤟 Exciting news! My talk "Representation is King 👑: The Journey to Quality Dialog Embeddings" that I presented at EuroPython is now available for viewing! I dived into how sentence embeddings can enhance the classification of dialogs, showcasing the use of top-performing small-sized sentence transformers. The talk is packed with intuitive, hands-on examples using the SentenceTransformers framework to fine-tune models with labeled and unlabeled data 👐. We leverage similar techniques at Salted CX to create innovative analytical contact center solutions 😎

39

Planning to develop an OTT app on Roku and not sure how to start ? Check out my new blog that'll truly help you start with your Roku app development. https://lnkd.in/dcZau6Gd #ConnectedTV #RokuDevelopment #OTT #Roku #SmartTV

23

Roofline Analysis of Apple Silicon GPUs using MLX I wrote a tutorial (https://lnkd.in/d8N6_8aU) on Roofline analysis and its application to Apple silicon GPU kernel development, a method traditionally used by CUDA kernel developers. A big thank you to Angelos Katharopoulos and Awni Hannun, the creators of MLX, for their invaluable help in making this tutorial possible. The inspiration came from friends who asked why Recurrent Drafting achieves higher speedups on the M2 Ultra compared to the M1 Max after reading my previous post announcing the open-source of its MLX implementation (https://lnkd.in/dNtdfyzW). The Roofline model helps explain the performance differences by analyzing the computational and memory bandwidth limits of the hardware. I hope this tutorial shares my understanding about performance optimization techniques for Apple silicon GPUs and showcases the outstanding performance of MLX as well as the benefits it brings to applications like Recurrent Drafting. Your feedback is welcome!

119

5 Comments

I gave a talk at the most recent London Ruby User Group (#LRUG) on how experienced programmers solve problems, and what that means about how we think and communicate as human beings: https://lnkd.in/eBzTM53t I am really proud of this talk and care deeply about this subject; I'd love if you could give it a watch! (slides available here: https://lnkd.in/eXX89qXe)

38

Being an #engineering #team #lead is a challenging and exciting, yet sometimes lonely role. What could be better than having a community of TLs to help & support each other, learn, and grow together 🤟 ? This is why we established the Wix Server TL Forum. The Wix IL Server TL community has existed for over a decade (Yes! a decade!), but in the last 6 months, we've completely transformed it: We meet biweekly, with each meetup focused on a preselected topic. A sub-team of TLs creates and drives the sessions and discussion groups, allowing the entire forum to share experiences, best practices, and improve together. In the last 6 months, we've covered many hot topics: 🔥 TL role expectations 🔥 Quality! (including reliability, bugs & performance) - how to measure, achieve, and balance with progression 🔥 Effective Code Reviews 🔥 Effective On-Call Practices 🔥 Milestone Planning and Executions 🔥 Mapping & Overcoming Velocity Killers 🔥 Effective Knowledge Sharing Coming soon: 🔥 Product <-> Dev Collaboration 🔥 TL <-> HR Collaboration Looking forward to more leadership learning and fun! 🤩 We’re always on the lookout for talented TLs, so check out our open TL and non-TL positions: https://lnkd.in/duFHZBKU #Leadership #Engineering #TeamLead #Wix #KnowledgeSharing #CareerOpportunities

49

There is a new open weights model on the Hugging Face, called MiniCPM V2.6 by OpenBMB. Of course, I tried it locally on my personal MacBook Pro and the HuggingFace space. I used a receipt from two days ago as the input image and asked some questions about the image, including an attempt to extract all the text from the receipt image and format the output in a JSON format. The model wrote the JSON format correctly, but it was not in the video. Perhaps it was because I didn't provide a few-shot examples for the model. Considering the model's size, it's an excellent model to tinker with. I'm not sure yet about running it on a production scale. Primarily because I didn't have enough time to explore the limits of this model. I'm interested in running it natively on the MacBook using the MLX framework instead of using PyTorch with the transformers module. Anyway, it was my first experience with the model. It's a good first impression. Links to the video: - Running locally on my MacBook Pro: https://lnkd.in/g7Du4jyw - Trying on the HuggingFace space demo: https://lnkd.in/gFXs2Rf2 Try it online at https://lnkd.in/ggDHQp7D See the model card at https://lnkd.in/gZ5PR4i4

94

1 Comment

This is a great blog from Gian Marco Iodice . Arm and Meta have a fabulous collaboration to empower developers to deploy quantized Llama models on Arm CPUs with ExecuTorch and KleidiAI. That's 4 great areas of progress in one sentence: quantization improvements, new Llama models, ExecuTorch beta release, and the great and growing KleidiAI backend. Whether you're one of over 20 millions developers targeting Arm, or one of the billions of users of Arm-powered devices, discover how you can leverage this powerful and innovative collaboration for mobile! Check it out here: https://lnkd.in/eepURWdX

13

"The essential labor of data work, like moderation and annotation, is systematically hidden from those who benefit from the fruits of that labor. [...] Many tedious, thankless, or psychologically damaging tasks have been outsourced to poorer countries, where workers are happy to take on jobs for a fraction of an American or European wage. This labor market joins other jobs of the “dull, dirty, or dangerous” category like electronics “recycling” and shipbreaking. The conditions in moderation or annotation work aren’t as likely to cost you an arm or give you cancer, but that doesn’t make them safe, much less pleasant or rewarding." Interesting data from "The Data Workers' Inquiry": https://lnkd.in/eXNPGQxs

4

New Blog Post ! Ever wondered how Ruby handles concurrency and parallelism? In my latest post, I dive deep into Ruby’s approach to these concepts, focusing on Ractors, Threads and Fibers. https://lnkd.in/eSGw3CPW If you're curious about Ruby, i'm just starting a little series on it so stay tuned for more Ruby shenanigans ! #Ruby #Threads #Fibers #Ractors

1

Exciting times ahead at Autonomys (formerly Subspace)! 🚀 We're pioneering the Age of Autonomy with our identity-based decentralized AI (deAI) stack for human + AI (H+AI) collaboration. Our Autonomys ID (Auto ID) protocol ensures secure, verifiable identities for both humans and AI agents, fostering a trustful, ethical AI environment. With distributed storage, compute, and a robust dApp suite, we're setting the stage for scalable, AI-powered applications. Join us in this journey towards a decentralized, autonomous future! https://lnkd.in/eUCn4yZY #AI3 #Web3 #DeAI #Blockchain #Identity #Autonomy #AIRevolution #DigitalIdentity

11

sharpening writing skill is one of killer skill!

2