Long story short:
A few years back, Rever Inc which is a well established Silicon Valley-based company developed an Idea Management Software named Rever Score. At that time, they have their product up and running with the Angular 2 Beta version 9. Unfortunately, for them, the release of Angular final version was delayed by Google and they realised that waiting more would be a waste of time and resources. Henceforth, it took them 8 more weeks to abandoned Angular and re-write the entire project with VueJS.
Imagine your 1000’s hour of hard work goes into Vain just because of a unfortunate incident like this one.
When it comes to hardware product development, cost is one of the most critical factor that drives decision making in most cases. In this blog post, I am exactly going to show you how you can save more than half a million dollars on IoT product development.
“That would’ve saved us a lot of money. We didn’t knew that”
I’ve met many startup founders and enterprises that share their stories of how they could have potentially saved hundreds of thousands of dollars if they knew the “right stuff” when they were building their product. Read More
When it comes to the serverless providers, there are many popular opinions based on various biases. However, while choosing the serverless there are many things that go on than the surface picture.
Considering how critical this is for the long-term success, platforms should be evaluated based on their functionalities and service integrations. The potential backlash of choosing a serverless platform is high. Some of them are vendor lock-in and data lock-in, as Patrick Debois, CTO at Zender, mentions in his tweet.
So how do you select the right serverless provider? The answer is in this article. Here we discuss the major serverless provider considering their technical empowerment which will help you to equally weigh the selection process directed towards your specific needs.
You are probably looking at GPS tracking systems for vehicles, likely because you want to:
- Leverage analytics to streamline operations
- Make remote operations more transparent and easy
- Instill new insurance models to lower risks
- Eliminate revenue leakage with connectivity
- Reduce theft
- Increase operational transparency
This list goes on… Read More
Functional testing is a practice that delivers huge benefits to the development process. When done properly, it increases the communication between analysts, developers, and testers. The progress of the entire project is objectively visible at any point in time to management by examining the passing (and failing) functional tests. Eventually, the speed of development increases because well-communicated requirements result in less re-work. The tests also drive a more modular architecture with subsystems that have clear responsibilities.
This blog specifies the scope of different functional testing types, its importance and when to perform. For example, smoke testing is performed on each build delivered to QA because it verifies the functionality at a high level while regression testing is performed when bugs are fixed in subsequent releases. Read More
Few readers of my previous blog on Unit Testing had different opinions on the utility of unit testing. Some went on to say that unit testing is a huge waste of time because these tests involve mock objects, calling mock methods and functional testing is what really helps to find real-world bugs.
I strongly believe that unit testing has its own place in the software development lifecycle but the results are implicit in the form of code quality. When we talk about delivering quality software, functional testing has the highest ROI since it is done with real data. Functional testing verifies that the software performs its stated functions in a way that the users expect. Read More
I believe the study of the cost is no longer restricted to procurement. It is an integral part of the software architecture activity. It is important for the solution architect to understand the cost (visible and hidden) implications of choosing a particular technology.
Software architectures designed on abstractions like containers, orchestration and more recently serverless (FaaS) increases the development velocity and reduces complexity and cost. But the cost of running an application depends on many factors such as the choice of database, application adoption, hosting etc.
Thus the complexity about the cost of an application implies that the organization can’t rely on their development teams to make that decision and needs a hands-on decision maker. Even though AWS Lambda Pricing is pretty straightforward but the cost of running a serverless application is complex and involves many challenges.
A lot has changed since I started building apps, we previously used to almost rebuild a server 15 years back, then came cloud infrastructure services using which we could simply get pre-configured connected servers to get started with.
However, it still required us to write a lot of code (for good). Read More
Throughout past 1-2 years, React has matured as an UI library and with that – lots of best development practices have evolved over the years. However, it’s possible to run into performance issues in a large web applications, if you don’t employ best practices and ignore the internal architecture of React.
In this article, I am going to cover some strategies that are extracted from thousands of programmers and agencies who have faced some kind of React performance issues in past.
This article is going to be more about building IoT prototyping and help your startup or team to get there properly. But, if you need help tackling the complexity of mapping user needs as a product manager, here’s an amazing read by Daniel Elizaldale.
Hardware is difficult!
Netflix, Mapbox, A Cloud Guru, BlackBoard, Conde Nast, and New York Times. Do you know what these companies have in common?
All migrated to serverless architecture and have immensely benefitted from this decision.
At the recently held ServerlessConf, ‘A Cloud Guru’ gave a proof of serverless promise saying they were never required to change their architecture due to performance reasons. They are running 287 Lambda functions, 19 microservices with 3.68 TB of data at the mere cost of $580 per month. Read that again!
We all are well aware of how serverless helps in elevating our focus to more business-critical tasks by empowering developers and offering cost-friendly solutions. However, we have still observed confusion among people who want to get started with serverless adoption but don’t know where, when and how! This blog post is about them.
Let’s start unfolding each of them with practical examples and benefits it brings to the organizations as well as development teams. Read More
If you ever thought that
“All my app does is to communicate to the server. Why should I design it for an offline experience?”
You really need to think twice! Read More