There's a spec, my collegues work along that spec and I can use their interfaces.
I don't see how IDE and/or editor preference could have any impact on that. When you run into a problem, now you are the problem because no one else can help you and you're working on x,y,z feature and you're stuck Workflows may be similar, but the moment you fork the road, when you run into a problem, now you are the problem because no one else can help you and you're working on x,y,z feature and you're stuck. If your toolchain/kit becomes extremely esoteric, every time you do something, it's magic to those around you, and when you fumble on something no one is there to offer assistance because you've taken the contrarian workflow that sets you apart from everyone else. I can only hope if you work with others, if someone ever has to observe your workflow, they can atleast walk away saying, hey, I learned something I can use within my toolchain/kit/etc. They have standardized on a very specific workflow, everyone who uses it learns it from those around them. Not to say that you or I work for facebook sized companies, but as developer count increases, standardization becomes more important. In an already established environment, this could be regressive. Tools & instructions are often times handed down. Example: every time you make a change on your local system it gets uploaded to your work-environment in a similar fashion that you would have had on say a vagrant installation, instead you push to remote system. Toolkit integration become very bound to workflows in code-bases. I've seen where processes become very dependent based on what ever editor/IDE being used is.
I'm not going to claim I'm an expert by any means.
0 kommentar(er)
