303 karma · joined August 9, 2017
It's a great way to fill a few hours while honing your skills and growing and learning too.
Do good works. Change someone's life - it's very rewarding.
There's a link to watch the launch live in the article.
That's some serious scope creep going on.
Project officials did not enforce proper code development practices, and there was insufficient testing of the software.
Sheesh, I wonder how much of the budget was burned on inflated admin fees?
What was the original budget?
Were there cost overruns?
Who got the tender, and why?
Where was the complexity that made it a $100M, decade long project?
This raises so many questions.
Their niche is indie music, plus it allows for artists to be more flexible on pricing. I think there are a number of parallels when it comes to ebooks and supporting authors.
1. What is the question? Too often, I found I was speaking about the topic, but not actually answering the question.
2. Wait, what is the real question? I try to take a moment and think about the question and what information the asker is actually trying to get.
3. Did I answer the question? Or did I ramble about unrelated minutiae?
4. Did I answer the real question? Or will there need to be follow up questions because I didn't get to the heart of the answer?
5. Did I actually make sense?
---
Whenever I have to answer hard questions, I try to write down succinct answers in less than 3 sentences. This helps me practice getting to the point, rather than my natural rambling.
The reason she applied for an $18 p/h role was simple: burnout. She'd been burnt out on long hours of grinding research and wanted something that allowed her more flexibility.
I gave her a shot, but she genuinely wasn't a good fit for the role.
In the end, she took a course on coding and is now doing quite well as a back-end developer in the Bay Area.
It was only a year after I quit that it began to make sense. Now I try to assume that people had good reasons for their implementations and I try to figure that out first.