We are pleased to announce that our Software Engineer, Jonathan Müller, will be attending the C++ standardization committee meeting in St. Louis this June. This meeting marks the final opportunity to make significant changes before the feature freeze for C++26. The committee will focus on refining reflection, pattern matching, contracts, and senders/receivers. We will keep you informed with a detailed report on the discussions and decisions made during the meeting, particularly regarding the final refinements of these critical features. Stay tuned for updates on our Dev Blog (https://lnkd.in/eF67fybZ).
think-cell Software’s Post
More Relevant Posts
-
SW developer, coach, trainer, architect, consultant and other roles needed for a project's success.
Another video - this time on the more theoretical side of things. Do you know the Cynefin model and how it influences our software development? https://lnkd.in/erArRNuQ
-
[Armv8-Exception] Why we need to learn Exception? Hello friend, This video explains the reason why system software engineers should learn Exception; The first reason is to level up troubleshooting skills in real project. You can follow me Austin Kim if this material is helpful to you. BR, Austin Kim
-
New blog post today! On the topics of Software Engineering, Technical Debt and sin-eating! https://lnkd.in/dD5s_xpY
-
Beyond mere coding, ensuring reliability demands a holistic approach encompassing software, hardware, networks, and human factors. Join Dylan Beattie for an exploration of systems engineering, its historical context, and strategies for building dependable systems, crucial in a landscape where software glitches can have far-reaching consequences. https://lnkd.in/dDvu7hhx
-
-
Software Compliance Verification Engineer (Senior Chief) @ 𝗔𝗦𝗘𝗟𝗦𝗔𝗡 {CSQE, CSFE} - Yapay Zeka Terbiyecisi
𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗣𝗿𝗶𝗻𝗰𝗶𝗽𝗹𝗲𝘀 The article provides the top-10 principles of all times based on a survey. Another top-10 list with novel principles covers more recent evolution in software engineering. https://lnkd.in/dtY9h-qW Christof Ebert
-
-
Technical Architect | Senior Tech Lead | Senior Application Consultant | Life Sciences | SAFe Architect | SAFe Agilist | SAFe POPM
From the blog "We see no realistic path for an evolution of C++ into a language with rigorous memory safety guarantees that include temporal safety. A large-scale rewrite of all existing C++ code into a different, memory-safe language appears very difficult and will likely remain impractical. " What is a clean way out?
-
Software Engineer @ Amazon | Author of "Build Tech Career" - a newsletter for practical, real-world insights from 10+ years as an engineer
The real battle is picking up the right trade-offs. That's where senior devs bring in their experience because to be able to pick the right trade-offs you need - 1. A deep understanding of the underlying problem 2. A deep understanding of how product evolves in your space 3. What are the strengths and weaknesses of the team 4. How much money can be allocated to the project
The 1st law of Software Engineering: ”There is always a trade-off”. Corollary: every technical question can be answered with ”it depends”. What other ”laws” have you encountered? 😁 #softwareengineering
-
☕️ Here's an entry from the Small Batches library: "Benefits of Separation of Concerns". From Modern Software Engineering (2021): Separation of concerns provides me with a mechanism to, very early in the process, detect problems that will, if I don't react to them, lead to reduced modularity and poor cohesion in my designs. Comment below on this applies to your daily work.
-
The 1st law of Software Engineering: ”There is always a trade-off”. Corollary: every technical question can be answered with ”it depends”. What other ”laws” have you encountered? 😁 #softwareengineering
Tech Enthusiast | Software Engineer | AI | Machine Learning | ALX Graduate | ServiceNow | Problem Solving | Graphic Designer |
3moExciting!