Christophe Buguet

Frankly I find ` OOPS generally excessively complicated . The simplest ` object is an " address space " an ordered list . I've commented to Alan Kay long ago , eg: https://lnkd.in/gTSi-fRy https://lnkd.in/gJiuCyFQ , that that what ` objects miss is the ` geometric attribute that APLs , including K , naturally retain . In CoSy.com , evolved from K as an open vocabulary in Forth , the 3 cell header for an ` object is simply `( Type Count refCount )` ( where ` refCount handles memory management , free on return to 0 ) . Upon that , any more complex Types can be constructed ` inheriting the entire general list manipulating vocabulary , again , evolved & greatly simplified from APL via K .

#SaaS | #venturecapital : "What's Wrong with SaaS? - An insightful piece from Avenir . Key Takeaways- (1) #Software remains a significant sector with hundreds of high-quality businesses. Within it, SaaS has suffered in recent prime years primarily due to deterioriating fundamentals, NOT a change in the valuation paradigm. The dearth of software #IPOs is due to mismatched expectations, NOT a shuttered IPO market. Today's private -high growth software companies can and probably should IPO. (2) The simplest explanation for deteriorating fundamentals is that we have passed the center of the SaaS S-curve and incremental revenue will be harder to come by going forward at the sector level. So far, SaaS companies have responded to this by spending more, leading to deteriorating sales efficiency and underperformance. What management teams have referred to as "tough macro" is likely a new normal. (3) Though growth will be harder to come by, it will still be meaningful. #AI represents a promising new #product development vector, and incumbents will generally be beneficiaries. Either way, SaaS companies have a long way to go before they are run in a financially sound way - multiples for the group could well be higher in a few years based on improving profitability and financial discipline. https://lnkd.in/gaUeVGJV

6

3 commentaires

CoderSchool (IT W21) saved $1000+/mo by switching to Lark Suite from Google Workspace, but there's even something more mindblowing about Lark...are you ready for this 🤯? There is a 🧋 Milk Tea Group Order🧋template in their default gallery. In all seriousness, while I originally switched as a cost-savings measure, I'm finding Lark Suite surprisingly delightful to use. It's fast, fluid, and unlike the Google tools, all the tools work together seamlessly, centralized around a "chat-first" philosophy. If people are interested, or even if they're not, I'll continue posting about some of the steps involved in our migration from 9+ years on Google Workspace. It wasn't that hard, although we're not through all of it yet. I'd encourage all startups to take a look - Lark is free for up to 50 users, so most small co's can replace Gmail/Notion/Slack/Sheets/Airbase/Drive for $0/mo. And you can still keep "Sign in With Google" on your old domain. Thanks to Mark Dembitz for the presentation about Lark. I was lucky to be sitting front and center wearing my bright red CoderSchool T-Shirt while you had the slides about why red is a bad choice for a brand color.

90

27 commentaires

New SREEZ website : It's online ! Minimalist design, fun logo : https://lnkd.in/eEqMk-rX A lot of new stuff to come out soon about SREEZ including demos, blogs, best practices and more. What is SREEZ again ? A platform with the required support to save countless hours to your development teams so they don't waste time deploying manually or doing infrastructure work instead of developing your next killer feature. It is inspired heavily by the platform engineering movement, an emerging trend that is currently accessible only to large companies that can dedicate many developers to the platform work. With SREEEZ you get a top notch platform and team that costs you less than a single developer but gets you the benefit of a full team of experts. Who is it for ? We're currently targeting teams between 10 and 200 developers who want to deliver faster. Build your own package by combining : - Fully managed platform that runs anywhere - Sustainable hosting on our micro-datacenters (general purpose, AI, distributed databases, S3 endpoints, etc.) - Migration services for existing projects - Consulting on DevOps practices, IT audit, development and more Want to see what it looks like ? Book a demo with Jean-Gabriel Gill-Couture : https://lnkd.in/e7Nvu6-n #platformengineering #kubernetes #devops #softwaredelivery #consulting #hosting

5

