Yeah I concur wirh this. Apologies if I've for the intent of this wrong but stand ups are intended to be a team sync point where questions are asked, mutual understanding reached and I doing a 1way update seems counter to the intent of a stand up.
It definitely has its place to provide opportunity where you can't all meet together but it you'd to rely promote questions and discussions following this by all team members to avoid it being a box tick
seems to me like the guy who started out as a one-man reseller host scaling out into something he's nowhere capable of managing.. scary to think how many of these are out there
What your describing is essentially a business analyst, albeit a technically minded in whilst not being a developer. I consider myself of the same ilk and I think the best thing you can contribute is input and UX/UI design, sanity checking of ideas, feedback from users etc.
The facilitation role between users and developers is so much more than 'documentation' which alot of the comments in this thread seem to suggest.
I suggest contacting a few of the projects listed here, or any you find on GitHub you'd like to contribute to and just offer to help.
that sounds like an interesting concept, similair to part of what something I am working would like to acheive. Are you providing a structure or allowing 'interviews' to be whatever form/structure the interviewer wants?
good luck, its a problem i havent seen solved properly yet!
isn't the point to block OTR. a core concept of both of them is knowledge capture and searchability which can't be done properly if your only having part of the conversation.
from reading the other replies in this read (and the above) it seems that the next windows server release will have ability to run both linux and windows containers.
ah nice, we looked into octopus at the time but was still early development days and was too much of a risk, otherwise pretty much the same stack. I can see what you mean re server config, would be a lot easier with docker than what i was hacking about with vagrant.
whats your current deployment strategy, series of powershell scripts or something chef/puppet based?
We had a powershell based setup and my previous shop but hardest part was maintaing and deploying different databases to make the tests relevant.
How do you think docker containers helps (as Im not sure it would have helped in my previous situation - too many other base issues to deal with first)
does this mean docker support will only come from wont come before the next drop of windows server? i.e. current windows platforms wont be docker-compatible
interesting - thanks for that. looks like your the author? Any reason why you went for notation-based rather than a drawing cavnas?
I'm thinking of putting together something very flexible and user friendly which can certainly do UML but not strict and the focus would be free notation with best practice to guide.
use case = purpose in this sense, so that answers the question., thanks!
ill have a look into it and see the techniques hes using here but it seems like a similair (although applied) problem domain to what im looking at.
Im looking at explaining / communicating complex problems, particularly developing software in enterprises with an already complex and not-well-understood environment.
Im currently in consultancy for financial services and getting anything either in as cloud-based SaaS or even a well-established vendor is a nightmare of risk assessments and red tape.
I think this type of tool is very valuable for a lot of these firms but the ones that need it will be the ones that have teams of people trying to block you. One answer might be SaaS-based but hosted on-site to avoid the security issues people have around having their IP in the cloud.
Best of luck!
seems like a really interesting concept, although I do think you might struggle getting that into the enterprise (or even medium/large business space) given the heavy installation.
Definitely going to see if it helps with me requirements of trying to unpick complex financial models built from spreadsheets.
I agree with your viewpoint totally - and others may disagree as they have a vested interest in encouraging consumers to share - but it is an trend that is becoming increasingly prevalent. I think your main point is that we are sliding towards the sharing-for-sharing's-sake end of the sharing spectrum rather quickly and perhaps without realising it, and that its something to be conscious of.
It definitely has its place to provide opportunity where you can't all meet together but it you'd to rely promote questions and discussions following this by all team members to avoid it being a box tick