Marijn Meijles

I came here to express my deepest respect to Maarten van Steen (and I presume to Andrew Tanenbaum as well). Recently, I received digital copies of their book 'Distributed Systems' for absolutely free, available upon request through van Steen's website: https://lnkd.in/dSrdHepd This is basically how spreading knowledge shall look like in the digital era.

13

Misconceptions about CSS Specificity – Bram.us https://buff.ly/3WLoCki Whenever a post about Specificity in CSS – and by extension the Cascade itself – gets published I get very excited as it’s a core concept of the language that everyone should know. The more articles on this, the better! However, I also sometimes raise one of my eyebrows as sometimes I, unfortunately, encounter something that’s just outright wrong.To remove some of the confusion, here’s a list of misconceptions about Specificity in CSS … Source: Misconceptions about CSS Specificity – Bram.us ()

6

Did a little writeup about the virtual #BevyEngine meetups I started organizing: https://lnkd.in/ezTxphZZ - why and how it started, what's the tooling behind it and why plus learnings. Let me know your thoughts! #rustlang #gamedev #events 🦀🎮

8

Update: CodeSee has been acquired by GitKraken! --- I am very sad to announce - officially - that CodeSee will be closing its doors and shutting down commercial operations on Thursday, Feb 22nd. All paying customers and free users can continue using CodeSee until Feb 22nd. We have a team that will maintain the service during this period and continue to support you. Thank you to everyone Thank you to all the customers who partnered with us. You were invaluable for helping us build CodeSee. Thank you to the open source community who were our closest collaborators from the very beginning. Thanks to all the employees who joined CodeSee. We’re proud of both the team and the product we built. Thanks for taking a bet on this startup journey. Lastly, thank you to all our investors who bet and supported us on our journey. Why we made the decision I can only apologize to everyone for this difficult turn. The company had more than doubled the number of new product logos in 2023 and grew by many thousands of free users. However our sales growth was inconsistent, and we needed to make revenue faster and more consistently. Given the nature of trying to solve code understanding, this meant being able to deeply cover more complex codebases, more IDEs, more tech stacks, and more programming languages which would have taken time that we didn’t have. And Gen AI has made this space even more complex, both as a tool to help and a source of ever more code to understand. As any startup founder, I had to make some tough calls on where to focus our efforts, but in the end those choices did not lead to the consistent revenue we needed for us to continue. Although we did receive a term sheet to continue going, we ultimately decided that it wasn’t enough to cover this mandate and deliver a truly valuable product. Here's our goal with CodeSee right now... Plan A: - Complete the process of finding a home for the tech and team. We're already in talks with several companies now and want to find the best mutual fit asap. Plan B: - If we don't find a good mutual fit, the team will (sadly) go our separate ways. Code Understanding is still awesome After this journey, we have no less enthusiasm for developer productivity and developer experience. We still think that when developer’s lives are easier, it’s pure magic. After speaking with thousands of companies, it’s clear that code understanding is still a vital problem to solve. It’s been an absolute pleasure to build tools to bring new and impactful ways of understanding code to the developer community. Even though CodeSee’s journey may be coming to an end, our passion to serve this amazing community is as strong as ever.

746

126 commentaren

Substrate is live! After nearly a year of development, really honing the developer experience and performance tuning a very unique runtime environment, we're finally releasing what we feel is by far the best way to run multi-inference workloads (e.g. agents, multimodal text, json, image, audio, embedding pipelines, etc). Substrate lets you use a ergonomic SDK (we really obsessed over the abstractions and typeaheads) to describe precise and complex relationships between AI tasks. And—importantly—it's connected to a backend specifically designed to run these graph workloads as efficiently as possible (optimized models, auto batching, insanely fast inter-node RPCs). Given the current state of "AI" models, we really believe that this pattern is the most effective for building capable, reliable, legible, extensible features with AI that go far beyond chatbots. We need both heuristic models like LLMs as well as normal symbolic computation, and a flexible/scalable way to coordinate these two modalities. We've already seen organizations like Substack building some super interesting pipelines that they can easily understand and iterate on, that just work at scale. It's still early in a much more ambitious vision for us, but we think this V1 is not only ready but already a meaningful improvement to many implementations. Reflecting on the last year, I feel so much gratitude for the team that I'm working with: Ben Guo, Liam Griffiths, Rishabh Parikh, 💭 Kyle Pitzen, Chris S., (& Hanwen Wu soon!). With this launch, we're announcing an $8M Series Seed led by Lightspeed (Nnamdi Iregbulem+Guru Chahal) with participation from many others. Feeling a ton of appreciation for the folks that took a bet on us or have lent their time and advice: South Park Commons (Ruchi Sanghvi+Aditya Agarwal), Craft Ventures, Red Swan Ventures (Andy Dunn), Lorimer Ventures, Chris Best, Jairaj Sethi, iqram and the immigrant groove, Andrew Kortina, Guillermo Rauch, Immad Akhund, Sam Lessin, William Gaybrick, Gokul Rajaram, Jana Messerschmidt, Shreyas Doshi, Matthew Hartman, Mike Cohen, Sabrina Hahn, Anne Lee Skates, Shreyans Bhansali, Julian Connor, Namrata Patel + many many others. https://lnkd.in/eHq8KUkA

