So what's the smoothest way these days to integrate localisation repositories into your git repo?

As a background: our localisation needs to live in a separate git repo that is monitored and also updated with new translations by pootle (a translation tool) but we also want to be able to pull out the generated PO files as well as push local updates (and new texts) from within the containing project repo the localisations belong to. So merges / rebates are kinda required.

Git submodules are the worst case here as you can't really commit / push local updates to the translations back to the localisation repo without making a separate checkout, doing your changes there, then pushing to your remote and finally updating the reference for your local submodule and pulling again.

Git subtrees sounded like a good idea but they way they're implemented makes them nasty to use as well.. they tend to break if you work with pull --rebase in the containing repo and merge conflicts in the sub tree can't be resolved with a sub tree-rebase either.

In the past I used to have the localisation as a full git checkout in a sub directory of the containing project and maintained it using a few CMake scripts but I had hoped there's be something smoother by now.

#git #submodules #subtree #localisation #i18 #workflows #question #SofwareDevelopment #boostswelcome

C++ Core Guidelines

The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++

I kind of feel like much of the LLM use in #sofwareDevelopment hype is similar to the LOC metrics of yore.

'It's so easy to generate code with this and also tests!' Well, yes but I feel that writing the code is a quite small part of the job anyway.

Reading the code and understanding it is more common and there's the whole, well, software development thing around it. What code we need to write? What does this piece do and how to modify it?

If you want to learn something about how to not create software, have a read of paragraph 251 in https://www.judiciary.uk/wp-content/uploads/2022/07/bates-v-post-office-appendix-1-1.pdf

This is a court document from the Post Office scandal's litigation, in which post masters were held liable for accounting losses due to (very) broken software (more on https://en.wikipedia.org/wiki/British_Post_Office_scandal).

This whole document is a fascinating read of failure in the software, and the criminal cover-up that followed.

#PostOfficeScandal #SofwareDevelopment

Top Custom Software Development Company

Our Top Custom Software development Company accelerates workflows, boosts revenues, and optimizes business operations from concept to code and development to deployment.

Contact Us:​​-
➖➖➖➖➖➖➖➖➖➖➖
Website: https://mtouchlabs.com/custom-software-development-company
Email: [email protected]
Phone: 093906 83154
Whatsapp: https://wa.me/+09390683154

#customsoftwaredevelopmentcompany #sofwaredevelopment #customsoftwarelopmentservices #mobileappdevelopmentcompany #mobileapplication

Custom Software Development Company Hyderabad - mTouch Labs

We are a leading Custom Software Application Developers specialized in crafting innovative and user-centric software solutions to elevate your digital presence.

Whelp #VSCode just made the choice for me at work today. It's totally hit the skids and is now shitting the bed in new and creative ways every time I try to use it. Guess my time with #NeoVim or #HelixEditor starts asap. Bit scary jumping into modal editing + pure TUI + extensible text editor at the same time as trying to be productive.

Any recommended learning resources vimheads?

#SofwareDevelopment #IDE #FOSS #OSS

Three books I highly recommend for beginning-to-intermediate software engineers to read, and for senior devs to keep on their shelves for reference.

There's code that works, and then there's elegant code. It's a lifelong learning process to produce more of the latter.

(Titles in the image description.)

#software #softwareEngineering #sofwareDevelopment

A random thought I had tonight after my day at work. In my experience, focusing at the macro level before the micro helps while designing #SofwareDevelopment solutions to complex problems. Starting with the details in the micro makes it hard to pull your head up to the higher level. Plus, I find that #IntegrationTesting and #TDD are a natural fit at the higher macro level. This idea scales for all sizes of problems. Break problems up into parts first and then solve the lower level details.

Finally migrated to my own server so it's time for #introduction

Hey. Name is Marcin Sawicki but friends call me Wicek. I'm proud "dad" of one mischevious cat named Sissi (We'll probably post under #MastoCats a lot)

For a living I do #SofwareDevelopment. Currently in #Python but as a #Coder I worked a bit with #cplusplus and #PHP too. I love #Linux, especially #ArchLinux

Besides that, I'm interested in religious studies and plan it to be my second degree. I play chess a bit

Making my #introduction as part of the #TwitterMigration. I live in rural Northern California and work in BizDev for #RenewableEnergy, formerly in #SofwareDevelopment. I have a master’s degree in #Library and #InformationScience #MLIS. I love #reading #books of all kinds and dabble in #writing. I also devote a lot of time to #gardening #baking and #baseball. I have three bossy #cats (now 4!) and one very opinionated #dog and love #wildlife and animals of all kinds.