57 karma · joined March 12, 2013
they continue to struggle to understand the digital era, and the executives have gone on record plenty of times in their own town halls expressing their confusion and dismissal of "that thing called the internet".
and while the CBC continues to compare itself to BBC at every turn, that is not a fair comparison, more like a toad contemplating itself a deer.
luckily, we're based in Canada, where anti-spam laws (CASL) apply.
we proceeded to contact them in social media / email to ask them to cease this activity and delete the collected emails.
they fought back at first, claiming it was legit and only would put emails under do-not-contact list, we did not accept that, again citing CASL laws, their actions were in clear violations. they stopped responding to our emails.
We have proceeded with a legal consult and have further contacted their legal representative for further action.
G2Crowd has been extremely un-cooperative, and seem to clearly lack understanding of laws and legalities outside of the US.
(edit: corrected some typos)
however there is no limit to how many containers you can expand to (to share the load/storage)
and that's also why we're offering the cold-storage option, so you can move your data freely.
furthermore, everything is accessible through an API as well, so integration and manipulation of your data is a breeze
we'll also be exposing a cold-storage mechanism, so you can move historical data out of the system when no-longer needed and retain it for your own future auditing.
Django REST Framework (or any other framework) to build your business logic and API services.
Kong is useful to scale and manage acceess to the API for API consumers (as oppose to end users) as well as a plugin system that abstracts HTTP tooling away from your API application, so you can scale them independently.
making it open source is the icing on the cake!
we want to give the power back to the developer community and together create amazing open source tooling, while directly adding years of lessons learned to your development stack.
as for YAML, I think its best for human readability, rather than actual usage in libraries.
and I'm not talking about hiring a PM off the street then bestowing him/her with the "ownership" of a product they've never seen before! True Ownership comes from a self generated interest in the well-being of the product, its customers, the technology empowering it and its sustainability.
This does not happen overnight, and is certainly not a skill that can be taught.
The most successful PM I've worked with over the years had one thing in common: they actually CARE about the product AND about the users (clients). this generates an internal drive for excellence like no other, in both satisfying business goals, client asks, and technology roadmap, even though those three are almost never on parallel lines.
As to the original question, where did they all go? I don't believe the role in it self went away, but rather smart companies nowadays recognize that a set of skills and an Agile/SCRUM/PMP/etc certificate will not make you a "drop in" successful PM, but rather they rely on the internal champions of the products to help shape the story.
This means more developers are stepping into the role, and through the right level of support they can/are picking up the business/accounting/client side of managing a technology product.
Also, an important part of a Product Manager (Owner) role is relationship management and communicating with people (clients, developers, business owners, sales, marketing, support, design, etc ...).
Human interaction is unfortunately another one of those things that cannot be taught! communicating with people is so different from sending status update emails, or adding them to auto notifications from tickets in a feature tracking system.
Sadly, most of the PM I've worked with and from what I've seen, the industry actually encourages the automation, over the human interaction. yet another reason why this role is changing and is being redefined.
just my 2 cents.