Website content, design and layout are three pillars web accessibility leans on. Team members responsible for these components - content editors, designers, developers - have to preach and consistently implement accessibility guidelines and standards. In turn, the responsibility of a quality assurance engineer is to prove whether they succeeded or failed in making a website accessible - both for humans and assistive technologies.
Equal opportunities for everyone offline and online are the 21st-century must. Web accessibility refers to a set of inclusive practices and guidelines to make interaction with any website possible and convenient for all people, including those with disabilities. In our previous article, we defined key principles and best practices for making a website accessible. Here are a few practical tips to achieve this.
We discussed software licenses and gave a few tips for dealing with them in our previous article (check it out here if you missed it). This time, we decided to cover a few more intricate licensing questions, with the focus on free and open source software.
Software licensing is quite a tangled tale for startupers, digital product owners, and (shhh!) sometimes to developers and project managers too. Let’s wade through license types, terms and permissions explained in normal-people speak. This article would also give you a few practical tips for dealing with licenses. They should be helpful to everyone involved in software development process.
Apache JMeter is one of the most popular open-source tools for performance and load testing. In this article, we shared a few Logicify best practices, tips and lifehacks to make testing with JMeter even more effective and indicative of a web app performance.
The third article in “Logicify Monitoring Tools” series talks about Grafana, a software we use both for internal and external projects to visualize and analyze the data about system state and performance.
The first article in the series about marketplaces described how you could build one with a minimal features set. Now let’s have a closer look at further stages - maintaining and managing a marketplace - which are often overlooked or underestimated by business owners, and especially startupers. We still use Upwork.com, a global marketplace connecting service buyers and service providers, to showcase some best practices.
We continue the series of “what does it cost to build” articles in our blog. We analyzed multiple platforms popular in the web today and shared our findings and takeaways on how to develop and maintain a marketplace. The first volume specifically focuses on the definition of a marketplace, its typical features set and timing to build it.
We share our tips for knowledge transfer from software engineers to engineers. This article, we overlooked the cases when the knowledge should be shared with novices in IT industry, Quality Assurance specialists for testing or Technical Support for maintenance purposes. The tips are backed by our experience, so they could come in handy to CEO and CTO managing development teams - whether in-house, remote or both, for PM and software engineers.