What's On Your Developer Radar?

Play What's On Your Developer Radar?

The Discussion

  • User profile image
    Always great to hear Richard Campbell and the topic is very interesting. You covered so many things, but I'd like to focus upon one of two to be my post short.

    Concerning APIs, I've seen their value for many years. In my previous job I wrote dozens of APIs so that a web or Windows client could consume them. The versatility of APIs is fantastic for them. But in my current job the culture is decidedly against APIs. I've no idea why; it just is. There is no API here and furthermore I get the strong impression that if I were to write some APIs, then there would be no effort to use them. Therefore, why bother to write an API when it will be ignored or worse, someone who duplicate the code in their own application that they write, thus making the API useless.

    Second, I thought that Richard's discussion of the Power Platform was interesting. You might be correct that the Power Platform, and competing technologies, are like what VB was like back in the 90's. But what do you do when you can't use them at all? Where I'm currently working all access to Power Platform, Power Automate, etc., were blocked. I don't know why. Perhaps cost is involved, but I don't know that for sure. At this point in an organization over 3500 people, only two have access to Power Platform. And they're both SharePoint developers. Certainly, it makes sense that SharePoint people would be involved, but I think that keeping the Power Platform aware from everyone else defeats the potential for what the Power Platform can bring.
  • User profile image
    @RodAtWork I fully agree with you that costing is probably a contributing factor. The company I'm working for has 10,000 people, but, when it comes to using new technologies, it's really falling back to individual department budget, instead of the costing for an overall enterprise strategy/solution. The problem for adapting an enterprise solution is that you're always working against the mentality of: If it's not broken, don't fix it. There're already too many IT projects selling new technologies with exciting, but forecasted, ROI, yet ending with failure. It becomes difficult for higher executives to say: how do I know the next one (Power Platform) would truly shine.

Add Your 2 Cents