For any digital product, a website may either work as a well-oiled lead generation machine or slow down business growth if the execution is mangled.
Imagine you’re on a long trip and want to pass the time doing something pleasant. Or you’re on a business trip, visiting your client’s offices. You pull up your favorite mobile app or one that you need to do business (one app could be both of those, though) and… it fails for good, refusing to work properly due to the Internet connection being spotty. So, you either do overtime waiting for websites to load, decide to give it a try another time, or at least get frustrated with the whole idea of websites.
It happens in the lifecycle of every product—some dead or duplicated code is slowing the project down, the team working on that particular product has changed, the technology and practices used have become outdated or obsolete. Over the next couple of years, the app evolves in an undesired way, getting bigger and scarier, and eventually you end up with a monster app that becomes difficult to handle.
Sound familiar? Believe me, when you work in a software development company, you see this kind of thing happen a lot.
Having an AngularJS app in 2018 probably means one of two things: either the app has been abandoned and isn’t really used or you’ve been thinking about migrating to another framework, but the time and costs that would entail have been prohibitive enough to have prevented you from drafting a roadmap for moving forward.
Node.js is still on track to take over the open source community. Big players from multiple enterprise-level organizations are either implementing it or considering it for their next platform. LinkedIn, Mozilla, Netflix, the list goes on. They all have bet on Node due to its scalability, performance, and twice-yearly releases (including one annual long-term service release).
Its growing popularity, however, does not necessarily mean that everyone should go with Node right now. After all, it shouldn’t matter how popular a technology is or whether one name seems more familiar than another—what should matter is making educated decisions about your stack.
GDPR issue hasn't stopped being a subject of debate for many digital business yet. Although many European-based companies took actions to become compliant before 25th of May, a shred of doubts stays.
In order to help you rest easy, we drafted a Q&A list comprising the most burning questions you might have as a digital business. Although there's no universal checklist applying to all cases, some issues pop-up more often than others. And these answers will be relevant for the years to come, since GDPR is not going anywhere.
Although nowadays we’re swamped with knowledge on more or less any topic we can imagine, it can still be hard sometimes to find reliable sources. In every industry, however, there is always a handful of individuals who really know their stuff and following their social media outlets, blogs, and their presence on other platforms is probably the best thing you can do for your career. In case you missed it, Karolina already drafted a similar list of Vue.js experts to watch in 2018. Now it’s time for Node.js.
You know, truth be told, there’s more than a couple of IoT geeks on our team here at Monterail. In late 2015, we set up a Raspberry Pi-based smart office system at our Wrocław offices, a process that one of my co-workers described in detail in a separate blog post. Since nearly three years have passed since the installation of the system, and given that we’ve grown a lot during these two years, we’ve decided that it was time to introduce a couple of upgrades to the system and make our office even smarter.
This one particular deadline applied to every business based in the EU or working with personal data of EU citizens—and as May 25 is behind us, this means that the GDPR is now in force.
The new law has stirred a lot of discussions, revolving chiefly around big companies relying heavily on advertising like Facebook. The whole tech world has been looking at Twitter, Uber, Airbnb, and other big players that manage loads and loads of data in their day-to-day operations, to see what they’d do. The main question was: What’s in it for us and our businesses? Can we draw any conclusion from their stories and use them? Unfortunately, the answer, more often than not, was no.
Amazon Alexa, the popular voice assistant helping with everyday tasks, has become a best friend to many households in the US and elsewhere. The list of available features for Alexa, released by both Amazon and third parties, keeps growing steadily, but according to reports from January of 2018, that the total number of skills (apps) working in the US only 25,784. More vendors are looking to integrate their product with the voice assistant—currently, you can link it to your Gmail account, your calendar, phone, or even home lighting.