How come cmdlets don’t act the same – or better yet, why is the syntax for similar things different? When I run Get-AzureADUser -All, I have to append a boolean $true for it to work. I would expect the switch to return true, if I append it to the cmdlet in the first place. Comming from Get-MsolUser that is pretty frustrating and pretty hard to explain, when spreading the good word.
I hope you’ll ask a question, too! Visit here for info.
This is a request: treat this as an “Ask Me Anything.” I’d like questions from you. Ideally, ones you think I can answer, but given a running start I’m sure I can come up with some answer <grin> to whatever you might ask.
Back in… jeez, 2015, which seems like forever ago, I started DSC Camp. At the time, Desired State Configuration was brand-new, and there were very few people actually working with it int he ran world. I wanted to get as many of those folks in a room as possible (it was about 15) for a weekend, and just brain-share what we knew.
I’ve begun the long journey toward the 2nd Edition of Be the Master, slated for an early 2019 release. Yeah… a long journey, given that it’s a spare-time project.
For those of you who obtained the book on Leanpub, you’ll begin seeing the 2nd edition in draft form Real Soon Now, with periodic updates throughout 2018. The original 1st edition will remain available in Kindle and paperback format on Amazon.
If you’re interested in seeing the 2nd edition as it’s written, pick it up on Leanpub soon. The Leanpub minimum price will rise in March 2018. Prior to March 2018, Leanpub still has the complete 1st edition, which means you can download it and squirrel it away somewhere, so you’ve got a complete copy to work with versus the draft editions that will start appearing in March 2018.
The second edition will be released on Amazon for Kindle and paperback in early 2019.
All the news has been focused on are the “plunges” in the US stock market, with headlines pounding home the fact that “the stock market” has had “historic” drops this week. Before you sell off your 401(k) and hide in the basement, let’s consider some less-hyped facts.
Thought I’d share this quick excerpt from Be the Master’s in-progress audiobook. Spent about a day dialing in the audio to what I hope will meet Audible.com’s specifications, but if not, there are other places I can publish it ;). Enjoy, and hope you’re having a great weekend!
(BTW, comments are welcome about the audio technical quality and specifications, especially if you can make them actionable – e.g., tell me what to do to fix something. I’m not an audio guy.)
As I’ve written here before, I do believe that the current concept of “operating system,” at least with regard to servers, is on the way out. Not quickly, of course – these things take time – but faster than you might think. So I wanted to take a moment to perform a little thought experiment: what’s the minimum an “operating system” really needs to do? How much of our current “OS” thinking can we just ditch outright?
This is an excerpt from my new book, Be the Master. In the Part of the book this excerpt is taken from, I cover some of the often-unseen fundamentals of the business world. The idea is that being successful in life and your career is much harder if you don’t really understand the rules that drive so much commerce and culture.
Businesses have their own language, and if you’re going to be in business, it’s good to know some of the terms.
This is an excerpt from my new book, Be the Master, available now at Leanpub.
There’s a perception that you’re not “good enough” to teach until you know everything. Indeed, as I’ll point out later, adult education often starts with the premise that instructors must establish their superior knowledge in order to maintain authority over the class. As in Timothy’s story, however, a moment’s thought will show this theory to be false. Nobody knows everything, ergo, you know something that someone else doesn’t. It’s just a matter of finding them, and teaching them; you don’t need to be an “expert” in order to share knowledge.
This is an excerpt from my new book, Be the Master, available now at Leanpub. It’s the base for much of the book’s discussion, and so I thought I’d share it here.
There’s a story from the 1700s about a blacksmith named Timothy, from a small village not too far from Lancastershire in England. Timothy had joined the smithy when he was twelve, and barely big enough to pick up one of the heavy hammers his Master (who is not named in the story) beat metal with. His first tasks were largely custodial – sweeping out the shop, keeping the forge hot, and so on. Eventually, he was given small errands to run around the village, such as delivering finished goods to customers. By age seventeen, he’d grown enough to swing the hammers himself, and he helped his Master with basic pieces. By twenty, he was working on his own for many basic projects – horseshoes were in particular demand, and this smithy was known for the unique, hoof-saving designs that Timothy’s Master had taught him.