Many of us will make that shift effectively, sure. I think the problem is that to really be a good architect, you need 10+ years of actually doing things to understand what should/should not be built, and the industry is rapidly removing the jobs that let people acquire that experience.
Yeah I would recommend avoiding LLM's while learning to anyone new to programming, because I have experience with meticulously rewriting code until I was happy with it's performance, conciseness and readability I can see when an LLM is writing something that could be improved and just gently nudge it in that direction and it resolves the issue.
I was working for one production company making products out of concrete, and they had this SCADA system. They had 5 factories and 5 versions of the same software.
This software was made by one company, but as factories were built in different times, software was evolving as well, so when I joined the company there were 5 factories with different code bases, that were doing basically the same thing.
Oldest software was written in VB6, newer in .NET 1.1.
The problem was that making changes on all factories required making changes in code in 5 codebases, and it was impossible to merge them into one because of subtle differences how the production lines were working. Also it was impossible to run this software locally, so only tests you could do on live production environment. Imagine testing your software, there is a bug, and you just wasted 2 tones of concrete...
My solution for this problem was making a checklist of all the things that need to be changed and checked before changing, codebase by codebase. Also keeping the changes in SVN helped a lot for implementation reference. Good commit messages and comments in code were essential not to drown in this mess.
In the end, I hired an employee, taught him the ropes and "sold him" to this company. He works there till now and does exactly the same thing (8 years and counting) ;)
I have 2 rehearsal rooms for musicians, with good acoustics and some basic music equipment. There are 10 bands sharing the rooms and paying monthly giving me 500$+ with ease.
I will do more as the market for such places in my city is not saturated yet.
Thank you, it is much needed, right now the most reliable way of generating PDF's I used not so long time ago is
- create DOCX with content and some template variable strings, like {{}}
- unpack document and get into text, replace text
- use DOCX->PDF linux tool to generate document.
Latex seems way better than either to me (but then, I know Latex). Certainly Latex makes it much easier to get consistency and precision. For your use-case, generate Latex code from a template using Python or whatever, substituting in what you need, then compile the Latex into a PDF. If you need graphical elements or precise layout control, use the Latex package TikZ.
If what you need is very simple (e.g. no word wrapping, same number of variable strings in the same positions), even manipulating the code of a template PDF directly is not too hard. This library would help with that.
And a variety of intermediate or input text formats, where you can pick your preferred poison whether for book publishing, research papers, math papers, technical documentation, slides, etc.
yep, I had two Dells, one XPS 15 from 2019 and some cheap Vostro, and both had problems with sleep state. The support is great, but I couldn't get Ubuntu to run without issues, and it sucked a lot.
Older Latitude were great for dev work, and I still use my 7450.
Sounds really like long way.
Yes it'd be great to be able to have some "home brew" manufacturing process that could be useful.
Then making CPU could switch to distributed model.
But I just read today of silicon wafer shortages, so story goes deeper...
