Programming

Hi programmers,

I work from two computers: a desktop and laptop. I often interrupt my work on one computer and continue on the other, where I don't have access to uncommitted progress on the first computer. Frustrating!

Potential solution: using git to auto save progress.

I'm posting this to get feedback. Maybe I'm missing something and this is over complicated?

Here is how it could work:

Creating and managing the separate branch

Alias git commands (such as git checkout), such that I am always on a branch called "[branch]-autosave" where [branch] is the branch I intend to be on, and the autosave branch always branches from it. If the branch doesn't exist, it is always created.

handling commits

Whenever I commit, the auto save branch would be squashed and merged with the underlying branch.

autosave functionality

I use neovim as my editor, but this could work for other editors.

I will write an editor hook that will always pull the latest from the autosave branch before opening a file.

Another hook will always commit and push to origin upon the file being saved from the editor.

This way, when I get on any of my devices, it will sync the changes pushed from the other device automatically.

Please share your thoughts.

I'm trying to see how active a project is, but dependabot spam makes it annoying to find actual commits and to know if those commits are relevant.

There's no need for me to know chai was updated from 5.1.1 to 5.1.2, I want to see what were the most recent actual features implemented.

The title. I have read many technical books (mostly compilation, programming languages & automata) , blogs and whatnot, and recently borrowed the above mentioned book Volume4 (combinatorial problems) from a local library. Just to give a try since Knuth is such a respected person in computer science.

It is by far the most frustrating and maddening book i ever laid my eyes upon. The author doesn't make the slightest effort to explain why something is useful, changes examples before explaining why previous example is interesting or how it shows why X is useful. On page 8, he says that "Graeco Latin squares allowed to François Cretté de Palluel to do with 16 sheeps, what otherwise would require 64 sheeps". How & why ?? No fucking clue. I know i am not the smartest person on earth, but i would love a little hand holding here, you know to explain a concept he introduced 2 pages previously, and gave 3 random anecdotes about.

The writing style is a complete opposite of what I (and I believe, what are most people ) am expecting. If you know something, it won't be useful, and you don't know something : don't count on the book for explanation. I had the physical urge to slap Knuth. It's absolutely maddening.

He then goes on his little hobby to gather 5 letter-English-words, and gives some fancy looking graphs with fancy names (3 cubes, Petterson graph, Chvatal graph). For all what i know, it could be graphs called 42 and graph Blabla. Again no clue how it's useful, nor why it's interesting. He introduces some definitions and theorems.

I am on page 26 (thr book is thicker than a bible) i think i am done. This book will not make you a better programmer, i have no idea who and for what reason could possibly find it useful?

If you think i am overreacting and should continue reading, please tell me so, but i don't expect it to get better

Our workflows and productivity metrics regularly ask knowledge workers for things that do not make good knowledge work.

Bloggers on reddit lament how much “meta-work” and “not-work” exists in tech. They kvetch about the conversations and the waiting. They consider the principal engineer’s calendar, packed with meetings, quod erat demonstratum that those roles are “easy” and “airware.” They insist that, if they could manage to not get caught, they could keep several such positions simultaneously and never under-deliver on any of them. None of these jobs, they claim, ask them for all that much code.

I'm working on a python program, and i need to sync the results to an ipad as a todo list (with checkboxes)

I had been using google keep, and manually copying /pasting the data over from my cli based app. I will be out of the country for 2 weeks, so im updating my software to no longer being cli, and ideally syncing the final list to google keep or something similar, since someone else will be running the software. You know how normies get when they see a terminal window..

tried this googlekeepapi thing i found online, but the authentication was very complicated and i couldn't get it to work. There is no specific reason we need to use google keep, was just the first thing that came to mind when we set this system up, and it works well and is cloud based.

Do yall know of any service where i can programmatically generate checkbox lists, and sync them over the web?

I should note i do not have a server available to self host. could potentially spin something up locally with a raspberry pi, but would prefer not to have another potential point of failure.

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.