Back at the start of my career I didn’t know how to code, but I got offered a role at a startup …
Back at the start of my career I didn’t know how to code, but I got offered a role at a startup after I came up with a solution of integrating google cals in a way that was crucial to the business - using Zapier. (The requirements were complex, but Zapier could handle it) This was after the outsourced dev team that built the company website said that it wasn’t possible without significant cost. Here comes me, not knowing how to code, pointing out a solution that cost a few pounds a month. During the next few years I built a ton of other solutions for the company using Zapier, to the point where we were running over 50000 tasks a month, easy. I learned how to code in the process (I now work as a software engineer), but I always consider low-code or no-code solutions when problems arise, because I’ve seen them save massive time and expense in a real world scenario, and working really well. It’s like the OP said in the end - we are problem solvers, and I would add that low-code/no-code tools should be part of your tool chest. …
Original discussionLow Code Software Development Is a Lie157 source comments · at import