GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
My objective is to waste as much time and phoney fiat currency (formerly known as money) as possible. Trying to be efficient is a good way to get fired. Just look at healthcare.gov, nobody who played along is getting fired, despite it being a half a billion dollar failure (in the middle of a recession). Only people who rock the racket's boat get canned. That's the way the corporate cookie crumbles. So just have another bagel and socialize in mindless meetings all day.
Last edited by 911InsideJob; 10-24-2013 at 06:11 AM.
Personally I use mostly plain text, plain csv, and plain text todo lists... with an adapted plain software solution. It works for years, it has no change in format, universal for the next 50 years, ...
There is some irony here. Wikipedia reports that ASCII was first published 50 years ago.
Of course ASCII was kind of absorbed into Unicode, which grows toward replacing plain ASCII daily. Though I guess we're referring to plain text as opposed to word processing documents. (Though when you say "text" or even "plain text", some people think you're talking about Microsoft Word documents. Frustrating.) I join your sentiment as I use Emacs a lot and pretty office document tools rarely too.
Originally Posted by 911InsideJob
... phoney fiat currency (formerly known as money) ...
... healthcare.gov, ... half a billion dollar failure (in the middle of a recession) ...
This is the wrong thread to vent about that. Otherwise I'd commiserate with you on this very sad chapter.
I believe that they lack of efficiency due to lack of priority in the tasks.
Look in attachment, you could order all your tasks into some categories, and start with the categories that have higher importance for you. And ... most important:
- Get a clock and a sort of log.
EDIT: And ... give your employees two monitors
Either I dont understand you or its the other way around. The guys who work in night shifts are in office by 10pm and work till 7am. So how are those inefficient?
And why is giving flexi timings lack of efficiency or lack of priority? I see it as a very good offering from employer. Also, meetings are usually arranged with clients during their work timings. And we adjust to those accordingly. I dont see lack of efficiency or prioritization in any which way.