markdown guide

I spent about 2 years working on a workforce management platform where we used some data science to tackle the 'nurse rostering problem.' Was a tonne of fun, and I learned a lot, especially about how a product can fail no matter how much you can prove it will save businesses money. Sometimes it's not a technical problem, it's a people problem.


Cool stuff, that's a good leason to learn!! I've seen that before as well.


In college, I started building a website for people to showcase the cool projects they build. While this is my coolest project by far, I have a portfolio of other projects I've built that's hosted on the site! (inception?) πŸ˜‚

Here's the link to the projects I've built which is hosted on the coolest project I've built: joinhelm.com/portfolio/5d6c7f9c19e...


In my case, we are developing a market/platform to create and share/sell bots and automation, this has been our playground at work for over 2 years, where we can play with tech and develop cool tools for it.

I once made a little phone simulator, In the dashboard of our Platform a phone screen appeared, there you could interact with it like a normal simulator, and it recorder the automation so it could be then reused or sold in the market.

We also made a graphic editor for linking bots between them and making even more complex ones. This generated a custom language (just for fun), we ended up rejecting this approach, but was fun nevertheless :)

Classic DEV Post from May 21 '19

Ten Cognitive Biases to Look Out For as a Developer

Cognitive biases can be viewed as bugs in our thinking. In this blog post we want to take a look at ten cognitive biases to look out for as a developer.

Manolo Edge profile image
I work a full-time job, maintain a couple of libraries of my own, try and contribute to open-source and write occasional posts :P I can also handle spice O(1)

dev.to is where software developers stay in the loop and avoid career stagnation.

Sign up (for free)