253 karma · joined February 19, 2013
Find me:
travis.lawrence12@gmail.com
https://redundantrobot.com
Overall though the severence is healthy, so I'll be plenty ok while I find another gig.
I'm down to see what you have going on there.
Find me on LinkedIn https://www.linkedin.com/in/travis-lawrence-b77400b8/
Adding to the list of things that a teacher already is responsible with doing is Tech Support. Because now parents are emailing her stupid questions that are easily google-able about Google Classroom.
* "How do I upload a picture?"
* "Can you email me the google classroom link again?"
* "What's the login for my kid? (omg this question)"
* "Where's the thing to click on? (fuuuuuuu.....)"
The district is now starting to have a minimum of 8 mandatory teaching sessions to parents on how these things work. EIGHT.
We cannot translate online classrooms 1:1 with the real thing. I wish the district would take a breath and approach this with a little bit more understanding that this is a whole new ballgame. I know parents need their kids to be somewhat occupied during the day (I have 2 kids under 4 so I get it), but overall it's not very pleasant for teachers.
Is that backwards? Wouldn't a tail wind represent "easier"?
...member chewbacca
Here's the Firefox version: https://addons.mozilla.org/en-US/firefox/addon/apod-by-the-t...
Anyway, with these updates I've added a service worker to make it load as fast as possible and in case there are others here that really love the APOD I wanted to share.
EDIT: Here's the Firefox link https://addons.mozilla.org/en-US/firefox/addon/apod-by-the-t...
Is that because it's boring, or is it because people think front end is easy/straightforward and then realize it's not? I'd argue that the front end is a much more difficult task than the backend in the beginning of a startup.
Step 2: Take pictures that are creepy af.
Step 3: Profit.
601 PowerPC baby.
Prior to going to DevBootcamp I worked as an engineering consultant, my product was informational reports that had to describe specifically what the problem was, how we determined that, and what we recommended to resolve it.
Sometimes my reports would be returned to me in a blood bath of red ink on changes but eventually you understand what it means to get the point across objectively and concisely.
My point is, get your copy proof read, limit the jargon, and get to the point in the first sentence.
Lucky for them it was interesting enough of a read or I would have closed it outright.