ss48

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.

Comment · 3 years ago

Evoluent Vertical Mouse. Mouse lasted for about 4 years (the middle scroll wheel stopped working), and replacement mouse purchased is still going strong.

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.

Comment · 3 years ago

Regarding the Side Note: probably because of their acquisition by Seimens: https://news.ycombinator.com/item?id=27556552

Comment · 3 years ago

There was an anonymous post complaining about mariadb.com, the company a few months back. Never saw the claims anywhere else though.

https://news.ycombinator.com/item?id=3546

Comment · 3 years ago

Honestly, I find that in many cases I would trust an anonymous random Joe more than a company because they can be more mission driven and limited in their ambition than a growth driven tech company. Firefox keeps trying to push advertising while keeping it private, trying to get people to subscribe to a VPN subscription. Google actively undermines adblocking extensions with Manifest v3 and Web Integrity API. Edge tries to monetize your browsing data by trying to randomly sign your browser in your Microsoft account and sync your bookmarks, history, and passwords to their cloud and keep trying to get you to use their chatbot. There are several more examples.

Comment · 3 years ago

Otherwise, your next best bet would be to add a notes file or folder with all your TODOs and notes that refer to lines in the source code and keep that in gitignore.

Comment · 3 years ago

Take a look at this. I'm not sure how active development is though.

https://thamara.dev/posts/code-annotation-a-vscode-extension...

Comment · 3 years ago

Our interfaces are simpler and bespoke compared to others. We create a document showing different components, how the components should be dimensioned, and also detailing of different interaction, theming, and animation conventions to be implemented. We try to provide enough detail so that a developer can reimplement in their tool of choice, and will schedule several meetings or screencasts with feedback as they proceed through their adaptation of what is documented. This document guides us in creation and modification of existing components. In several cases, need for new components can drive a complete rethinking of the system.

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...

Comment · 3 years ago

Figma

Comment · 3 years ago

https://www.youtube.com/watch?v=WE58YisgFeQ

Techalter did a good job describing the fate of a lot of Philips different businesses and product lines.

Comment · 3 years ago

I would say yes. We work with several subcontractors for our software development (business systems and embedded standalone products). Our responsibilities and subcontractor's responsibilities need to be clearly defined, along with an expectation of what functionalities the final product will have. We would usually need to define a week or months worth of tasks and not be able to provide much more input until each deliverable is ready. Our subcontractors would use whatever development approach they want to achieve our deliverables, though.

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.