I use this tool everyday and with some customization it has been very helpful for me. It helps that I also use VS Code for my job so its nothing to have an extra window open. I don't have to worry about folder and file structure and just write. The VS Code search is robust and fast.
The customizations I use are just for auto creating daily notes and including timestamps and other metadata.
Foam is also easily incorporated into static sites, although I have not yet used that feature.
I subscribe to this application, and I love it. I was not one of the first 100 to experience any of these difficulties, and the one bug I did experience was fixed by Jen two days after I pointed it out. In the mean time, Mint still has not deleted my account two months after I requested it...
He's not talking about that. He's talking about the fact that, at any Wal-Mart you care to patronize, you'll find that while they have sixteen or twenty tills installed and ready to use, they have maybe three actually staffed and available for checkout, so you end up standing in line for five or ten minutes even when there's hardly anyone in the store, and when it's busy you get to choose between waiting half an hour and taking your business elsewhere.
Since there aren't any screenshots I don't think I will use this till you fix the landing page. Does anyone have any alternatives that are 'bloat-free' Readers?
Can you explain this? I will sit for hours with just a pen and paper and not be able to come up with anything worthwhile ideas or thoughts. What do you do?
I sometimes try using pencil and paper when I'm stuck on a specific problem. For example, if I'm trying to debug an algorithm, I might draw examples of the possible states the data structures could be in to make sure I've figured out all the edge cases.
Also, if I'm working on a project and can't figure out which of a dozen possible things to do next, I write down lists of tasks. These will eventually get transferred to digital form, but I find that circling important things and drawing arrows between them is a lot quicker on paper than messing around with some user interface on a computer, and this lack of friction promotes a state of flow.[1] If I get bogged down with data entry, it's easier to forget an item that came up while writing down another item.
So I already know system admins are in high demand. I am a computer science undergrad and hope to get a sys admin job out of college. What should I be doing on my own to get a job like this? (besides playing with different linux distros and learning commands).
I would suggest looking into the Redhat certifications. Even if you don't want to take the test, they cover a wide range of topics that will give you a good base. The list of exam objectives alone will point you in the right direction to get started. You aren't likely to brush into things like autofs just playing around at home. But something like that is much more common in larger environments.
Learn to do things that you read about in system admin blogs. Spinning up VMs, clearing log files, and setting up monitoring systems. Learn to roll your own package. Even better yet maintain one for a distro and put that on your resume.
Make a effort to become familiar with several scripting tools. You don't have to master them all, but make sure to pick up enough to be able to read code in bash, perl, python, and maybe even ruby.
The final step to being a Linux admin is learn Windows. Most real world jobs require that you have to deal with both. Even if it is not your primary responsibility, you will need to know how to inter-operate with Active Directory and the services that hang off of it.
If you want to be a linux admin you should be comfortable with the command line. You should be able to write a simple bash script without needing to look up too much. You should be able to configure a LAMP stack from scratch without much hassle (looking at documentation here totally recommended).
I personally think the best way you can get started is by using the command line for everything "work" related. When you're doing your projects for school you should be using vim (or emacs if that's your thing). When you're navigating directories or performing file operations you should just use the terminal. Using the command line effectively is such a critical component of being an admin, and it just takes practice to get good at it.
The fact your doing computer science is a huge leg up, because you'll have a good understanding of the fundamentals of computers. When you work with linux you very often need to know the underlying mechanics of whatever you're working with. This goes hand in hand with being able to troubleshoot - a huge component of being an admin. Let's say you're troubleshooting an i/o issue on a server. When certain operations are performed on a SQL database in high volumes you notice the server starts to chug and i/o is severely bottlenecked. You need to know things like whether the RAID is configured correctly, and what the most optimal settings are for your usage. You need to know to check the i/o scheduler and make sure that's appropriate for what you're doing. Some of this stuff you won't know out of college, but you'll work with all of it eventually and pick it up. What counts is that you don't need somebody to explain the super basic stuff, you will already understand most things at a fairly high level. You should be able to pick things up quicker as a result, and cover significantly more ground than somebody learning Linux whose never really worked with computers seriously.
Anyway, that's longer than I meant to type up but hopefully you get the gist of what I'm saying. I'm slightly inebriated so sorry if my wording/sentence structure is hard to follow!
As I Linux sysadmin, here (in no particular order) are things that I've found most useful. I've no idea what level you're at, so if you already know this stuff, just give yourself a pat on the back; you're ahead of the game!
Most important: Have fun! If you're not enjoying it, get out because there's no point in wasting your life on this.
Learn to touch type: it's one of the most useful skills you can pick up and not just for IT work
Join your local Linux User Group. If your area doesn't have a LUG, start one! Put this on your CV.
Speaking of which, create a CV (resume) but putting down all the experience and skills you'd like to have. Then go and make it so! Get help with this by finding out which companies near you use Linux and asking for their help; which skills they're looking for and what technologies they're using. People are generally very happy to help people achieve things for themselves (and hate when they're really being asked to do the work for someone, so avoid that!).
Learn vi or emacs. It doesn't really matter which, just spend some time using it for all your text editing. Knowing a good text editor well is hugely important.
Distros: Install Gentoo from Stage 1 and run it for a while. Try Linux from Scratch at least once. Otherwise, just install a few different distros just for fun and to get an idea of what the differences are (they're not huge). Also, try out the BSDs at some point.
Learn and use git. It's quite simple to understand exactly how it works, so do this. Use it for day-to-day stuff. Get a github account and try contributing to other projects.
CLI. Use shell scripts for all sorts of things. Use one-line "for" loops for batch resizing images, or generating thumbnails. Forget about the GUI; it'll all have changed in a few years. CLI stuff will still be the same.
Web servers: learning Apache and ngnix. Get yourself something like an Amazon account. Whatever is cheapest. Use the API to create and remove servers and configure them.
Languages: shell scripting, Python and PHP are the ones you will encounter most. I see a bit of Ruby, but not a huge amount.
MySQL is very common. Again, learn the command line stuff, not some particular GUI.
Don't waste money on stupid stuff, aim to save about 65% of your net pay and become financially independent in 10 years.
Neither a borrower nor a lender be,
For loan oft loses both itself and friend,
And borrowing dulls the edge of husbandry.
