@shreerajjadhav
PhD student in Computer Science
I primarily program in C++, OpenGL, CUDA, OpenCL, and Python. Most of the applications I develop are non-web. These are related to computer graphics, visualization, volume rendering, scientific solvers, mesh/geometry processing.
Nothing here yet.
No blogs yet.
I use the built-in gnome-keyring application on my Linux desktop. I prefer to store my stuff locally. Cloud storage for passwords is too dangerous. Far too often websites get hacked and the passwords are published online. I don't need that in my life. Imagine all your passwords are exposed in a single day. Due to local storage, I have to restrict most of my Internet access to my desktop machine. But that is a good practice, in my opinion. There is no real need to access your sensitive accounts through mobile phones or shared computers. EDIT: Also, I would like to mention that I don't use generated passwords because they are based on some random number generator. It follows some model. Theoretically, those can be predictable. Of course, one can argue that even if passwords are manually generated, they can have biases. But you can follow a system to reduce that bias. For example, writing a very long random text string and then cutting out isolated pieces to form one password. I am done ranting. Where's my tin foil hat?
I followed instruction from this wiki page [ https://wiki.debian.org/SSD%20Installation ]. I had my debian installation ready and running on the new SSD within an hour. I had to be careful when making the drive bootable, but it worked out in the end. Best part is, it is so much better than a fresh installation. I have conserved all my softwares and customizations across the migration.
The thing I like about Debian-stable is that it runs updates occasionally. Hence, it is statistically less likely to breakdown. Ubuntu updates a little too frequently for my taste. On the other hand, I have found that it is easier to install things in Ubuntu as compared to Debian. I still use Debian with gnome3 as my primary OS for the simplicity and reliability.
In my opinion, analysis is absolutely essential before development. Specially if you are working in a team, because the interfaces should be clear to everyone. Once the design is on the paper with sufficient detail, implementation should be trivial. When I first started as a programmer, I hated the design and analysis part because I felt it was disingenuous to write a high level document without knowing how it was actually going to be implemented. But the real reason it made me uncomfortable was that I was bogged down into details of implementation. I was an amateur who couldn't get my head beyond code itself.