Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Explaining the stack externally #70

Closed
rub1e opened this issue Jan 2, 2019 · 3 comments
Closed

Explaining the stack externally #70

rub1e opened this issue Jan 2, 2019 · 3 comments
Labels
discuss Share your constructive thoughts on how to make progress with this issue help wanted If you can help make progress with this issue, please comment! priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished question A question needs to be answered before progress can be made on this issue technical A technical issue that requires understanding of the code, infrastructure or dependencies

Comments

@rub1e
Copy link
Member

rub1e commented Jan 2, 2019

It would be very helpful to have an "approved" blurb to help talking through #67 with potential clients/partners

More specifically, I'm keen to understand how to talk to potential clients about the modularity/reusability concept, and what that would mean about working with dwyl; why they might be interested in this way of working / what benefits there are for them; equally why it might not be the right approach for a client in a given situation.

Perhaps this could begin as a discussion and then I could distil the ideas into a written blurb?

Grateful for everyone's thoughts.
@rub1e rub1e added help wanted If you can help make progress with this issue, please comment! question A question needs to be answered before progress can be made on this issue discuss Share your constructive thoughts on how to make progress with this issue technical A technical issue that requires understanding of the code, infrastructure or dependencies priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished labels Jan 2, 2019
@rub1e
Copy link
Member Author

rub1e commented Jan 2, 2019

(P2 as I've got a call with a potential client next week)

@nelsonic
Copy link
Member

nelsonic commented May 7, 2019

image

Wow, this Spam account was registered 20 minutes ago and has already posted this helpful comment ...
image

Reported as SPAM:
report-spam
image

Sad.

@nelsonic
Copy link
Member

Our tech stack is a lot more focussed in 2022. ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discuss Share your constructive thoughts on how to make progress with this issue help wanted If you can help make progress with this issue, please comment! priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished question A question needs to be answered before progress can be made on this issue technical A technical issue that requires understanding of the code, infrastructure or dependencies
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nelsonic @rub1e and others