10,141 karma · joined December 21, 2015
Socials: - dev@famic.de
---
> In Germany, however, such images—US soldiers at food banks—are unlikely to be seen. The list of supply tips quickly disappeared from the website. Why food banks were mentioned there in the first place remained unclear at first.
> The more than 30,000 US soldiers in Germany are unlikely to have encountered any major financial problems anyway – according to the IMCOM spokesperson, they received their October salaries as normal despite the shutdown.
> This is in contrast to the approximately 11,000 civilian employees of the US Army in Germany. The US has not released their pay, which is processed by the German “Wage Office for Foreign Armed Forces” in Rhineland-Palatinate. For the time being, the [German] federal government has stepped in and paid the logisticians, cooks, and firefighters their October salaries totaling around 43 million euros, as a spokeswoman for the [German] Federal Ministry of Finance announced on Thursday in response to a query from the SZ.
[0]: https://www.sueddeutsche.de/bayern/deutschland-us-army-solda...
> Modern AI has thrown a wrench into Brooks’ theory, as it actually does reduce essential complexity. You can hand AI an incomplete or contradictory specification, and the AI will fill in the gaps by cribbing from similar specifications.
The essential part is still not adequately covered by Generative AI, and probably never will be. Here is my detailed write-up about it: https://smartmic.bearblog.dev/no-ai-silver-bullet/
> Is the use of a compatible licence a "re-licensing"?
> No. The original code will stay covered by the EUPL. It is the combined work only that could be, when needed, covered by the compatible licence. In this framework, a combined work results from merging functional codes covered by two (or more) different licenses. The simple action of "linking" does not merge functional codes and in such case the various linked parts will keep their primary licences. This is resulting from the European law, since Directive 2009/24/EC states that interfaces (APIs, data structures etc.) needed for making two programs interoperable can be freely reproduced/used in the various source codes, as an exception to strict copyright rules.
> To be legitimate, the use of the compatibility clause must result from necessity: using it for the sole purpose of relicensing a copy of the original work would be a copyright infringement.
Some people might say that writing in XML is annoying, but it isn't if you have a decent XML editor. In my case, it is Emacs nXML mode. Customisation is possible with DITA-OT [1] and plugins, and yes, it is also based on XSLT. Overall, I think DITA is an industry-proven XML powerhouse. It may be boring, but it has huge potential for anyone with advanced documentation requirements.
[0] https://dita-lang.org/dita/archspec/base/introduction-to-dit...
In any case, aberrations such as the excessive use of emojis and exaggeration are becoming increasingly common, which is yet another reason for me to distance myself from GitHub. For me, a README that more closely follows the conventions and minimalism of a classic man page is a sign of quality, and it could perhaps even be rendered in plain text to achieve a high signal-to-noise ratio.
If the latter, I wonder how you can manage another programming language alongside Odin — anyway, thank you and great respect for both!
However, I felt that writing anything not closely related to solving mathematical matrix problems made no sense to me. Unfortunately, APL is too niche; I don't know anyone in my industry with whom I could share the tools. Nevertheless, it was a valuable learning experience.
For it to be worth spending more time and effort on, I would need a closed system thermodynamic calculation. The technical term for this is a "heat balance diagram". This is the first thing any technical consultant would request.