263 karma · joined October 27, 2021
Is there a way to add our own internal part numbers corresponding to manufacture's part number?
Can individual wires have different wire lengths?
Are there any features if when used won't render properly in wireviz?
If you want to manage passwords amongst family members, it's easier to set them up with one of the cloud services compared to Keepass. You also get some level of customer support, and don't have to worry as much about when your password breaks.
I personally have set up KeePass, made sure it's backed up regularly, and even set up a WEBDAV server to access it remotely. It works great for me, but I know how everything is set up. Strongbox for mobile access is the main reason I can actually use this, and this is a paid application that not everyone is willing to pay for. Experience-wise, other mobile applications for KeePass have not compared, and I have no idea how apps for Android compare, since I set up everyone with iOS devices. Sometimes, the connection to the server gets disrupted, and I have to reconnect. Not everyone wants to do this, and can have less confidence in the other supporting infrastructure.
As much as attack vectors exist, the biggest risk is you losing access to your own passwords (there's been enough lost crypto wallets you can read about on the internet). Compared to that, a cloud based service is better for a large group of people.
https://evoluent.com/products/vm4rw/
My wrist would ached so much when working at a computer until I started using it. Then got a PERIBOARD-409 keyboard (https://www.amazon.com/Perixx-PERIBOARD-409U-Mini-Keyboard-1...) that would allow me to keep the mouse closer to the keyboard.
https://thamara.dev/posts/code-annotation-a-vscode-extension...
In separate document, we put the application screens, and navigation between screens only. We try to detail out all possible states of the application, elaborating them in writing in the file.
Finally, we have one more page showing variations of the interface to illustrate all conventions.
Biggest benefit is that all design assets can be exported in SVG format and used in actual application so the app is as close to the Figma as well.
Once you have working prototypes, I strongly suggest including videos of the actual implementation for reference and accommodations for limits of the tech stack used, because it may not match perfectly with the Figma.
For more complex design systems, you may want to look at design kits by larger companies. Examples below: * https://www.figma.com/community/file/1035203688168086460/Mat... * https://material.io/blog/material-3-figma-design-kit * https://www.figma.com/community/file/1159947337437047524 * https://www.figma.com/community/file/1248375255495415511/App...
Techalter did a good job describing the fate of a lot of Philips different businesses and product lines.
When things deviate from a set of requirements, we can review and adjust the requirements accordingly so our expectations in working together can stay in line. We don't have a luxury to constantly keep changing things after releasing the software because a we work in a more regulated environment where changes will need to be reverified and validated before release, not just by ourselves, but by our customers. In the projects, we are heavily involved in ensuring a good user experience and integration testing of the software to ensure it meets our needs and solves the business problems we have.
I think it should be used when there is more than one company involved in developing an application between the companies at least, and should be avoided when exploring different design ideas and gathering requirements and scoping out the project. In any project, I strongly advocate towards doing whatever it takes to expose problems and areas of uncertainty that should be scoped out as soon as possible. It's a lot more expensive to build a solution around an existing solution than to incorporate it as part of the solution from the start.
https://www.nytimes.com/2022/08/24/podcasts/the-daily/workpl...
Staroffice which became OpenOffice and Then Libreoffice would be another
AutoCAD is 40 years old
If I'm approaching the problem first and not the solution, I try to classify if the problem is technical or organizational. If it's technical, I try to identify each of the barriers, and search endlessly for something that looks like it would get me a little further along in getting insight into how to solve the problem. It its organizational, I look at how I would restructure how I am approaching the problem or work or communicate with others in solving the problem.
Sometimes, I need to redefine the problem, scope of the problem, or what a successful outcome looks like. For example, I wanted to find a way to verify that the reports I was entering in PDF forms were being filled out properly. I spent forever trying to find a tool or program the PDF form to be verified. After a while (several months), I realized that verifying a spreadsheet would be a lot easier, and that I could generate the same report from the spreadsheet. Once that perception changed, I was able to tackle the problem I had: not being able to ensure that a procedure was filled out properly.
I think something got lost in translation here.
In 2020, companies were envisioning that the way we worked was so drastically different from how it really turned out, surprisingly similar to before. That meant a lot more investment in new markets that would need a lot more services and goods (ex. remote work meant a lot of work for people to develop homes more, allow more to be done fully virtually, move many services originally in cities to suburbs). When things didn't turn out that way, and people started to get back to normal, projects that would have had a huge return if realized and need more people working suddenly different. Then it was a game of chicken of how to admit that they invested in the wrong efforts because things didn't turn out how they had expected.