I build "no code" solutions using MS SharePoint and Nintex tools, and they involve programming concepts (loops, variables, arrays) and development concepts (debugging, testing, agile). I use a few front-end markup hacks here and there, but it's mostly done without actual code. How could this background be made relevant to product management jobs? Possibly even junior dev jobs? Or is this background too far removed from coding with actual languages (Python, Ruby, etc.) to be relevant? Thanks for the help!!
Your skills would be most useful if you were starting your own startup and needed to make an early prototype to show to investors or potential cofounder developers.
Your experience in debugging, testing, and agile, could help you get a job as a product manager, and the fact that you have a background in some sort of 'coding' will help too. It's very unlikely that it would help you get an actual dev job though, since you wouldn't be able to translate your programs into actual code that could be taken over/continued by other devs. Even if the programs you mentioned do allow you to export as code, it's unlikely that it would be exported in a way that's very usable by other devs.
I think you'll really struggle. Despite my title I still spend a lot of spare time coding, attending and speaking at tech events and was a coder for 30 years. I have also worked in product ownership roles too. The reality is that not only will you struggle to convince coders, you'll turn them against you because you use what the industry often regards as "Doodleware". It's the same attitude that buffets tools such as TIBCO AE, WSO2, NeuronESB etc.
You have to understand some of the key aspects of the mindset. Despite the very intellectual nature of the role, many software developers are extremely irrational, short sighted and a lot dimmer than the role and the reward's they're paid would have us believe. Many see their roles as crafts and as someone who tried to push the industry into true engineering lines some 20 years ago, trying something genuinely new, but too far outside one's natural paradigms, as a cohort, doesn't go down well at all, even from within it's own ranks. It's taken that long for some of the concepts I was talking about back then to start to permeate software development today. They're human after all and have very much the same concerns every other human has, but also with a unhealthy dose of prejudice to go with it.
Taking ESB's like the above as a part of an example. Many ESB's have build in routing and workflow configuration tools and have a sweet spot where their delivered value overtakes direct connections, including those of [badly engineered?] microservice architectures. This is due to the combinatorial complexity (or rather the explosion) of such connections, make change more cumbersome the bigger it gets, since they have to change up to O(n-1) connections to other services. By comparison, ESB solutions with workflow designers can make such changes in O(1) - There is no growth to that complexity. Configure a single new transformation and go. Similarly, workflow design is just reroute, and publish. That said, even here, aspects of Test Driven Development/Behaviour Driven Development are still necessary.
From a product owner's perspective, this carries unbelievable value, since it lowers the skill bar required to participate in the change (so QA's, designers, BA's and even product owners themselves can do to) making ongoing change substantially faster, easier, less risky and 'multi-skills' everyone as good as overnight. Otherwise to reduce the "Bus factor" risk alone, they'd have to find and recruit people with that skillset, taking time and money and for niche tools, this carries a high probability of failure and high cost in wages or contract rates. Having a workflow or configuration tool to do the job ups productivity massively. If you have developers who truly mean they deliver valuable software, they'll understand that's value. However, with all due respect to my colleagues in the industry, many say it, but don't mean it or understand it.
This sort of tool is a direct attack on revenue streams and someone's livelihood, though that will never be admitted. So you have to be mindful of that. I go through challenging conversations all the time, with both sides of the divide, mainly because I am almost "allergic" to waste. I have no issue having such conversations when needed and the same process happens.
1. Tool is touted as a solution by managerial teams
2. One developer is chosen to try it out (note, foisted upon them)
3. Developer begrudgingly uses it, doesn't get the wider benefits, presents an argument either to dismiss it or accept it "passive-aggressively"
4. Product owner, Manager, EA or whomever mandates use of the tool, effectively taking credit for the devs work
5. Devs use it, hate it, don't use (or attempt to use) it effectively, and it gets a groupthink of frustration
6. Tool is rejected
The answer is usually to allow developers to come to the conclusions themselves. There is almost no way of doing it otherwise. It almost certainly means your skillset won't be valued and in some case, it'll be laughed at.
As an example, ESB's are shunned (even the free ones like WSO2) in favour of MassTransit, which is more lightweight but if you visit the sites, you'll see requires code to change it. That means lower ubiquity (the world is bigger than software development) and it has to be built into the Continuous Integration/Deployment process and tests have to be written for everything from the routes to Automatonymous (the state machine). So it's not quick and for others, it's not easy.
Make no mistake, MassTransit is cool, I really like it with my coding hat on, but in reality all the problems it solves have been solved before. Many people say WSO2 etc. are not testable, which couldn't be further from the truth. They just don't have the skills to test it and "cargo cult" their objection, as this hits ego massively. There is of course, the automatic objection to vendors, especially high priced ones, thereby potentially iring them with your Sharepoint skills too. So be mindful of all of all of that.
Happy to discuss it on a call if you need more information.
You asked 2 different questions:
1. Will it impress hardcore coders? No. Never. We could be impressed by what you achieve without code, but we wouldn't respect you as a developer. You're more of a crafty product developer, which leads me to...
2. Could it be made relevant to product manager jobs? Yes. Absolutely, because product managers don't need to be able to code, they're not hired by coders, and most don't know how to code at all. What you're doing would be considered product prototyping, or concept proving.
I'd agree with a few of the answers you got.
All applications are done with code, even generated code. You're showing some level of technical skills that and some point could translate into businesses and roles. In businesses, we are here because we need people to help us move projects forward, solve solutions in any creative way and bring results. We appreciate our team have and understand that mindset. In your situation, you cannot 'compete' with any hard code 'expert' with lots of years of experience, but, who can be an expert today? in this so changing tech era, in where code , frameworks, business models integration and blah blah always popup. So, one thing for sure is learning and understanding, and, actually, following methodologies, basic fundamentals, techniques, and strategies that seems to work (general concepts about programming and how it relates to the type of project you are working on) - and this case may be hard for you knowing you may find yourself really limited.
You may not get into organizations that already have their requirements up front. But, there are flexible organizations and s/m businesses, start ups, that application requirements are so open - they want someone to help bring the idea up. Tehy need a piece of sotware that can integrate with their main software smoothly. To test, or to even run with law strategic features, who knows you can't do it?
Yes, I can see a path into junior dev roles. Even though you use automated platform to create apps, internally they are using one of the languages you mentioned, or a couple of them. It is relevant? for product improvements, for calable applications, for security and for performance, e.g. Yes! it is relevant to understand how all those pieces work together. But most of the time, you don't work alone. That is part of working with a good team.
Programming and development is a changing evolving career, in where there is constant improvements - in where you also find people too stuck and really closed minded. There are organizations for each situation -there are organizations who allows working in pairs. And In talking about methodologies to use, it is a good topic to learn from as well. Go as you feel fit and are able to bring something to the table. I am in Seattle, and there are few organizations I know some people get into them not because of hard coding experiences, but who have worked on passionate projects in where they did some sort of coding and offer a solution for a problem - that sells! sometime. Prove what you can do. When the business has or make money down the road, then they will strategize on how to address their technical needs and departments. At first, many startups don't even know where are they up to yet.
@Horace Nelson's answer is absolutely spot-on!
In my opinion, this is what you should take from all the answers on this question.
A product manager / owner who can actually understand a prototype? That's pure gold. Go agile, immerse yourself in the tech culture via weekly meet-up groups and industry blogs, and you're there.