125

9 commentaren

It's really cool that people are slowly starting to notice RIFE2 and bld, and recognize why they matter in the Java ecosystem. Thanks Leonardo for the great blog post: https://lnkd.in/eg6sDygu #java #webframework #bld #buildtool #maven #gradle

5

Some years ago I witnessed a fuckup 💥 which let to the creation of our Rules of Play and the need for a macro architecture and guidelines. In the early 2010 Scala as a functional programming language became very popular. We were a Java Shop with an occasional Groovy service. All JVM based. One team decided that they wanted to try out something new and went for Scala. It was cool, new features, functional, less boilerplate. It was hype. As you have it in your head right now: But hey, there must be some governance around this. Yes, we had. But not as much as we needed to. We were heavily growing, we scaled from 10 to 120 people in 2 years. We were distracted. So much was happening all at once. Software was written, the product owner like the outcome. At least one other team tried to emulate the functional style in Java, where everything at the end had an .apply() method. The idea was spreading. The intervention came late. The Head of Architecture stepped in and made it clear, that the course had to be reversed. Introducing in a growing organization with existing hiring, a functional language was too much at this point. This needs to be rewritten in Java over the next few weeks. The story could end here. What did happen was that the product owner did not want to put time aside for a rewrite with no new features. I can only imagine how the developers tried to convince the PO to migrate away from their beloved Scala. At the end, the team happily coded away in Scala and nobody noticed. Until one day, weeks later. So much code was written already, and the pressure was even higher to deliver, that nobody considered a rewrite any more. So we had now officially Scala in our Tech Stack. This all worked all nice under the circumstances until the first Scala people left and others had to take over. They did not know Scala. They had to learn it. And some did not want to. We kept Scala alive. Over the years, we always had to make sure that we have 2-3 people knowing Scala are in that team. As the hype dried down, it was harder and harder to get the right developers. People leave, but technology stays. We fucked up. After all of that, we came up with two rules regarding programming languages. - It had to be JVM based - If you want to introduce a new language, you need to convince the management team, that the benefits outweigh the costs. This way we could still introduce a new language and get the benefits, but only after all relevant arguments were heard. Years later, we introduced Kotlin. In another company, one person was advocating for Rust. We were a JavaScript and Go shop. We did not introduce Rust. What did I learn - A few hard guidelines are important. There should be only a few and these should be strict. - Product and Tech need to be aligned. Because of this misalignment, the product owner did not have a chance to understand the tech implications for the company and the product of using a new programming language.

51

16 commentaren

Apparently, it's that time of the year where I publish a book review. 🖥️And this time this is directly related to work. So are you curious about platforms and how they succeed or fail in taking the lead 🦸in their market ? 📚 Find out some ways to make sense of it in these books reviewed at https://lnkd.in/ePYgxBTV

10

1 commentaar

Looking to save money on your daily groceries? 💸🛒 Excited to share my latest little project: "Salling Stores Clearance Monitor"! 🚀 This #JavaScript application observes local supermarkets like Bilka, Netto, and Føtex for newly added discounted items and sends push notifications directly to your phone so you never miss a great deal! 📲 I developed this using Salling Group's public "food-waste" API endpoint, making it easier than ever to find savings while reducing food waste. ✨ Check out the project on #GitHub: https://lnkd.in/dTbFYaf4 #OpenSource #StopFoodWaste #SallingGroup

3

2 commentaren

