Programming

Hi friends, as promised, I'm back with my second post. I'll be hanging around in the comments for any questions!

In this post, I take a look at a typical deployment process, how long each part of it takes, and then I present a simple alternative that I use which is much faster and perfect for hobbit software.

Hello everyone! 🎉

I’ve created an RSS Feed Bot that automates sharing news in Lemmy and Fediverse channels, helping to keep Fediverse users better informed. The bot is written in Python3 and can easily run via Docker Compose.

Hope you find it useful! 🚀

#Lemmy #Fediverse #RSS #Python #Docker #Automation #OpenSource

Sharing some lessons I learned from 10 years/millions of users in production. I’ll be in the comments if anyone has any questions!

A new proposal for C/C++ to force bytes to be 8 bits wide

I just finished reading this book and decided to share my experience with it.

About the Book

Continuous Architecture in Practice is a sequel to Continuous Architecture both written by Murat Erder, Pierre Pureur, and Eion Woods. The authors attempt to address feedback from their 1st book by navigating the reader through the Trade Financs eXchange (TFX) case study.

The book starts with a brief introduction to the core concepts of Continuous Architecture, including its 6 principles, as well as its essential activities:

1. Focus on quality attributes
2. Drive architectural decisions
3. Know your technical debt
4. Implement feedback loops

From then on the book switches focus to common architectural concerns:

1. Data
2. Security
3. Scalability
4. Performance
5. Resilience
6. Emerging Technologies

Each concern is tackled in a separate chapter that features an introductory quote, a definition along with some historical context, a list of issues an someone should keep in mind when architecting for that concern, a list of tactics, and a further reading section.

My Opinion

Overall, I liked reading the book, it gave me a lot of inspiration and a desire to learn more about particular topics. The book assumes a certain level of familiarity with software engineering which helps it focus on general concerns and avoid implemention specific details.

I particularly liked the Emerging Technlogies chapter as it offers a healthy view on AI, ML, and shared ledgers. It helps remove the fairy dust that's blinding our industry, and instead focuses on meaningful changes that actually provide value to a product.

Also, as someone with experience in software security I appreciated the focus on shifting left security concerns.

Who Should Read This

In my opinion, every software engineer can benefit from reading this at some point in their career. However, I wouldn't recommend it to a junior, if you are not already familiar with the topics covered in the book it could be intemediating.

PS I am not affiliated with the book or its authors in any way. I am just a person that read a book they liked wanted to share my experience.

cross-posted from: https://lemmy.ml/post/21458338

The GNU Compiler Collection (GCC) support for the C23 programming language standard is now considered "essentially feature-complete" with GCC 15. As such they are preparing to enable the C23 language version (using the GNU23 dialect) by default for the C language version of GCC when not otherwise specified.

Preparations are now underway to set the default C language version of GCC to GNU23 as the GNU dialect of C23. Or in other words, implying -std=gnu23 when no other C standard is specified.

The latest update to the TIOBE Index reveals notable shifts in the world of software development. While traditional programming languages remain popular, many developers are seeking out technologies that can make sense of the vast amounts of modern digital data. Legacy languages like C, COBOL, Fortran, and Assembly still have their place, but they no longer take center stage.

I only recently learned about Turtle but it seems like a fun way to represent data. I'm curious to learn more & mess around with it or similar formats for representing the meaning of English text. Anyone have any suggestions for projects, libraries, etc to look into?

https://positive-intentions.com/blog/qr-codes-as-a%20data-channel

QR Codes as a Data Channel

the demo in the blog article is a bit cluncky. here is a better link for it: https://chat.positive-intentions.com/#/qr

cross-posted from: https://lemmy.ml/post/21365139

Buny

Today, we’re thrilled to announce Deno 2, which includes:

• Backwards compatibility with Node.js and npm, allowing you to run existing Node applications seamlessly
• Native support for package.json and node_modules
• Package management with new deno install, deno add, and deno remove commands
• A stabilized standard library
• Support for private npm registries
• Workspaces and monorepo support
• Long Term Support (LTS) releases
• JSR: a modern registry for sharing JavaScript libraries across runtimes

We are also continually improving many existing Deno features:

• deno fmt can now format HTML, CSS, and YAML
• deno lint now has Node specific rules and quick fixes
• deno test now supports running tests written using node:test
• deno task can now run package.json scripts
• deno doc’s HTML output has improved design and better search
• deno compile now supports code signing and icons on Windows
• deno serve can run HTTP servers across multiple cores, in parallel
• deno init can scaffold now scaffold libraries or servers
• deno jupyter now supports outputting images, graphs, and HTML
• deno bench supports critical sections for more precise measurements
• deno coverage can now output reports in HTML

Deno is a single binary for the TypeScript and JavaScript ecosystems. Deno is secure by default (installing npm libs do not automatically have full system perms/access).

The new standard library stabilizes a vetted collection of safe binaries instead of having to search for and install random libraries for basic or common use cases with [or without] own security assessments.

Deno compile compiles the TS/JS project into a single binary.

The backwards compatibility to npm and npm/js frameworks enables deno usage in existing projects and with existing libs with the benefits of deno and a path to incremental migration.

The announcement video is worth watching. The intro is great.

Every second Tuesday of October Ada Lovelace Day is celebrated - to commemorate the famous English mathematician of the XIX century, and the first programmer in history.

To mark this occasion, we rounded up a party of games that are not only fun to play, but can teach you to think like a true engineer and feel like a tech wizard!

Welcome to Ada Lovelace Day Sale. Hello, world!

ends 14th (tomorrow)

cross-posted from: https://lemmy.today/post/17580707

Hi,

My question certainly stems from the imposter syndrome that I am living right now for no good reason, but when looking to resolve some issues for embedded C problems, I come across a lot of post from people that have a deep understanding of the language and how a mcu works at machine code level.

When I read these posts, I do understand what the author is saying, but it really makes me feel like I should know more about what's happening under the hood.

So my question is this : how do you rate yourself in your most used language? Do you understand the subtilities and the nuance of your language?

I know this doesn't necessarily makes me a bad firmware dev, but damn does it makes me feel like it when I read these posts.

I get that this is a subjective question without any good responses, but I'd be interested in hearing about different experiences in the hope of reducing my imposter syndrome.

Thanks