People in the comments as well as Julia in the article are mentioning breaking changes. I would imagine committing to a stable API and signaling this through a v1 release would show respect to the time of your users.
809 karma · joined September 28, 2011
https://github.com/DonDebonair
People in the comments as well as Julia in the article are mentioning breaking changes. I would imagine committing to a stable API and signaling this through a v1 release would show respect to the time of your users.
If Telegram breaks the law - which it does - it’s completely logical that the CEO is held accountable for that and is arrested
The author does not seem to require iterating over a sorted list. Sorting is not the same as ordering. An ordered map is a map in which the insertion order is preserved when iterating over the elements. A sorted map outputs the elements in an order defined by a comparison function when iterating, regardless of their insertion order. You can for example sort alphabetical in case of string keys.
And you are right, I don’t know anything about that code base, certainly not enough to know if estimates should be easy or not. But the fact that they aren’t is a sign of problems either way.
And I stand by my point that your boss’ question is reasonable, and the team should do some introspection to learn why such a fair question cannot be easily answered
Regarding capitalism favoring hiring for competence, I’m afraid history has not shown this. I’ve seen in my own environment that male candidates were hired where more competent female candidates were available. And this has been consistently shown throughout history. Minorities really did have less chances in the past, despite capitalism.
So I think the question is how we can hire for competency while giving everyone equal opportunities.
2. I’m not suggesting anything to make any problem worse. I was just observing why companies are over compensating. I’m not voicing any opinion on that. But if you want my opinion: we should remove bias from the hiring process as much as we can, either way, so that all candidates have equal opportunities
3. “WTF???” comes across as overly emotional and does not serve any purpose in a leveled discussion
The reasons disciplines like marketing and sales exist and also why processes like product discovery exist is that if we would leave product development to engineers, we’d get super efficient machines and software that are really elegant but don’t necessarily solve the problems customers have, are way too expensive to build and are not being sold.
At least that has been the case in the past sadly. So companies are now sometimes over-correcting by applying positive bias towards minorities
- Software Engineers don’t understand the best way to make money - Bottom up means that everyone will optimize locally for their own turf instead of converging on a common goal/set of goals for the company (ie reaching a global optimum)
I live in the Netherlands and despite what detractors would tell you, it’s impressive how on time the Dutch railways can keep such a complex schedule.
But let’s just agree to disagree here. You do you and build REST APIs, while I’ll stick to gRPC
The DSL I consider a plus. If you build REST APIs you will usually also resort to using a DSL to define your APIs, at least if you want to easily generate clients. But in this case the DSL is OpenAPI, which is an error prone mess of YAML or JSON specifications.
I imagine other companies went through a similar scenario but failed before series A
I really hate it when people throw around acronyms instead of just hitting a few extra keys on their keyboard for clarity