tartieret

Does anyone knows any alternative simple open source MDM solution that works with Windows, Linux and Mac?

I still use Docker Swarm in production, but the main issue is the lack of support from cloud provider and tooling. For instance, there is no good solution like ArgoCD for continuous deployment and updating your stacks. In addition, if you want to be able to automatically add a new node to the cluster, you basically have to write some infrastructure code by yourself. This makes infrastructure as code / configuration as code a pain, and these things are required to be compliant with stuff like SOCII

it looks like an interesting concept, I would love to try it !

I work on B2B SaaS applications for medium/large industrial company and I don't think open source would improve your security posture for this type of client. IT departments have to evaluate vendors against a set of criteria and you pass or fail. if they are worried about the confidentiality of their data, then another approach would be to let them run your chatbot in their own cloud environment (or on premises).

this approach is appealing for a lot of companies. for instance, just looking at Azure, if you make your application part of the MS Transact program, then the client would simply pay their monthly/annual azure subscription and your license would just be a line item on it. this may seem pointless but large corp tend to negotiate deals with cloud providers and negotiate a better deal provide they spend a certain amount per year. if your solution helps them achieve this amount, it's very appealing

Beyond that, you can work on complying with SOCII or other programs

We leave on person on "support duty" outside of the sprint. One of my friend working at Amazon in a team of 8 did the same with 2 persons out of the sprint (one being "on call" and dealing with support & operational issues, the other one working on "improvements" voted by the dev team, like better tooling, better monitoring...)

On my side, working in a small team of 5, we just leave one person out of the sprint to work on support requests, bug fixes and if time allow improvements. Large handling of technical debt (ex: transitioning from VueJS 2 to 3, good luck expressing this as a "product increment" in a sprint goal and good luck if you don't tackle it ... ) are part of sprint work.

Overtime, I realized that Scrum is a framework, not a fixed set of rules, and as per Agile, the goal is to maximize business value. So if we are swamped by support requests and our systems are not operating properly, it's the role of the person on "support duty" to warn the rest of the team and ask for help. Sure it may impact some velocity metrics and we may not hit our sprint goal that week, but why would that matter? There is no point writing more code and building more features if what we have is not working properly and not satisfying to users.

The main issue i have seen with this system is that the developer on support duty may not have the right skills to perform all the work that is needed. Scrum relies on the assumption that anyone can do anything, and that's definitely a flaw when working on a larger codebase with a mixed of frontend, backend and devops with more junior developers. It does force us to train everybody and learn to delegate so that everybody can be exposed to all parts of the system but this takes many months / years.

We also learnt to define smaller Scrum goals. It's better to achieve a small goal and then decide what to do next than to always feel like we are running behind. The sequence of "two weeks" sprints is often seen as a "fixed" schedule with deadline to hold at all costs, but that's stupid. The core idea of Agile is to follow an incremental approach following the path of max business value delivery, and periodically reflect about how things are going. If the amount of support requests and operational issues is such that there is no more resources available for new feature development, then it's time to prioritize tackling some technical debt and improve monitoring and automation to prevent the most common issues

how secure is hoppscotch.io?

For sure ! Thanks for the advice

Thanks, all feedbacks are great ! :)

Panevo | Full-Time | Flexible Onsite/WFH (Vancouver) or Remote WITHIN CANADA

At Panevo we build data intensive applications for industrial IoT. We have two main products: - an energy management platform for industrial sites - a lean manufacturing application to detect production downtimes in real time and help improving industrial performance.

Our platforms are currently used by some of the largest industrial corporations in US/Canada, and we are looking for developers interested in building advanced analytics features and take our products to the next level.

Hiring: - Junior developer (full stack & frontend) - Senior developer (full stack or backend) - Machine Learning engineer

Tech stack: Python (Django), VueJS, Redis, Kafka, Docker. PostgreSQL, MQTT, Microsoft Azure: IoT Hub, Event Hub, Azure functions…

See the list of available positions here: https://www.linkedin.com/company/panevo/jobs/

You need a valid work permit in Canada (no sponsoring)

Apply through Linkedin or by email at thomas.tartiere (at) panevo.com