user18905: I have this if statement:
if (now.hour() == 5 && now.minute() == 10 && now.second() == 0 && now.dayOfTheWeek() != 1 && now.dayOfTheWeek() != 7){

Is there a way to condense that for the purposes of saving on some bytes?
Ultimately trying to say "At 5:10 every weekday do X"

user20245: Yes. The method now() Returns the current time as seconds since Jan 1 1970. Simply keep tract of all your time this way and you only need to test this one value.
The Arduino is not a good source of time over long periods.  Consider using an RTC (Real Time Clock) chip.  This Arduino page links to this page which talks about an RTC.  (I will leave it up to you to research any compatibility issues.)
Many RTCs contain a register set specifically designed to handle tasks such as you outlined above. For example, setting alarms off on weekdays only or on specific days of the month.
If absolute time is not important in your application I would try the following code outline.  Each test only has 2 operands:
// Turn on Arduino on Monday at the time task is to be performed.  Task
// should be performed at that time on Monday, Tuesday, ... Friday.
// Nothing should happen on Saturday & Sunday.  Then cycle repeats.

// Set time to zero.

// Count through days (0, 1, 2, ...).

// Wait each day until number-of-seconds is greater then seconds-in-a-day
// times the day number.

// If day number is 4 or less do activity.  Else skip activity.

// If day number is more than 6 set the day counter to 0 and set the time
// to zero.

If you want to start the Arduino at arbitrary times, set the initial Arduino clock value to the number of seconds from the time the activity would have been performed on Monday and initialize the day counter to the appropriate value.  For example if you started the Arduino on Tuesday 23 hours after the time the activity should have happened on Monday set the Arduino clock to 23 * 60 * 60 seconds and initialize the day counter to 2.  Of course you can calculate the initial day counter value using  = initial_number_of_seconds / 60 * 60 * 24.

user3917: The following saves a couple of program bytes (but no RAM) when now is a structure with a byte called DayofWeek:
 if ((byte)(now.DayofWeek+249)>250) ...
   -vs-
 if ((now.DayofWeek != 1 && now.DayofWeek != 7)) ...

It might save slightly more than that in your case, where now.dayOfTheWeek() appears to be a function reference.  This technique will work if function now.dayOfTheWeek() returns a byte, that is, an unsigned char.  The technique depends on value 7+249 overflowing to zero in byte arithmetic when truncated to a byte, because 7+249 is 0 modulo 256.
The cast to byte [or uint8_t] of now.DayofWeek+249 is needed because of int promotion as Edgar Bonet pointed out.

18905: <p>I have this if statement:</p>

<pre><code>if (now.hour() == 5 &amp;&amp; now.minute() == 10 &amp;&amp; now.second() == 0 &amp;&amp; now.dayOfTheWeek() != 1 &amp;&amp; now.dayOfTheWeek() != 7){
</code></pre>

<p>Is there a way to condense that for the purposes of saving on some bytes?</p>

<p>Ultimately trying to say "At 5:10 every weekday do X"</p>
 20245: <p>Yes. The method now() Returns the current time as seconds since Jan 1 1970. Simply keep tract of all your time this way and you only need to test this one value.</p>

<p>The <a href="https://arduino.stackexchange.com/questions/242/arduino-time-clock-accuracy">Arduino is not a good source of time over long periods</a>.  Consider using an <a href="https://en.wikipedia.org/wiki/Real-time_clock" rel="nofollow noreferrer">RTC</a> (Real Time Clock) chip.  <a href="http://playground.arduino.cc/Code/Time" rel="nofollow noreferrer">This</a> Arduino page links to <a href="http://www.pjrc.com/teensy/td_libs_DS1307RTC.html" rel="nofollow noreferrer">this</a> page which talks about an RTC.  (I will leave it up to you to research any compatibility issues.)</p>

<p>Many RTCs contain a register set specifically designed to handle tasks such as you outlined above. For example, setting alarms off on weekdays only or on specific days of the month.</p>

<p>If absolute time is not important in your application I would try the following code outline.  Each test only has 2 operands:</p>

<pre><code>// Turn on Arduino on Monday at the time task is to be performed.  Task
// should be performed at that time on Monday, Tuesday, ... Friday.
// Nothing should happen on Saturday &amp; Sunday.  Then cycle repeats.

// Set time to zero.

// Count through days (0, 1, 2, ...).

// Wait each day until number-of-seconds is greater then seconds-in-a-day
// times the day number.

// If day number is 4 or less do activity.  Else skip activity.

// If day number is more than 6 set the day counter to 0 and set the time
// to zero.
</code></pre>

<p>If you want to start the Arduino at arbitrary times, set the initial Arduino clock value to the number of seconds from the time the activity would have been performed on Monday and initialize the day counter to the appropriate value.  For example if you started the Arduino on Tuesday 23 hours after the time the activity should have happened on Monday set the Arduino clock to 23 * 60 * 60 seconds and initialize the day counter to 2.  Of course you can calculate the initial day counter value using  = initial_number_of_seconds / 60 * 60 * 24.</p>
 3917: <p>The following saves a couple of program bytes (but no RAM) when <code>now</code> is a structure with a byte called <code>DayofWeek</code>:</p>

<pre><code> if ((byte)(now.DayofWeek+249)&gt;250) ...
   -vs-
 if ((now.DayofWeek != 1 &amp;&amp; now.DayofWeek != 7)) ...
</code></pre>

<p>It might save slightly more than that in your case, where <code>now.dayOfTheWeek()</code> appears to be a function reference.  This technique will work if function <code>now.dayOfTheWeek()</code> returns a <code>byte</code>, that is, an <code>unsigned char</code>.  The technique depends on value 7+249 overflowing to zero <strike>in byte arithmetic</strike> when truncated to a byte, because 7+249 is 0 modulo 256.</p>

<p>The cast to <code>byte</code> [or <code>uint8_t</code>] of <code>now.DayofWeek+249</code> is needed because of <code>int</code> promotion as Edgar Bonet pointed out.</p>
