Listen "29: The Why & How"
Episode Synopsis
Special thanks to Digital Ocean for sponsoring this week's episode!
Head on over to http://digitalocean.com/doesnotcompute and you'll get a 1gb droplet for free for an entire month. Again, that's a free ssd backed server with a dozen one click installs available for free.
Things Mentioned
Sean's (current) Favorite Tools
Vue.js
Statamic 2
Rails
Hapi.js (Node)
Linting
Gitlab
Gitlab CI
Drone
Circle CI
Why you should enforce Dangling Commas for Multiline Statements
Listener Question
I'd like to know how developers can better provide input into a job spec/set expectations. When a client says "We need x, y and z" is there a way to say "yes, no or maybe" without spending an hour diving into docs or building a prototype. - @kidqueb
Paul: first off, if doing that is part of your job, you should absolutely have the time to spend as much time as needed figuring out actual requirements and deliverables. Too much pressure on people in this way would make me look at company culture problems, not at individual devs.
Make sure that projects are scoped out as much as possible up front - If you have any questions, ask them.
Project postmortems - It's beneficial to take some time after each project to analyze what went well, what what didn't, and why. If you don't have whys, it's harder to get the how's.
Time - It just takes time to gain experience. Soak up everything you can from others around you, and seek knowledge.
Learn how to read documentation efficiently - this will make getting the gist of something much easier.
Search support forums. For example, if you're needing to learn something about Shopify, check out the support forum. You'll find out the real details that the marketing pages don't spill.
Previous Show Notes
If you're looking for a link we've mentioned in the past, head on over to the Does Not Compute Show Notes repo and use GitHub's excellent search tool!
Join Us On Slack
If you've enjoyed the show so far, reach out to us on twitter at @seanwashington and @paulstraw, or join us in the Spec.fm slack community at http://spec.fm/slack!
Leave us a review!
Last but not least, if you haven't rated or reviewed the show yet and you'd like to do us a huge favor, you can do so by clicking here!
Head on over to http://digitalocean.com/doesnotcompute and you'll get a 1gb droplet for free for an entire month. Again, that's a free ssd backed server with a dozen one click installs available for free.
Things Mentioned
Sean's (current) Favorite Tools
Vue.js
Statamic 2
Rails
Hapi.js (Node)
Linting
Gitlab
Gitlab CI
Drone
Circle CI
Why you should enforce Dangling Commas for Multiline Statements
Listener Question
I'd like to know how developers can better provide input into a job spec/set expectations. When a client says "We need x, y and z" is there a way to say "yes, no or maybe" without spending an hour diving into docs or building a prototype. - @kidqueb
Paul: first off, if doing that is part of your job, you should absolutely have the time to spend as much time as needed figuring out actual requirements and deliverables. Too much pressure on people in this way would make me look at company culture problems, not at individual devs.
Make sure that projects are scoped out as much as possible up front - If you have any questions, ask them.
Project postmortems - It's beneficial to take some time after each project to analyze what went well, what what didn't, and why. If you don't have whys, it's harder to get the how's.
Time - It just takes time to gain experience. Soak up everything you can from others around you, and seek knowledge.
Learn how to read documentation efficiently - this will make getting the gist of something much easier.
Search support forums. For example, if you're needing to learn something about Shopify, check out the support forum. You'll find out the real details that the marketing pages don't spill.
Previous Show Notes
If you're looking for a link we've mentioned in the past, head on over to the Does Not Compute Show Notes repo and use GitHub's excellent search tool!
Join Us On Slack
If you've enjoyed the show so far, reach out to us on twitter at @seanwashington and @paulstraw, or join us in the Spec.fm slack community at http://spec.fm/slack!
Leave us a review!
Last but not least, if you haven't rated or reviewed the show yet and you'd like to do us a huge favor, you can do so by clicking here!
More episodes of the podcast Does Not Compute
285: Purpose Fulfilled
05/08/2021
284: A Good, Practical Tool
23/07/2021
283: Drew Clements
16/07/2021
282: Off That Plateau
08/07/2021
281: The Vagaries of Unicode are Boundless
02/07/2021
280: Always Be Pivoting
22/06/2021
279: All Roads Lead to JSX
16/06/2021
277: This is an Abomination
04/06/2021
276: A Conversation of Tradeoffs
27/05/2021
ZARZA We are Zarza, the prestigious firm behind major projects in information technology.