Lloyds digital’s Post

Cool little milestone: 2999 questions have been asked about AnyLogic over at Stackoverflow 😎 ( https://lnkd.in/dtv2-732 ) Over the past few years, SOF has established itself as one of the homes for the AnyLogic community, primarily for technical Q&A community support (beyond the fantastic AnyLogic support itself and the LinkedIn forum). Unfortunately, SOF recently hid the "top users" section but it was a select few individuals who tirelessly helped beginners and advanced users, notably Felipe H., Jaco-Ben Vosloo, Stuart Rossiter, Emile Zankoul, Yashar Ahmadov, Amy Greer and even AnyLogic's Gregory Monakhov (and many more) 💐 So who will be asking the 3000's question? PS: If you are confused by the various AnyLogic community places to interact, see this explanation: https://lnkd.in/d-hwdcm6 PPS: If you still want to see the "top users", it is still accessible via https://lnkd.in/dA7DEVVe

New feature of React-19 - Action and Hooks "Actions enabling smooth data transfer between clients and servers. While Hooks giving you greater flexibility during the development and updating of your code." https://lnkd.in/dgh-KkYN

In my latest blog post, I dive into the world of edge computing and explore how deploying simple apps directly on the edge has become simple, cost-efficient, and developer-friendly with solutions like Cloudflare Pages. I hope this article inspires other developers to try our edge computing capabilities. It does look like we'll use a combination of JAMstack architectures and edge computing/delivery more and more in the future. Check it out 👉 https://lnkd.in/ddEFrHcJ #EdgeComputing #WebDevelopment #TechTrends #CDN #Cloudflare

🕵️♂️🎭 Server-side tracking can seamlessly blend in with your site's backend, making it nearly invisible to ad blockers. This means more accurate data and insights without interruptions. Stealth mode: activated! #ServerSideTracking #TechFun #StealthMode #AdBlockerProof #ServerSideTracking #TechFun #FastWeb #DigitalInnovation #FunFactFriday

100xDevs Web-Dev Cohort 3.0 🔥📈 𝗪𝗲𝗲𝗸 5 : HTTP Server and Express This week, we dove into the depths of Express Server with Harkirat Singh Here are the 𝗞𝗲𝘆 𝗧𝗮𝗸𝗲𝗮𝘄𝗮𝘆𝘀 ✍🏻: ⎺⎺⎺⎺⎺⎺⎺⎺⎺⎺⎺⎺⎺⎺⎺⎺⎺⎺⎺⎺⎺⎺⎺⎺⎺⎺ ・HTTP Server ・Express JS ・Routes, Body, Header and Query Params ・Middleware's and Cors ・Postman Harkirat Singh's expert guidance made this week truly enriching. 🙌 The continuous support from the 100xDevs community has been crucial to my progress. #100xDevs #opentoconnect #Web #webdev #100daysofcoding

Thank you to Dev.to for featuring my thoughts on "Network Observability: Beyond Metrics and Logs" in their blog roundup this week. https://lnkd.in/gYHPq-6M

Let's unpack some key insights from StackOverflow's 2024 Developer Survey and see how they can help you make better decisions about your Tech strategy.

As a person who has, and is, actively still doing ASM, OS level C, application level programs in multiple languages, and infra/SRE work, I am willing to take the Pepsi challenge on this question.. Though I am going to try to avoid speculating as to why the question is "primed" with such an obvious bias. Ref: https://lnkd.in/gRjuJDNN IMHO, at the core levels of CS, there is little to no difference between Infra/SRE work and designing/writing a Kernel, or firmware for a Micro-controller, or anything really. All of the same CS concepts are found equally in all of these domains. Concurrency, recovery, locking/exclusion, message passing, shared memory, caching (and cache invalidation), interrupts/events, etc. I have often told people that I consider all of these domains to be the same/similar as a developer is always "orchestrating moving parts", and the same age-old solutions/paradigms continue to be applied; the only real difference becomes the matter of scale. Though I would like to address a couple of fallacies in the wording of the question. SRE work: - Is to make an application 100% available, even in the face of loss of servers, networks, or even entire data centers. - Is often spent developing new source code and new solutions, either via developing new "custom fit services", or integrating with existing services that may or may not be documented; or have undocumented behavior that they are relying on. Just like any other software work. - Does not have "all the source code". Odds are in favour that SREs are working with maintaining large swaths of "brown field": https://lnkd.in/g8f6EDeF) Sections of the infrastructure may be "working" but the people who developed it are long gone, often because they moved on when they were inhibited from reworking/refactoring the software. In this way, SRE work is often worse than normal OpenSource work (integrating with horrible 3rd party hardware aside). In comparison, once an infra solution is "in place" there is little-to-no business incentive to let the dev team use their newly-acquired-IP to revisit their solution and "do it right this time". To that end, much of the internet infrastructure is, again .. in-my-experience .. a collection of rapidly produced proof-of-concepts, with no documentation and no one still around to answer questions. This often means that these "brown field" portion of the infrastructure end up with a lot of time spent writing abstraction layers and a lot of time spent in pointless upkeep. In many cases it isn't even possible to move this stuff to a new OS image or hardware emulation, resulting in long-term increased costs of just keeping the junk running. - Is also support work. They support these "live deployed" solutions, both supporting developers running on and interacting with the infrastructure, as well as being paged anytime something "fails". IMHO, they really are mostly the same job with different tools.

Join Tracy Lee, Adam Rackis, and Tim Neutkens from NextJs to learn how TurboPack is revolutionizing the bundling process, slashing build times, and enhancing parallelism and caching. Plus a bonus treat: get some details on what's coming up in #NextJS15. Link down below!

What will happen this year in the world of open source? Read predictions 🔮 from OpenLogic and Zend Senior Product Manager Matthew Weier O'Phinney >> https://ter.li/pfwgqu #opensourcetrends #opensourcesoftware