All things software & product, honestly - FrontEnd, BackEnd, DevOps, ML - as long as we're solving massive problems.
My code is used by millions of users globally - Potatoes make me happy
Whew you got me with the grammar part, I realised i set "publish" to true before proofing it. So my bad there - no point taking this offline.
Can vouch that it does get dry when you continuously build for others, but some/many people drive energy from solving problems "the whole consulting world".
Surprising you'd say the agency devs are in it for money, considering most agencies tend to not pay market price for engineers, nonetheless you have a very valid point RE product engineers vs agency engineers. I learnt the difference in a hard way, but ideally if you get a team that understands the business model and you build transparency around it, its possible to scale. (Annoying part of any agency is that scale == headcount)
On the money with the Technical Documentation bit! 🚀
Pricing is always a tricky one, we've done fixed scope and kept comms restricted as well as done TnM, both worked well for us, and didn't at the same time. You just need to get good at understanding the audience and stepping away from a potential project if you know the client is going to be a brain drain.
Also much like Ady's comment, it would be great hearing from other agency owners on their thoughts on running their business.
We focused on only senior hires and I paid them well for remoting based on Canada standards.
I did not notice grammar issues. Paid Grammarly would have suggested improving your writing style. It's not my interest to call you out it (grammar or poor writing otherwise). You asked for feedback at the end of the article so I delivered.
All things software & product, honestly - FrontEnd, BackEnd, DevOps, ML - as long as we're solving massive problems.
My code is used by millions of users globally - Potatoes make me happy
Whew you got me with the grammar part, I realised i set "publish" to true before proofing it. So my bad there - no point taking this offline.
Can vouch that it does get dry when you continuously build for others, but some/many people drive energy from solving problems "the whole consulting world".
Surprising you'd say the agency devs are in it for money, considering most agencies tend to not pay market price for engineers, nonetheless you have a very valid point RE product engineers vs agency engineers. I learnt the difference in a hard way, but ideally if you get a team that understands the business model and you build transparency around it, its possible to scale. (Annoying part of any agency is that scale == headcount)
On the money with the Technical Documentation bit! 🚀
Pricing is always a tricky one, we've done fixed scope and kept comms restricted as well as done TnM, both worked well for us, and didn't at the same time. You just need to get good at understanding the audience and stepping away from a potential project if you know the client is going to be a brain drain.
Also much like Ady's comment, it would be great hearing from other agency owners on their thoughts on running their business.
We focused on only senior hires and I paid them well for remoting based on Canada standards.
I did not notice grammar issues. Paid Grammarly would have suggested improving your writing style. It's not my interest to call you out it (grammar or poor writing otherwise). You asked for feedback at the end of the article so I delivered.
And the feedback is always appreciated 😉 Gotta have that tight loop of feedback / execution