I find too verbose comments less annoying than no comments.
Try to describe the bigger picture. Good comments allow understanding the current portion of the code without reading other code.
Also add comments later if you find yourself having to read other code to understand the code you’re currently looking at.
Comments are also a good place to write out abrevations/acronyms.
Never optimize for sourcecode size.
check carefully what you signed. If you didn’t sign anything saying otherwise, there’s nothing to prevent you from doing it.
If there’s something, you could still work around it (e.g. remove company secrets).
If the resulting product is provable better, then it’s objectively not the same thing you did for your boss.
After checking all of this, your local FSF might give you free legal advice to get going (keep all notes/correspondence secure for later if anything comes up. It proves you tried to act responsibly).
you could check textual, it’s a TUI framework that yields quick results.
you don’t need to know electrical engineering to design an airplane control panel
lol, of course you do. and A LOT more. Hence it’s usually done by a team of experts. Pilots, eengineers, manufacturing, regulation/standards, safety,…
UX is just one of many parts of the expertise needed. same in software.
What you’re claiming is wishful thinking that has nothing to do with real world workflows. I also don’t know a single UI designer having the troubles you are pointing out.
The majority of designers (not all) I have worked with have been very shy about technical work, so having no clear “non-technical” contribution pathway is a deterent.
That’s the difference between designer and UI Designer. Just because you can draw an UI with your favourite tool, doesn’t make you an UI design expert.
there is never even an opportunity to submit design work.
nowadays, design work is code (or at least markup). Like .qml or .glade or even html/css.
is asking people who don’t typically code to do so
encounter a problem and learning a new tool to solve it, is a pretty standard situation in IT. Designers have varying capabilities in that domain. While a print designer might have trouble learning a new software, a MMI-Architect or UI Designer should commonly be able to learn a new UI framework (designer software).
Generally, if you like to contribute to any project (not limited to software), you can’t expect the project to adapt to your toolset.
But often it’s enough to share an idea for it to get adapted.
there’s https://bountysource.com/ or https://www.vamp.sh/
Bound to specific problems and limited to projects willing to pay money.
use open source software. whenever you see potential to improve, open an issue with detailed explaination.
try to solve the problem yourself. send pull requests. adapt them according to instructions by devs. when they’re good, the will get merged.
if you use the software a lot, contribute whenever you think something is needed.
We live in the real world. If you don’t submit the government forms how they want you to, they shrug and fine the shit out of you.
Then you just don’t know the law. There is no legislation that enforces Acrobat in any civilized country without alternative.
Quite the opposite: Send macroridden documents to any decently secure infrastructure and you get a big fat warning in the subject if it’s not filtered entirely. Officials LOVE to do that extra call ensuring that this document is really from you before opening it and no phishing attempt…not.
Source: working >25 years in IT, >15 years for government IT
EDIT: we got some real Adobe Acrobat Fanboy here, eh? ;-)
At least I hope you’re not.
Of course I do and I expect my employees to report such incidents to IT. Such documents are common attack vectors.
In my experience, customers are not aware of failing interoperability or possible security threats and often grateful for such hints.
There’s a reason why libreoffice (and I guess other office suits aswell), evince or antivirus show a big, fat warning when opening such documents. Surely there are cases were macros are useful or necessary, but if they have to leave the company, you’re doing it wrong.
This talk might be interesting for you: https://www.youtube.com/watch?v=4F2xMw3987I
I only know thumb = motion/current but now since you say, it’s clear: people used x/y for 2D logically but the 2D plane used to be paper. which is parallel to the earth surface (usually). Computer screens are perpendicular so Y points up, not away from you.
So this makes sense with paper, TIL. With computers, Z traditionally means depth.
Formulars, such as calculating a sum based on the preceding fields.
You’re doing it wrong. PDF with embedded javascript is a nightmare and it still doesn’t make PDF equal to excel.
Better generate your documents with your favourite HTML templating engine from your DB and convert them to simple PDF in the last step.
LibreOffice notoriously renders Microsoft Office documents incorrectly in my experience.
Only had that experience with badly designed, macro ridden documents which there’s no excuse for anyway nowadays. I use a lot of print templates (various label printers) and it works flawlessly.
Also, exporting a non MS file format usually imports fine in LibreOffice, even with complex documents.
The ability to quickly edit PDF makes it the office suite of my choice.
Textual is the new kid in town. With CSS, mouse support and a growing number of widgets, it’s THE unique framework for UIs in the terminal with python.
Consequence:
Software can only be good, when enough people WANT to work on it and with it along the complete life-cycle. There’s a critical amount of developers/contributors/testers and (feedback providing) users.
Hence a lot of critical consumer stuff is based on popular opensource.
Also, we’re entering an aera where the difference between hardware/firmware/software gets increasingly blurred. So all of this applies to more and more hardware, too.