Thanks for the information. Keep sharing such informative post. keep suggesting such post. sites.google.com/view/blink-app-for-pc-windows-10…

Thanks for the update and quick reply. I'll be sure to keep an eye on this thread. sites.google.com/view/pipocolandia-para-pc/home for Windows Looking for the same issue. Bumped into your thread. Thanks for creating it. Looking forward for solution.

sites.google.com/view/animes-brasil-para-pc/home

Hi Craig! Hey everyone! It's Craig!

This answer is coming "post burrito", so no promises...

To answer this, I'm going to use an article that I wrote this week on GraphQL (shameless plug), and kind of dissect how I got from zero to article.

Simona has been teaching me GraphQL and each time she and I got together, we recorded the session. That left us with three videos in which I go from zero to GraphQL in a React app. We wanted to share those videos with everyone, so we needed a blog post to let the world know.

That's the premise from which I started - a blog post announcing three videos on GraphQL with Simona.

So here's how this comes together.

I don't write titles first - always last. Because there is a good chance that I will change direction in the article and not even go with my original premise. This last article is a perfect example of that.

I start writing an intro. I usually write the first sentence and delete it about 5 times until I have something that I like. I try and let people know what the article is going to be about in the first sentence. This is called "not burying the lead".

The first paragraph is always the hardest, and then I just let it go. In this case, I wrote a draft and sent it to Simona. She reviewed it, offered some feedback and said "There aren't many jokes. Where are the jokes?"

I slept on it, got up on the right side of the bed and went back and began to re-write the article. About halfway through, I realized that the article was mostly about how GraphQL keeps you from going into technical debt. That was the main thing I took away from these sessions with Simona and it was coming out in the post, so that's the angle I went with. Once you figure out what exactly it is you are trying to say, articles nearly write themselves.

Whew! That's a whole wall of text and part of me is sorry you have to read it, but another part of me is just hungry for peanut M&M's. Priorities.

I work on a Mac. That always strikes people as funny since I work at MSFT, but it's not uncommon to see Macs around.

Hardware

• Macbook Pro i7, 16 gigs
• Apple Bluetooth Keyboard
• Magic Mouse
• 27 inch cinema display
• Beats Studio 3 Wireless headphones (They are the best headphones and I will defend this with my dying breath)
• Yeti Stereo Microphone
• Rode Mic Arm
• M&M dispenser. Late 90's model. Peanut M&M's only.

I have a Uplift Desk standing desk that my wife bought and had a top custom made for me. I don't use the standing feature, but other than that, it's great.

My chair was like 99$ on Amazon. I'm probably going to regret that someday when my back goes out. I'll let you know.

Here's a pic of my desk my work area. I don't know if these comments support Markdown images, but let's give it a go.

Software Probably the usual, but here is what I use most often...

• VS Code (not Insiders. I'm not a risk taker.)
• Chrome (i can't quit the devtools)
• Sketch (best image editing program for Mac. Period.)
• Slack / Teams (We use both)
• Outlook for Mac (I love it. Some people don't. They are wrong)
• Snagit (Buy this. It's worth it. You can easily grab any part of the screen as pic or video and convert to GIF.)
• Sizeup Window Manager (This tool lets you set a custom window size and I record the screen a lot so I need windows that are EXACTLY 1280 x 720 or what have you)
• CopyClip (Clipboard manager. Just lets me access my clipboard history, like, indefinitely)
• Azure Data Studio (for connecting to things like SQL Server, Postgres, what have you)

Sorry I didn't provide links to all of those. I got lazy. I think I need a cheeseburger.

Hi Milica! Great question, let me see if I can answer it without rambling myself into a ditch.

I work remotely (from home), so I generally start at around 7:00 and go to around 5:00. I find that I am most productive first thing in the morning and then after 3:00 PM. In between is a lot of meetings and other interruptions that make it hard to stay focused.

First thing in the morning is a time for working on whatever I really want to get done - blog post, demo, talk I'm working on - ect. I work on that until around 10 AM when everyone starts to come online and then a lot of my time gets sucked up with meetings and communication. Since a lot of us are remote, we tend to overcommunicate with each other to stay connected.

I eat lunch at my desk and then go for a jog around 2 in the afternoon. From 3 to 5 I'm back focused again and I've shut all my chat programs down.

That's pretty much it, unless I'm traveling and speaking at conferences. In that case, I sleep until the last possible moment and then wallow in anxiety in my room about my talk.

Plugins are available for outsiders. They have all access - super premium's premium member. Why to have plugins?

All we need to have plugins because, we use CE of VSCode. If you use paid version then you might be feeling even better.

Hi Simon!

Other editors? What is "other editors"?

I keed.

Uh - let me check and see...

The only other editor I have installed is Visual Studio for Mac and I don't believe I have ever used it.

5 things I hate about VS Code? Do I have to? This is like saying "What are 5 things you hate about your spouse"? Well, there may be some things, but I'm not gonna admit it! 😉

Ooh! This is a great question!

I think that GraphQL is not a REST killer. It is a REST saver. It shouldn't be the things that replaces your REST API, but rather the thing that sits in front of it and keeps you from having to change it all the time just to get the right data in the right format to your front end. In other words - it's the thing that is going to keep you out of technical debt.

I wrote about this just this week along with some video tutorials for anyone out there who is new to GraphQL like I was and wants to understand how it fits into the applications they have today.

medium.freecodecamp.org/why-graphql-is-the-key-to…

Hi Jill!

I did notice that your question was first yesterday. I don't have a prize for you, but you can tell everyone you know that you were first and I will verify that you WERE.

My energy comes from Goo Goo Clusters. Lots and lots of Goo Goo Clusters.

When we are filming, I am "on". Meaning it is a performance to a degree. I am not that chipper in real life all the time. And being on like that for extended periods is exhausting. We film 4 - 6 of these things in one day. The last time we filmed, I was in bed by 5 PM. That might have been a Goo Goo Cluster overdose though.

I do get quite intimidated when I talk to certain people - especially if they are extremely high profile. But the camera is sort of an equalizer. People are uncomfortable when the camera is on. They aren't sure how to act, where to put there hands, where to look - ect. So the awkwardness of being together on camera is sort of a bonding thing that helps me be less afraid that I have no idea what I'm talking about.