Polyglot Software Development

Caching - Are you optimizing before identifying the problem? (Part 2)

If your pages take too long to render, caching may be a solution but before you go all out and start implementing or improving it, ask yourself if there are other fundamental problems that need addressing first (which led to the issues in the first place).
 
#snowpal aws.snowpal.com learn.snowpal.com

When looking to make performance improvements, it is natural to look for that ”single” big problem. But, that’s hardly ever the case.

I've worked on making performance improvements across all tiers, and in a variety of ways within any given tier, during the course of my career and one thing I can say with a good degree of certainty is that it gets more challenging as you get closer to your goal. Reducing a page rendering time from 3 seconds to 1 second is a whole lot easier than reducing it to 900ms, then to 800ms, and then to 50ms!
 
#snowpal aws.snowpal.com

Keep your code DRY. As in, super DRY! Code duplication is a maintenance nightmare.

You have to make a conscious effort to keep your code base DRY. Every time you make a change, add a feature, or fix a bug, make an effort to find duplication and to determine design patterns. This will play a huge role in keeping your code DRY, and maintainable in the long run.
#snowpal aws.snowpal.com learn.snowpal.com

Libraries vs Frameworks (based on my rather loose definition of it!) - What’s your preference?

Some of us prefer a framework that offers a lot more than what we might initially want, while others prefer a library that is small and simple but offers the barest minimum. Based on that simplified definition, what do you generally lean towards?
#snowpal aws.snowpal.com learn.snowpal.com

Should you implement that next requirement now, later or never?

Before you implement something, ask yourself if it needs to be implemented at all.
#snowpal #softwaredevelopment #requirements
Subscribe to our APIs on aws.snowpal.com.

[Paid Course] Snowpal Education: Writing scripts to understand REST APIs

If you are building integrations, or leverage other API Providers to reduce your Time to Market, you are bound to consume a fair number of APIs.
When you do that, how quickly your team wraps their head around a brand new API is going to make all the difference between going LIVE in the next sprint vs one down the road. We use a simple tool that we created for one part of this purpose. Let’s explore it.
Purchase course in one of 2 ways:
1. Go to https://getsnowpal.com, and purchase it on the Web
2. On your phone:
    (i) If you are an iPhone user, go to http://ios.snowpal.com, and watch the course on the go.
    (ii). If you are an Android user, go to http://android.snowpal.com.

Is GitHub Copilot worth it?

I've been using GitHub Copilot for a few months now, and am ready to share my thoughts on it.
#snowpal
Subscribe to our APIs on aws.snowpal.com.

API Hubs. API Portal. API Platforms. What are some of the differences?

blobr, apiable, kong, and the list goes on... Let's understand the similarities and differences between some of the providers in the same space (of APIs).
#snowpal
Subscribe to our APIs on aws.snowpal.com.

How many developers does it take to build something?

That's a very generic question! So, let's take a hypothetical scenario and discuss that.
#snowpal
Download mobile app from ios.snowpal.com and android.snowpal.com.

What’s more difficult? Building something, or selling something?

Is it more difficult to build something than sell the same thing? Or, is it vice-versa?
#snowpal
Subscribe to our APIs on aws.snowpal.com.