2,379 karma · joined April 6, 2016
Writing documentation also seems to be a task you kick out to your junior developers that you'd rather not give more critical assignments to, which is backwards as can be.
We decided to structure our front-end application using Atomic Design which classifies UI Components in a hierarchy of Atoms, Molecules, Organisms, Ecosystems, and Pages. Pretty universally the definitions of these terms did not translate to many of our remote developers in other countries not only because of the language but likely they didn't have the same Biology education either.
This and other similar revelations have led me to always put myself in the shoes of anyone reading my code, comments, commit messages, and force myself to use simpler language whenever possible.
Great write up, though this gold nugget should be in a massive <h1> at the top instead of at the bottom underneath a whole lot of coding talk.
The more I interact and learn from businesses the more I'm convinced founders need to categorically stop writing code, buff up soft skills, and tirelessly hammer the business needs at near complete expense to software development. Yes some companies really are engineering first and need an engineer at the top, but most don't.
A practical example I ran into lately, we had a small system run on GKE and Google Cloud Loadbalancer and struggled to automate the certificate renewal process. Because the cluster/project was for an internal tool this automation was given a low priority and we still have to "manually" swap a certificate every few months (and if we forget to we get an angry slack DM).
TLDR; there are still many combinations of networked services that still do not ~easily~ support certificate automation, even ones you expect really should by now.
Did he though? Or did he send his servant to the market for him and chastise the servant if ever he over-payed by a penny or more?
It's a real stretch to try to add a moral imperative to Uber's price gauging. Speaking of historical references, why don't we mention Uber's history alongside this rich old man of yours?
There is a huge need for them to have abstractions which provide structure and consistency without being hidden behind too much magic. React in general, redux, and hooks, to me all work to fill this need in a way which is superior to alternative tools. Specifically you can learn how they work in ten minutes or less.
Of course ecosystem variety is critical and there are no doubt many cases where mobx, non-hooks, or similar implementations are the better solution.
I would LOVE to create a large curriculum in house that aims to teach non degree holding individuals these skill sets because it would have tremendous return on investment. Be we are a small company (<100) with limited resources that can not afford to have a six month on boarding process to Do it properly (and I am not a professor).
It is an unrealistic burden to any small or medium org to do what is required by your comment.
Pay no mind that:
> WeWork entered Japan when office vacancy rates were near a decade low. The supply has tightened since to around 1%, a level not seen since the 1990s, allowing landlords to raise rents, while requiring a deposit of as much as a year’s rent.
They've got a great new product too:
> The new Passport service would give tenants flexible use of desks, community spaces and meeting rooms, amenities for which visiting customers currently have to pay extra. The service is a work in progress, but if adopted, WeWork aims to set aside a certain number of desks at all locations for Passport users, the people said. The move is aimed at increasing occupancy, the key to making locations profitable.
And forget that:
> Moreover, SoftBank itself has been a big contributor to that high level of occupancy. The Japanese conglomerate and its subsidiaries take up about 20% of WeWork’s office space in Japan, the people said. Over the years, WeWork pushed its locations worldwide to attract corporate clients because those contracts are more lucrative and stable. But Japan had a higher proportion of enterprise customers from the start, beating the 40% global average.
There is also something about well-off individuals taking investment money to get a fancy office rather then bootstrapping and keeping all the equity/destiny of the company themselves that smells funny to me. I guess its "free money" but I have to wonder if the products would be better if it was sweat equity instead.
VPNs are not the type of consumer product you EVER want to have acquired by ANYBODY. Not by Google, or Facebook, a US company, a Russian company, a Japanese company, NOBODY. Was this not extremely obvious when the deal started to form?
You've made a lot of promises that nothing will change, but those are empty promises given the history of post-acquired companies, as well as the vpn market as a whole. You have a lot of work to do following up on those promises, and until you do you will not have the same level of trust as you once did.
But at the end of the day if you build and release an OSS project you should get to do whatever you want with it, like the use of emojis that was discussed in the postwoman.io project that came up last week.
My opinion is who cares, we should be discussing its technical merits first and foremost on a forum like this.