💼 #AI Job Board: ➡️ Développeur/euse en Intelligence Artificielle - Industrie & Services  https://lnkd.in/eD8kqBEf --- I post new job offer in AI everyday! Add me/follow me for consulting, implementation, engineering AI job offers https://lnkd.in/fPkM9Vy #artificialintelligence #intelligenceartificielle

1

The ultimate Shopify Liquid secret is here ! When to use “.value” when dealing with metafields (and metaobject fields). And it’s surprisingly easy, let’s dive into it ! If you need to remember one thing, always use “.value” ! An implicit output (omitting the “.value”) will return a string, making it OK only for most basic types. I’ll go into more detail below. Only exception not using “.value” is chaining a metafield filter in order get tailored markup for the value. In a nutshell, here is the first-principle ruleset for metafields : - I need the value for business logic, use “.value”. - I want to generate markup for the value, use metafield filters. - I work with references and need Shopify gIDs to communicate with APIs, implicit output. Now that everything is clear, let’s have a more comprehensive overview. At the beginning, the metafield object. We can access it in Liquid using the following syntax “assign metafield = resource.metafields.namespace.key” - “resource” can be a product, a collection, a market, etc … - “metafields” is a property of the associated resource object. - The “namespace” and “key” are set when creating the metafield definition. At this point, we have assigned a metafield object to our variable, from which we have access to the metafield Liquid object properties (see https://lnkd.in/efGjRNpS). Introducing the “value” property. Accessing it will return the metafield raw value. The format will depend on the metafield type and whether it’s a list or not. Still, this is what you want, what is used to create Liquid logic. You can also use a metafield filter on the metafield object (not on the value) to format your data (see https://lnkd.in/e_e4nVST). Similar to the “image_tag” filter, using your image URL to create image tag markup. The most common case you will encounter is using the “metafield_tag” filter when using “richtext” metafields. In Liquid, richtexts are in fact objects, similar to a tree data structure, leveraged to build the markup from it. That’s why using the “.value” property will not be useful here and we instead use the “metafield_tag” filter, providing markup for our needs ! And finally, the implicit output, extremely dependent on the metafield type. Always returns a string, making it compatible with basic data types, but don't be fooled. Any list of values will return a stringified array. References, like product references, returns Shopify global identifier of the ressource. In both cases, data we can hardly work with ! There are niche cases where we need the gID to communicate with APIs. Still, with current tools like section rendering API, there is always a better way ! It’s a wrap, hope this will help you in the future, I’ll get into more details regarding the other confusing syntax of Shopify soon. Like “.value” and “.values”; “.size”, “| size” and “.count”, let me know if you’re interested ! A great week-end to you all !

71

15 commentaires

Remember the fiasco with the French-German Interrail project? They aimed to sell a massive number of tickets but ended up leaving the data of about 245,000 registrations almost unprotected on the web. We hear this happening to SaaS companies often. For non-technical founders, it can even be crippling. The silver lining — it's avoidable! Let's talk about how you can prevent similar mistakes in your SaaS products.

8

2 commentaires

Practice makes perfect Mini blog statique réalisé avec Next.js  Next.js is an open-source web development framework based on React. Developed by Vercel, it has gained significant popularity due to its robust capabilities

2

1 commentaire

Your contribution for the evening 🌖: OpenReplay👇 Led by Mehdi Osman, OpenReplay is an elegant open-source session replay stack that lets you see what users do on your web app, helping you troubleshoot issues faster. Here’s why you should contribute to this repo: 1️⃣ OpenReplay offers an advanced developer tool suite that facilitates session replay, error tracking, and real-time user interaction analysis. With around 90 issues currently open for grabs, contributing allows you to improve how developers diagnose and resolve issues, ultimately enhancing user experience on web and mobile applications. 🖥️ 2️⃣ If you like a challenge, you are in luck! At Quira, we rank Developers by their DevRank (more on this here: https://lnkd.in/eNtrs97F). We found that the median developer working on the repo belongs to the ~97th percentile of GitHub developers. If you want to challenge yourself and contribute to a growing repo with over 8,000 stars, here's your shot! 🏀 3️⃣ Maintainers take extra care in getting back to you with an 85% reply rate and an average of 2 days to answer your queries. This means your contributions will get the attention they deserve. 🌟 You can check the GitHub page directly here: https://lnkd.in/dEM3SQh 📖

3

The relationship with Tech Leads and Engineering Managers is often unclear. Last week, I wrote that The Manager's Path by Camille Fournier missed the opportunity to clarify the relationship and the split of responsibilities between these two key figures in modern Software Engineering teams. While waiting for a second edition of the book, I put together an article aimed at clarifying an area that is often muddy and fuzzy and causes unnecessary friction. In it, I suggest a simple model that goes as follows: * The engineering manager is accountable for all technical decisions made by the team. * The Engineering Manager and Tech Lead are responsible for making these decisions. The split of responsibilities and what is being delegated to the Tech Lead should result from explicit agreements between the two parties. It should prevent the EM from giving up their part of responsibilities altogether. It will reduce the risks of having a single point of failure in the team and the manager stagnating technically. You will find the whole article in the first comment. Happy read! #EngineeringManager #TechLead #CTO #EngineeringLeadership

56

10 commentaires

🗞 More new developments from the Wikimedia Enterprise Team! 👏 🤗 We just released a new Wikipedia dataset on Hugging Face!   • Full English and French Wikipedia articles   • Structured JSON format for easy ML integration   • Includes article metadata, abstracts, infoboxes, and parsed sections   • Ideal for NLP tasks, knowledge base construction, and more   • Open access under CC BY-SA 4.0 and GFDL licenses Big news and exciting times for developers and researchers! If you want to explore our datasets you can do so here 👉 https://lnkd.in/eBtGh2M4 Need higher thresholds, interested in becoming a testing partner, or have questions? DM me to chat. Let's unlock the power of Wikipedia data and pave the way to smarter data access! 🔑 #Wikipedia #WikimediaFoundation #WikimediaEnterprise #HuggingFace #FreeAPI #StructuredContents #SnapshotAPI #KnowledgeSharing #DemocratizingKnowledge #OpenData #AI #MachineLearning #NLP #AIResearch #DeveloperTools #WikipediaData #StructuredData #KnowledgeGraph

2

Rollstack is growing faster than we can handle, and I'm calling all the exceptional Software Engineers in my network to join our incredible team! 🌟 Why hop on board? 🚀 1️⃣ 𝗦𝘁𝗲𝗹𝗹𝗮𝗿 𝗣𝗿𝗼𝗱𝘂𝗰𝘁: We simply have the best product out there, and teams just love it! 2️⃣ 𝗦𝗲𝗿𝘃𝗶𝗻𝗴 𝘁𝗵𝗲 𝗯𝗲𝘀𝘁 𝗖𝗼𝗺𝗽𝗮𝗻𝗶𝗲𝘀: We serve the most innovative companies including monday.com, 1Password, and Monzo Bank. Rollstack gives teams a real edge in their industry and market. 3️⃣ 𝗘𝘅𝗽𝗹𝗼𝘀𝗶𝘃𝗲 𝗚𝗿𝗼𝘄𝘁𝗵: We’re growing insanely fast and profitably (not your typical cash-burning startup!). Backed by the best in the business including Y Combinator, the founder of Indeed, the CEO of AngelList, and former leaders from Microsoft, BlackRock, Google, Pinterest. 4️⃣ 𝗥𝗲𝗺𝗼𝘁𝗲-𝗙𝗶𝗿𝘀𝘁 𝗖𝘂𝗹𝘁𝘂𝗿𝗲: Our company culture is remote-first and centered around customer devotion, accountability, excellence, and innovation. Link to apply in the comments.

103

4 commentaires

Curious to know how I built few animations on 13g.fr? I wrote a case study on Codrops !! 👀 👇 https://lnkd.in/e6sh2fcS hashtag #webdesign #webdevelopment #frontend

101

5 commentaires