I haven’t been creating all that many blog posts here in the past months. It’s not that I don’t enjoy it, rather it’s more about the shape of my posts. As I analyzed a while ago, the average length of my blog post tends to be close to 2,000 words these days. They take quite some time to produce.
Sometimes less is more when it comes to words. Let’s look at one medium that is famous for its strict limit on the number of characters: Twitter. Max 280 char tweets are quite an enjoyable format for me to write in, too:
There’s a middle ground that I have been experimenting quite a lot with recently. LinkedIn posts with their 3,000 characters give enough room to express your thoughts without a compression algorithm. At the same time, it’s short enough that you will want to just open up the box, type whatever is on your mind about the topic right there & then, then click “post”. No planning needed, unlike with blog posts that may sit in my drafts folder for months.
A challenge with these social feed posts is that they are quick to post and they also disappear almost as quickly. I personally like to reflect on my past writings, be it via referencing old blog posts or viewing old tweets as a “this day in history” type of a digest via Timehop. LinkedIn posts don’t have any natural format yet for such reflection, so I’ve decided to manually create it.
This blog post is a collection of texts and images I’ve shared over on LinkedIn during the past 3 months on all things Power Platform and low-code. I don’t yet know whether I’ll create more of these Thinking Quarterly digests on this Thinking Forward blog. It’s all just about me experimenting with the tools and channels, to discover natural ways for both thinking fast & thinking slow.
I’ve grouped the posts under the following headings:
- Low-code
- Power Platform solution design
- Power Platform governance & administration
- Other Microsoft products
Low-code
Lessons learned from building big apps with low-code: [view on LinkedIn]
Why there will be more potential citizen developers in the organization than most (especially in IT) think: [view on LinkedIn]
Power Platform solution design
The concepts of declarative vs. imperative functions in Power Fx help in understanding how this low-code programming language can be used: [view on LinkedIn]
In Power Apps canvas app, the concept of a preview feature is quite different than the general MS guidance on Power Platform level: [view on LinkedIn]
Why “export as managed” should not be the default option in the solution management UI: [view on LinkedIn]
Dataverse legacy connector deprecation for Power Automate & Logic Apps, what you should know: [view on LinkedIn]
Power BI quick reports feature significantly lowers the barrier for analyzing Dataverse data from views in Model-driven apps: [view on LinkedIn]
Collaboration Controls are bringing Microsoft 365 services more deeply integrated with Power Apps: [view on LinkedIn]
Power Platform governance & administration
The governance challenges with Power Platform Dataflows: [view on LinkedIn]
You can change the environment in which SharePoint form apps (aka “special” Power Apps canvas apps) are stored to be something other than the Default environment: [view on LinkedIn]
Automatic deletion of unused Dataverse for Teams environments can soon be set via a policy: [view on LinkedIn]
Requesting IT approval for apps to be added into Microsoft Teams can now be directed into a proper request management system with new configuration options: [view on LinkedIn]
Azure AD B2B guests have been enabled as guest makers for Power Apps: [view on LinkedIn]
What you might not know about Power Apps / Dynamics 365 security roles: [view on LinkedIn]
CoE Starter Kit will no longer support Dataverse for Teams environments: [view on LinkedIn]
Other Microsoft products
MOCA, the Modern Collaboration Architecture definition by Microsoft, contains an interesting positioning of Power Platform vs. Dynamics 365: [view on LinkedIn]
Microsoft Docs is dead, once again: [view on LinkedIn]
What might be the next apps for Microsoft Viva suite: [view on LinkedIn]
(Header photo by Patrick Tomasso on Unsplash.)
Leave a Reply