Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
I've some initial feedback (some better some worse) and a couple of questions though.
Disclaimer: For anyone reading this: I didn't tested the product (for now at least) so my feedback is just about the text above and a bit of information from livecycle website, hence I may be right or completely wrong.
Some things to clarify:
That's not a study, it's a report (a cooked data output from one or more surveys), not done by venture beat but by Retool and Wakefield. They asked to ~600 -allegedly- software engineers (then they proceed to say "including both ICs and managers", hence I'm wondering how many of those 600 are Software Engineers in truth), in conclusion, it may not be close to the reality.
As a Software Engineer your main job is not to code but to analyze, define and design. To ensure a good design you need a good definition, and to reach a good definition you need a god analysis, and a good analysis requires iterative communication. That's the reason for separating the terms software developer and software engineer. Every software engineer can act as developer but not every developer can act as engineer.
Of course devs don't want to involve in "Ops", it's fun to do it in your free time (maybe) for your side projects and so but those are tasks for sysadmins and not for developers, hence sysadmins are the ones acting as "DevOPS" in the major part of companies but that's an un-related topic with the rest.
We don't want to be managing communication protocols.
We don’t want to be doing administrative tasks.
We don’t want to be sending emails and updating Jira tickets.
We just want to code. That’s it.
You'll face some sort of bureaucracy in every possible job. Administrative tasks? That's a nope as response on my side.
Managing communication protocols? That's for management, not for devs. Sometimes software architects, Tech Leads and Team Leads need to jump into that side as well, someone need to act as "glue" or to ensure certain information reaches every corner of the people involved in a project and that everyone is aligned.
Sending emails and updating Jira tickets, in the other hand is part of the job, and it's an important and necessary part of the development project, like it or not and I assume that we're all adults hence we can understand the needs of our own job without cries and tantrums.
Some questions
While this seems a good idea
Once Livecycle is installed, anyone who opens the preview environment will not only see your work, but they can also comment on it, in context, on top of the product UI.
I don't really know how I feel reading it 😂😂
Will that means that people will annoy constantly in develop environment (which is NEVER an environment for people to test, neither a stable one)? Or will that be placed only in QA/UAT/Preprod environment? Which is a later stage and therefore the "catch things in an early stage" will became blurred and less useful.
What happens then with this feedback? Will it need to be copy-pasted into the project issues tracker hence increasing the bureaucracy? Or will livecycle act as issue tracker as well? If so, which integrations and capabilities does it have?
Good parts
I visited the website of livecycle and I feel that the most powerful features are those two:
If understood it properly, it will generate a preview per-commit or per PR. I'm wondering how many resources does it consume to do so but leaving this aside, I would love to have a preview for branch so, as you state in the text, other related departments can verify the developments.
Also, to toy around and maybe self-answer some of the questions above, does livecycle provide any free tier? Is there a way to self-host it or..? I didn't find a pricing in the navbar but the website does look like the product has a pricing 🤣
That seems a good base project to me! 😍
I've some initial feedback (some better some worse) and a couple of questions though.
Disclaimer: For anyone reading this: I didn't tested the product (for now at least) so my feedback is just about the text above and a bit of information from livecycle website, hence I may be right or completely wrong.
Some things to clarify:
That's not a study, it's a report (a cooked data output from one or more surveys), not done by venture beat but by Retool and Wakefield. They asked to ~600 -allegedly- software engineers (then they proceed to say "including both ICs and managers", hence I'm wondering how many of those 600 are Software Engineers in truth), in conclusion, it may not be close to the reality.
As a Software Engineer your main job is not to code but to analyze, define and design. To ensure a good design you need a good definition, and to reach a good definition you need a god analysis, and a good analysis requires iterative communication. That's the reason for separating the terms software developer and software engineer. Every software engineer can act as developer but not every developer can act as engineer.
Of course devs don't want to involve in "Ops", it's fun to do it in your free time (maybe) for your side projects and so but those are tasks for sysadmins and not for developers, hence sysadmins are the ones acting as "DevOPS" in the major part of companies but that's an un-related topic with the rest.
You'll face some sort of bureaucracy in every possible job.
Administrative tasks? That's a nope as response on my side.
Managing communication protocols? That's for management, not for devs. Sometimes software architects, Tech Leads and Team Leads need to jump into that side as well, someone need to act as "glue" or to ensure certain information reaches every corner of the people involved in a project and that everyone is aligned.
Sending emails and updating Jira tickets, in the other hand is part of the job, and it's an important and necessary part of the development project, like it or not and I assume that we're all adults hence we can understand the needs of our own job without cries and tantrums.
Some questions
While this seems a good idea
I don't really know how I feel reading it 😂😂
Will that means that people will annoy constantly in develop environment (which is NEVER an environment for people to test, neither a stable one)? Or will that be placed only in QA/UAT/Preprod environment? Which is a later stage and therefore the "catch things in an early stage" will became blurred and less useful.
What happens then with this feedback? Will it need to be copy-pasted into the project issues tracker hence increasing the bureaucracy? Or will livecycle act as issue tracker as well? If so, which integrations and capabilities does it have?
Good parts
I visited the website of livecycle and I feel that the most powerful features are those two:
If understood it properly, it will generate a preview per-commit or per PR. I'm wondering how many resources does it consume to do so but leaving this aside, I would love to have a preview for branch so, as you state in the text, other related departments can verify the developments.
Also, to toy around and maybe self-answer some of the questions above, does livecycle provide any free tier? Is there a way to self-host it or..? I didn't find a pricing in the navbar but the website does look like the product has a pricing 🤣
My worry as well 😅 this way we don’t get rid of the described problems at all, we only generate an additional set of 😫