>I can't go to the bathroom without missing atleast 1 phone call from someone about something breaking.
Don't worry about that. Hell, I straight up ignore my phone sometimes even when I'm right beside it. Priorities and such.
>if I need to start looking elsewhere for more pay to offset the stress
Not a bad idea. Always be cognizant of what's out there.
As others have said, bring it up professionally with your boss. His response will help sway the "should I look elsewhere" decision.
Another good suggestion is to work on time management skills. Here's a highly recommended book around here.
And you have vacation days for a reason. Use them. If you try to but they never approve it, then that's a big red flag.
This is an excellent book on the topic, covering how to balance a sysadmin's unique need for periods of laser-focus to solve deep and complex problems in an environment fraught with interruptions!
Time Management for System Administrators
Yes it is slightly old, as in 17 years, but as a process it describes it is very much still relevant and helpful. Just ignore any references to tech it mentions and concentrate on the process/methods.
This is how I manage mine. I was diagnosed at 40. I like Pomodoro apps like BFT (Bear Focus Timer) and analog to do lists.
Also, try picking up Time Management for System Administrators. https://www.amazon.com/Time-Management-System-Administrators-Working/dp/0596007833
Check out an O'Reilly book, Time Management for Systems Administrators (https://www.amazon.com/Time-Management-System-Administrators-Working/dp/0596007833/ref=mp_s_a_1_1?crid=2ERQ11V58G3NJ&keywords=time+management+for+system+administrators&qid=1650987575&sprefix=time+management+for%2Caps%2C369&sr=8-1).
It won't happen overnight, but steady changes will make it happen.
Just use a pen and a notebook, write your daily list, tick them off as you go. A whiteboard is also good for brain storming all the little things that you and you team need to do.
Sometimes, simple is best. Have a read of https://www.amazon.co.uk/Management-System-Administrators-Thomas-Limoncelli/dp/0596007833/ref=nodl_
Time Management for System Administrators.
Practically: daily to-do list handwritten in a journal every morning. Whiteboard with weekly, monthly, yearly to-do wishlist. The daily/weekly list is fed by scheduled tasks on the calendar, tickets and the monthly list. Yearly projects feed the monthly list.
You should be able to justify hiring a desktop support tech. It sounds like you can probably put together stats on time you're spending doing tasks that could be completed by a cheaper employee, and stats on what you could accomplish if you had time to shut the door of your office and work. 60 employees in a tech company is a reasonable place to start this expansion and division of labor. If you weren't doing dev work it would be different.
I guess I'm saying free yourself some time. After you get a desktop tech, you'll be in a position to move toward either a devopsy sysadmin track or a manager track.
If your employer doesn't see value in what you think you could be contributing if you had more time, then you don't have much to do besides move on.
Time Management for System Administrators by Thomas A. Limoncelli
It is quite old, but still gives you an idea how to organize some parts of your work.
Also some kanban-style boards can help, like Trello or Kanboard.
I'm running Kanboard for myself and while I still didn't find out why automatic task recreation doesn't work on my setup, it still helps. If I don't forget to move teh cards manually, heh.
I'm not entirely sure. It's possible I picked it up from Time Management for System Administrators, but I read that a long time ago so I'm not sure; I do remember it having some useful things in it around building practices that allow you to rely less on thinking and remembering things so that you can use that brain power for other stuff.
I suppose it's kinda one part "I tie a string on my finger to not forget something" combined with "everything has a place where it lives". The latter I think is also covered in Marie Kondo's book (something I've found extremely useful and influential), but I extend it to what most people would probably consider a ridiculous degree. For instance, I keep certain tabs open in certain windows on my computer, always, which means I can tell you without looking that virtual desktop one has a window with, in order, slack, gmail, calendar, and my jira dashboard, and so on. So I never have to exert any thought to find those things because they've been in the same place for years. Routine extends to actions as well - I drift off in the shower in the morning and process what I'll be doing for the day, and don't have to pay attention to what I'm doing because I wash in exactly the same way (first, left arm, top, from shoulder to stay wrist, then underside back up to the armpit. Then right arm in the same way. Etc.) for decades. I eat cereal in a defined manner that's hard to describe via text but again requires no conscious thought. I'm constantly evaluating anything I do repeatedly and building routines so I can stop thinking about them.
My wife has ADHD and finds this all completely crazy and impossible to implement. :) Our brains work in very different ways, which is to say that I can't guarantee this will work for you.
Start by reading this. It's a long-standing classic for techniques and concepts for how to better manage your time, given a sysadmin's extremes of needing to laser-focus on deep and complex tasks while facing constant interruptions. And how to still end your work day at the appropriate time.
However, for your specific questions, the right answer here is to implement a ticketing system. Track all of your tasks and related notes in a single place, and track your time in a separate field in the ticket.
Then, implement a policy that every task needs a ticket behind it. If you don't have the pull to force your users to be the ones to submit the ticket, create one yourself. "Hold on, I need to make a ticket for this" should become a phrase that your users mock you about over lunch.
Not only will this give you the info that you need to better keep organized, it is also one of the best interfaces between you and management. Having a ticketing system means that you can provide tangible metrics to management, and management really really likes that. And, it gives you data to back you up when a manager puts yet another highest-priority-ever task on your plate, you can point to all of the other highest-priority-ever tasks already on your list and ask them which task they want on their desk first.
Stop. Take a breath.
The best way to manage your stress is to work your queue. If it isn't a ticket it doesn't exist in your world. Most importantly if it isn't done at the end of the day, guess what? It will be there tomorrow when you are fresh.
Go and read: Time Management for System Administrators
> I need to start looking elsewhere for more pay to offset the stress
This mentality is unhealthy. Pay never offsets or justifies stress. Don't fall in to that trap.
> I'm not allowed to work from home, ever.
Good. You should be going home and recharging yourself. Part of burnout is people who try to solve all the worlds problems in a week.
My biggest question is this concern about work piling up being impressed upon you by yourself or your boss? If it is your boss, what are they seeing needs to be done differently.
Having 16 tickets in your queue isn't necessarily a bad thing. Just make sure they are prioritized properly since not everything can be top priority at the same time.
I'm exactly in your same situation besides the work scenario. I'm a one man MSP/Consultant for a few clients, ranging from medium to large. All my clients have been from word of mouth, so it's been growing for the past 3-4 years. I've considered dropping my clients and work a single full-time job to pursue my OSCP and CEH since I paid for both at 50% off during Cyber Monday... Not to mention that I've enrolled myself into a Masters of Science of Cyber Security program in the spring.. I finally found someone super capable that I met during a CTF that really needs a job, so I hired him. That alleviated my workload.
As you can imagine I have ZERO personal time, I feel you can tough out this job and study on the side. With my schedule I can sneak in a few games of PUBG, during my train commutes I have eBooks for days. Never stop my friend, you stop you die. Also, I reccomend this book: Time Management for System Administrators
I've just search the thread and couldn't find a pointers I think is worth mentioning:
This helps you not only to track your efforts and see what you have to do but also gives you a feeling of accomplishment on the end of each days.
Time Management for System Administrators is also a must read IMHO with many great pointers.
Für Sysadmin machst du ne Ausbildung als Fisi.
Davon ab: google mal DevOps.
Aber sowieso: dir fehlen drei Jahre Bachelor, jedes einzelne davon ist vollgestopft mit harten und wichtigen Dingen.
Fang vorne an, alles andere würde als Zeitverschwendung enden.
Zudem: Als Sysadmin hast du keine Zeit für eigene Projekte übrig. Ganz im Gegenteil. Du hast nicht mal genug Zeit für deinen Job - ein großer Teil der Kompetenz von SAs wird durch exzellentes Zeitmanagement bestimmt.
Start with this book: Time Management for System Administrators.
> Currently I write down all my tasks at the start of the day, then split them down to smaller tasks and fit them into 30 minute chunks.
This may be part of your problem. Stop micromanaging your tasks.
> I have done none of my tasks for the day as I have been chasing up other things.
What these other things you are chasing? Why are you chasing them? Start documenting these shiny objects and sit down with your boss and be honest with them, "Hey. I have been trying to get all this stuff done but I keep getting pulled on doing things like this, this, and this. How would you like me to handle these when they come back up again?"
In addition you can see where you time is going and realize you are getting a lot accomplished. Just not prioritizing the right work to get done.
I also recommend this classic, they're the two books I love the most for fixing my productivity:
There's lots of good advice in here. I'll drop this book as something that can help you manage your tasks:
https://www.amazon.com/Time-Management-System-Administrators-Working/dp/0596007833
I find that I work in sprints, so I can't change jobs/tasks throughout the day. I need to focus on one thing and make good progress on it for a half day or so, then move on to a couple small things. I try to have a mix between fun projects and necessary shit daily, but it doesn't always work because of my "sprint" mentality.
get off reddit and don't ask people wasting their time on a metal forum how to properly utilize their time. /s
On a more serious note, I really enjoyed this book, might not apply to you if you aren't in software engineering although I think much of it should apply to life in general: https://www.amazon.com/Time-Management-System-Administrators-Working/dp/0596007833
I know you asked about automation, but I can't recommend Time Management for Sysadmins enough (http://www.amazon.com/gp/product/0596007833/ref=olp_product_details?ie=UTF8&me=)
I use Texter Portable to make sure I'm polite even when I don't feel like it (often) and to keep myself organized (documentation templates, etc)
There is a book called "Time Management for Systems Administrators" by O'Rielly.
It works for anyone (not just System Administrators).
Also, I use the GTD system by David Allen using an app on my phone called DGT GTD, it works for me because it has alerts and alarms (ie draws my focus).
Someone on a different post, posted this: https://www.amazon.com/dp/0596007833/ref=cm_sw_r_sms_awd_W2HBwb27CD89X
A good time management book for IT.
Secondly remind people that computers don't run on magic.....There is a science behind it as you know but people outside of IT want to think we do magic. Thirdly my manager usually say's the IT dept is the red headed step child of a company. He's been around it long enough to see all the crap that gets blamed on IT. For example I had a client who kept opening new IE windows on his computer until the ram was full and the PC got sluggish. Believe me that was a crap(like 50+) load of windows but it was difficult to teach the guy to close out of windows and not open so many.
That being said, hope for the best but be prepared for the worst. Don't be afraid to move on when you need to.
You could leave like suggested or you could talk to your supervisor. Or HR. Or someone up above you. You report to someone, right? They're responsible for you and your workload. The only way they'll hire someone else is if there's a demonstrated need to do so, they won't go looking to hire more people for funsies.
If there is too much to do for one person then document that and show that to your higher ups. If they ignore you or promise to deliver a change but never do then, sure, leave. Otherwise you may have created a new role.
Another option is to show them that you need time away from break fix to automate or address root issues to reduce your tickets. There are a couple of ways to approach this. I would start with reading Time Management for System Adminsitrators. That book has suggestions for people in your situation about how to get a break from constant interruptions.
It's not a family where you can hide your emotions forever, it's a business. Be professional and get some relief. Don't let a job affect your life outside of work like this.
Don't take under promise over deliver too far. As in, don't pad your timelines too much.
Also if you're too eager and constantly exceeding your timeline, you might have mangers start to pad for you.
Also, BIG tip. When you under promise for your first few times, you might get it wrong. No big deal, your managers should understand that you're new at this. Keep them informed of your progress and NEVER BE AFRAID TO ASK FOR HELP OR RESOURCES. In my experience my manager hates surprises. If you keep him informed he can move in to assist, and will appreciate the heads up and honesty.
You'll also get a better feel for estimating your time as you go, so don't worry about getting it just right too soon and give yourself some breathing space.
I recommend Time management for system administrators by o'reilly. Applies to IT in general and can help you get started managing your workflow properly once you start getting more heavily relied upon.
Also, if your in a money constrained environment, check out gigapedia.com for "book reviews". Often times a new small project can be informed or completely directed by a good book. tip, once you get an account, search for books by isbn by appending the isbn to the sites main url, followed by a slash.
Good luck and Welcome!
Если вдруг кому-то когда-то доведётся быть админом, очень рекомендую книжку Time Management for System Administrators для поднятия навыков тайм-менеджмента. Впрочем, многое, что там содержится, вполне полезно и другим простым смертным.
I have many.
First, buy them each a copy of:
https://www.amazon.com/Time-Management-System-Administrators-Working/dp/0596007833
My personal list, not exhaustive:
This book changed the way I handle my days when I was a solo engineer doing everything under the sun. Now that I'm part of a larger network engineering team, I only use a handful of the tools recommended in the book as I don't find my time to be as scarce, and I get pretty good priority communication from management.
When I was a solo engineer:
Start of day: Block off the first 30min of your day to deal with any immediate, business-critical fires that I was either called on, texted about, or emailed about. If nothing is critical and needing attention, I would evaluate my task whiteboard (broken up into Primary/Secondary/Tertiary columns). Items are assigned to Primary priority either by myself or my manager. Secondary and Tertiary priorities are up to me. If someone waiting on a task that I deemed was Secondary or Tertiary priority is upset about that, they can speak with my manager and we'll determine what is most critical to the business.
End of day: Evaluate task whiteboard and determine what, if anything, needs to be added (and to what column) so it can be re-addressed tomorrow morning. As you cross off and wipe things from the board, make sure to document your accomplishments so it's easier on you/your boss during review time.
Start of Week: Maybe block off 30min with your manager/team lead/etc. to discuss current/upcoming projects. Document any completed tasks from your taskboard and wipe some off to make space (don't leave too much space or people might think you have nothing going on!)
End of Week: Update notes on what progress (if you managed to find any time) you've made on the projects you discussed in your stand-up meeting with your manager/lead/etc. at the beginning of the week. This is so you already have your notes ready next week and can do your Start of Day 30min fire addressing/taskboard eval on Monday without scrambling.
Start of Month: Man, I don't think I ever planned anything a month ahead.
This book has been suggested a few times so I finally got around to reading it. I think it has some good information in it. I'm only about halfway through it, but I like it so far.
Time Management for System Administrators
Other books would be any of the social books like "How to influence people", "7 healthy habits..." Etc.
I haven't read this one yet, but It has been suggested to me if you plan to go more into management/leadership Start with Why
Other books that have I have ear marked due to being mentioned:
Also, do a search for "Books for IT Professionals" to find a lot of other suggestions.
Read this: Time Management for System Administrators
Time Management for System Administrators
As general book that can cover regardless of OS, duties, etc.
I love books, possibly more than I enjoy reading tech books. But these few are some that I’ve read (most of) and keep around for referencing.
Time Management for Systems Administrators - it’s a little old, but has some decent topics. Plus it’s not hard to snag a used copy.
The Practice of System and Network Engineering - I had to give a departed coworker his old copy back recently and have already reached for it a few times, so a new one is on order.
The Practice of Cloud System Administration - I haven’t read this one, but I’m hoping it might be a useful addition to the above two.
Beyond those, I’ve found Manning books to be pretty great references and guides if you browse and find something on a topic you like. Paper books come with a copy of the ebook. They have an early-access program that lets you read along with an early version of the manuscript before it’s out. It’s well worth ordering from them directly IMO.
It’s really hard to get anything done if everything goes through management.
IDK if it’ll be of use but if you’re stuck going it alone, I remember this is good: https://www.amazon.com/Time-Management-System-Administrators-Working/dp/0596007833
The OP didn't include the title of the book, only an image...
Time Management for System Administrators: Stop Working Late and Start Working Smart
Thomas Limoncelli, O'Reilly Media (2005)
https://www.amazon.com/Time-Management-System-Administrators-Working/dp/0596007833/
Alternately, for postally challenged and starving researchers like myself living in the third world, you can find copies in mobi, ebpub or pdf on libgen. It's a major pain in the ass getting anything shipped to Cambodia, especially in the midst of a hard COVID lock down :(
np, i have this hosted on my wiki - check out openproject, its a blog/ticketing/calendar/wiki, ect. solution you can self host - PM me if you start homelabbing and have questions.
some good books that really helped me that i wish i knew about when i started in IT:
Time management for system administrators - old but really good, helped build gauard rails so i spend less time fighting fires and more time to spend on fun projects
essenitalism - how i learned how to say no
4 hr work week - inspirational and lots of good nuggets
Meditations - how i learned to not sweat the small stuff and keep things in perspective
Also, their time management book: https://www.amazon.com/Time-Management-System-Administrators-Working/dp/0596007833
I'll keep posting this book until everyone has a copy!
Two area for me:
Great read…. Had someone suggest it when I started feeling the same way at work. Hope it helps.
https://www.amazon.com/Time-Management-System-Administrators-Working/dp/0596007833/ref=nodl_
Now, with that out of the way:
If you want to do well at your current job, that's admirable. Good on ya. A few things to keep in mind: * Set expectations. This is a valuable skill regardless of your job, but doubly so in a position where you are expected to perform tasks from three completely separate jobs. It's OK to remind people that you're relatively new to IT and were, in fact, hired as a web developer and video editor who "assists" IT. You are NOT "the IT guy" and do not have the full set of skills one would expect from an IT pro with a decade of experience. If you don't immediately know the answer to something, say so. "I have no idea how to fix that, but I'll work with our consultant to find out. However, I need to get the videos edited for the new ad campaign by Friday. I won't have a lot of time to spend on your issue until next week." * Read this: [Time Management for System Administrators]. It's probably the best $20 anyone with an IT or IT-adjacent job can spend. * Get clarification. If you were hired as the in-house web dev and video editor, but are spending 70% of your time on IT-related tasks, you need to get the sorted. Are you spending 70% of your time on IT-related tasks because there is no web dev/video editing work, or are you simply getting thrown into the deep end because your consultant doesn't have a full-time on-site presence and shit is burning? If the former, great! Keep busy. But if the latter, that shit needs to come to a screeching halt. Why are they paying a consultant (and believe me, there is at least a monthly retainer going out) to NOT address the IT issues? Who the hell is your actual boss? Y'know, the one who prioritizes your tasks & offers feedback & support. * Learn only what you need RIGHT NOW. Small business sysadmin work is massive. You will not know what you need to know off the top of your head. Don't worry about that (see Set Expectations, above) and focus on whatever task is immediately in front of you unless directed otherwise by someone with the authority to prioritize your work. * Google is your best friend. Seriously. Literally every IT professional on the planet uses it daily. * Reddit is your second best friend. Seriously. Being able to ask questions of other IT professionals is unfathomably valuable. This will remain true once you get into proper dev work.
Also it's really important for the employee that you write SMART goals It's a game changer for them especially for the PIP and use active listening as in have them explain what they are reading and ask probing questions like "after reading this objective what in your words are the next actions for a successful completion? I also always include either the O'Reilly time management book or getting things done by David Allen
There is a great book about it:
Time Management for System Administrators: Stop Working Late and Start Working Smart
Time is a precious commodity, especially if you're a system administrator. No other job pulls people in so many directions at once. Users interrupt you constantly with requests, preventing you from getting anything done. Your managers want you to get long-term projects done but flood you with requests for quick-fixes that prevent you from ever getting to those long-term projects. But the pressure is on you to produce and it only increases with time. What do you do?
The answer is time management. And not just any time management theory--you want Time Management for System Administrators, to be exact. With keen insights into the challenges you face as a sys admin, bestselling author Thomas Limoncelli has put together a collection of tips and techniques that will help you cultivate the time management skills you need to flourish as a system administrator.
Time Management for System Administrators understands that an Sys Admin often has competing goals: the concurrent responsibilities of working on large projects and taking care of a user's needs. That's why it focuses on strategies that help you work through daily tasks, yet still allow you to handle critical situations that inevitably arise.
Among other skills, you'll learn how to:
Manage interruptions Eliminate timewasters Keep an effective calendar Develop routines for things that occur regularly Use your brain only for what you're currently working on Prioritize based on customer expectations Document and automate processes for faster execution
What's more, the book doesn't confine itself to just the work environment, either. It also offers tips on how to apply these time management tools to your social life. It's the first step to a more productive, happier you.
Time Management for System Administrators: Stop Working Late and Start Working Smart
Practice of Cloud System Administration, The: DevOps and SRE Practices for Web Services, Volume 2
The Subtle Art of Not Giving a F*ck: A Counterintuitive Approach to Living a Good Life
I would also suggest searching this sub for book reccomendations. It comes up pretty often and the common reccomendations don't change a whole lot.
Yes. I have ADHD. I’m also an IT executive with teams totaling 50 people. The pandemic top ended all of the (extensive) time management schemes I had created (mix of getting things done methodology as well as things I learned from the book “Time Management for Systems Administrators… link below” by Thomas Limoncelli.)
Along with with the anxiety of life in March 2020, keeping head above water and staying organized and productive at work was rough, focus nearly impossible.
Then I found Todoist, Purchased late March 2020 and it’s become my “time management operating system” if you will.
For one thing, it let me maintain my GTD methodology, but it also let my organize reminders and plan my day in a fluid and dynamic way with the variations of tags, projects and views/filters. That book mentioned above says to write things down rather than try to remember them, having Todoist everywhere on all devices was key to maintaining that mantra.
I ended up displaying 3 windows of todoist vertically on my home office wall TV. “Work today”, “Home Today” and “General Reminders”. By the end of the day I wanted all 3 windows clear, either done, deferred, deleted or delegated.
With regards to ADHD and focus, I have tags like “Focus_120” that tell me to find a 120 minute timeslot, put on my headphones (usually listening to focus@will, the headphone equivalent to Adderall, it’s a brilliant focus app).
As of yesterday I hit Todoist Grand Master and my teams and I have had a great 6 quarters despite the pandemic, lots of credit to Todoist for keeping me straight, nearly 4700 completed tasks. Thanks to the developers for this one.
Time Management for System Administrators: Stop Working Late and Start Working Smart https://www.amazon.com/dp/0596007833/ref=cm_sw_r_cp_api_glt_fabc_E8ZMWS04GP5DY6XPNH57
Focus@will focus app for people with ADHD https://home.focusatwill.com/
https://www.amazon.com/Time-Management-System-Administrators-Working/dp/0596007833
This is the single most useful book for learning the profession of system administration. The unique nature of the job, with a constant need to focus on deep intellectual work and problem solving running against constant interruptions pulling you out of that focus, means that if you don't intentionally craft your environment, your workflows, your planning, and your day as a whole, you'll never get anything done.
Beyond that, this is a massively important document from the early ages of IT. Not only when dealing with online forums and the like, the tips in this also help with your own searching and problem solving by arranging what you do and don't know about the problem in a logical way.
As for the acronym soup, I suggest looking into picking up some certification study materials for the now-defunct CompTIA I-Net+. This certification was a broad overview of all areas of IT from the perspective of an IT manager. Everything that you wish your boss knew about your job, with none of the things that you don't want your boss to think they know and get too involved in. So, nothing about how to build firewall rules or routing tables, just enough info to understand why there is a $10k invoice on your desk for a new firewall.
These are a few books I always recommend in no particular order:
This book might also be interesting for everyone here:
"Time Management for System Administrators: Stop Working Late and Start Working Smart"
https://www.amazon.com/Time-Management-System-Administrators-Working/dp/0596007833
https://www.amazon.com/Time-Management-System-Administrators-Working/dp/0596007833
Technologies come and go like fads. Learning how to manage your time is always valuable.
Yo dude, I was in your position a couple years ago! First off, what you're feeling is normal. Most of us deal with self doubt on a pretty regular basis--especially when working on new/difficult things. The trick is just sticking with it, breaking things down into smaller pieces, and documenting everything because you're going to forget how you fixed it or got it working in 6 months.
If you're looking for books here are a couple I have found very helpful in no particular order:
Time Management for System Administrators
Learn PowerShell in a Month of Lunches
Learn CMD the Hard Way (his books are great but this bit is online which is nice)
Internetworking with TCP/IP: Principles, Protocols, and Architecture
Now this list is by no means everything you'll ever want to read but scripting, DNS, TCP/IP, and time management are all pretty important. Happy to add more suggestions if y'all want.
If you'd like some notes on Directory Services (AD and OpenLDAP, I've still got my notes from when I first started using them). Troubleshooting comes with a combination of exposure and knowing how systems work--which is why you should always look for documentation on MSDN, StackExchange, Reddit, Wikipedia, etc. The big take away with troubleshooting is start small and work up (because it's not usually a DC, core switch, etc. and if it is you'll know because everyone will be calling you to let you know--things aren't working).
Sorry if this is a bit of a rambling mess, I wanted to address everything you mentioned.
Failure and self doubt are totally normal, and as you get more experience and stick with it you'll develop skills to minimize those feelings. Also don't be discouraged by failure! Scripts are hard and take time to get working. All of our stuff fails and we all run into things other people find basic but don't know--but do your best to learn it and then... WRITE. IT. DOWN. IN A WAY YOUR GRANDPARENT OR CHILD IN YOUR LIFE COULD FOLLOW TO SUCCESSFULLY COMPLETE THE PROJECT!
Tl;dr: you're probably fine, this is all normal and will pass, document everything so you don't forget later! Also feel free to ask questions, people saying your dumb on the internet isn't so bad.
Not really a book guy to use as reference or even learning something new, but this one helped me straighten my shit out while being relatable (and readable) https://www.amazon.com/dp/0596007833/ref=cm_sw_r_cp_apa_W5.pAb0E4NBX8
Time Management for System Administrators: Stop Working Late and Start Working Smart
The Practice of System and Network Administration, Second Edition
Windows Server 2008 R2 Unleashed
Windows Server 2016 Unleashed includes Content Update Program
The Practice of Cloud System Administration: DevOps and SRE Practices for Web Services, Volume 2
Network Warrior: Everything You Need to Know That Wasn't on the CCNA Exam
It's an older book but this one is still got some great tips:
https://www.amazon.ca/Time-Management-System-Administrators-Working/dp/0596007833
It's an older book but this one is still got some great tips:
https://www.amazon.ca/Time-Management-System-Administrators-Working/dp/0596007833
There's a book for that. Time Management for System Administrators - Thomas Limoncelli
This is great.
I haven't finished it yet but it seems to be great so far.
https://www.amazon.co.uk/Management-System-Administrators-Thomas-Limoncelli/dp/0596007833
Time Management for Sysadmins. It's not FOR webdevs but there's plenty of things that all 'tech' people should know in this book.
https://www.amazon.com/Management-System-Administrators-Thomas-Limoncelli/dp/0596007833
I just picked up this book: Time Management for System Administrators. It's helped me a lot deal with the high availability that I am needed.
Sometimes you need to be available, and sometimes you need to pro-actively push stuff to the back burner.