This is a guest post written by Jocelyn Brown - freelance technology writer specializing in home and business solutions and developments.
Last Monday was very exciting. About 100 young women gathered in Monterail’s office to listen to our women experts from different fields—front-end, backend, QA, design, project management, and other roles. During the 2-hour event, we discussed possible career paths in IT industry and real life stories of getting there.
*In a medium sized software house in Wrocław, we’re currently looking for a new team member who knows how to design applications, network management tools, procurement or social platforms, and such. For those who don’t know, that means Digital Product Designer. If you want to know what qualities and skills you need to start working on such position (not only in Monterail), read on.
An aspiring entrepreneur I’ve recently consulted told me that she’s done coding. As she’s a great programmer, I asked her what’s wrong. She was a capable technical co-founder, but, as it often turned out, she was too quick to assume that her ideas would sell.
Many years ago I attended an architecture conference with my father (an architect and college professor) and he told me something interesting. We were leaving after hearing a presentation on “ecological architecture” and its advantages over “ordinary” architecture, and because I saw my father visibly wincing throughout the lecture, I asked him what upset him so much. He told me that he didn’t understand this “all eco-everything” hype and back in his day something was either good or bad. That if you took all the important aspects into consideration and did things right, then it was just “good design.” Nothing less, nothing more. No fancy names for processes or frameworks. Just you, your knowledge, experience, and attitude.
As I was contemplating the problem of few women in IT, I approached my friend Mateusz Sławiński, a Talent Manager here at Monterail. We had a long conversation that yielded some eye-opening (at least for me) conclusions. This blog is more or less a distilled essence of our conversation augmented with research that I had a lot of help with from my female colleagues. Thank you!
We know that for some people hardware devices plus Agile just doesn’t sum up. Agile may even feel a bit odd for hardware development, with all the tools and processes behind it. The problem is, hardware is often deprived of iterative development and therefore its release may be overwhelmingly stressful (and exciting for sure) for the company.
If you've ever been working on an application with a domain concept like organizations I bet you had to struggle with custom features, behaviors and complete white labels. Most young fellows start such with the if-else construction which quickly can fall into monster-spaghetti. Can we do better?