Manifest V3 has arrived in Chromium-based browsers, impacting privacy and customization options. This change makes it crucial to reflect on the importance of freedom and choice in our online experiences. Your Choices: Safari or Firefox While Safari offers a solid experience, Firefox stands out for its commitment to privacy and openness. Why I Choose Firefox: 🔒 Privacy First: Protect your data with Firefox's robust privacy features. 💡 Open Source: Transparency and innovation through community-driven development. 🔧 Customizable: Tailor your browsing experience to suit your needs. Support a more open, privacy-focused internet. Join me in switching back to Firefox and championing digital freedom! #Browsing #Firefox #SwitchingBack #Privacy #ManifestV3 #DigitalFreedom Let's make a statement about the future we want for the web! 🌍✨

1

My thoughts about Google IO, innovation, the AI hype and "putting all your eggs in one basket". TLDR: 🤔 I think that AI is overhyped! 🔥 Video and image generation is wild though (not mentioned in the video) 🔎 Google IO is not cool anymore. What do you think? 🥚 DONT PUT ALL YOUR EGGS IN ONE BASKET! if they pull the plug on you ... you're done. #googleio #innovation #techstartupsuk #cto #techinvestor #fintech #ai

3

Ever clicked "confirm" only to see "seats unavailable"? 😞 Wondering why your movie seat bookings fail at the last moment? 😕 We've all been there. But what's the REAL reason behind this ticketing nightmare? In my latest article, I dive into the fascinating world of database locks and transactions that booking websites use to prevent double bookings and ensure a smooth user experience. 🚀 Curious about how it all works? Check it out here: 👉 From Frustration to Fascination: The Truth About Double Booking Problem

18

1 commentaar

--- Make a positive difference. Do what you love. --- That’s why you’re working in the software industry… to contribute to something that makes a positive difference. And to do what you love. So you invested your time. Committed. It demands a lot of your creativity. Continuous learning. Keeping up. It’s challenging. And perhaps the constant high pressure is getting to you: - Sacrificing personal time and relationships in favor of work - Decline in health - Too much stress which can lead to burnout - Feeling unmotivated You never signed up for that. And you don’t know what to do about that. You were never taught how to handle tight deadlines and high pressure. In 2006, I was where you were. And I learned how to handle it through various courses and learning specific techniques. Because I was depressed and needed to know how to handle it. You can learn them too because your well-being matters more than any job. So you can keep loving what you do. And continue to make a positive contribution. It's possible to have a sustainable career without burning out. So you can be thriving and helping others with your talents. ♻️ Repost if this helped or inspired you in some way 🔔 You can follow me, Tom Verbroekken for more inspiring content like this 👇 If you'd like to get help with combatting stress or being more productive, then you can check out the link in the comments below

6

1 commentaar

⚡ Shocking but software doesn't run for free... ⚡   🌱 Last week, I had the pleasure of attending the 2nd meetup in Amsterdam of Green Software Foundation - The Netherlands 🇳🇱. While I already knew a lot about Green Software, the presentations reinforced the concepts and added great perspectives. I also enjoyed sharing and hearing from others about what made them interested in Green Software. Of course, the immense carbon footprint of LLMs/AI had to be mentioned, specifically by estimating the impact using the Software Carbon Intensity (SCI), which has recently become an ISO standard, through the Impact Framework. 💡 My biggest takeaway was that you should first optimize system utilization, addressing the embodied carbon in servers and the issue of underused servers, before focusing on optimizing the software itself. This can be seen as the "low-hanging fruit." 💧 Secondly, Wilco's presentation reminded us to consider the impact and measure it. Fortunately, I work at HULO.ai, where we strive to make a significant impact by saving a lot of drinking water through better leak detection and localization. 🚀 From the start, HULO.ai has cared about its (software) footprint, and luckily our software does not require huge amounts of data to be trained. As a startup, there is still a lot of work to do, but I believe we will continue to improve and keep tackling the impact we make each day! 🏆 Thanks to Wilco Burggraaf for the invite and Vandebron for hosting the event. 🎓 To learn the basics of Green Software, take the very short course on https://lnkd.in/eyTCWFhn 📆 They will organize many more meetups, so follow https://lnkd.in/eQpgSARX #greensoftware #meetup #impact #ai Frank van der Hulst | Laura Garzon Useche | Robbert Lodewijks | Redmer van Netten | Rudy Dijkstra

18

2 commentaren

If this is not influencing, I don't know what is I shared my appreciation for #oyo 's blog [https://lnkd.in/eG82BJ9c] about Micro-frontends, which encouraged me to try it out on my project, of course use-case presented itself once I knew more about MFEs. OYO #frontend #react #microfrontends #javascript

6