>Income tax + business tax pile up to 50% already Is that for all your income or "just" over a certain threshold? >Even if you make some good money, that does not leave you with a lot to live. You said you travelled to…
I bind Ctrl-J to ":Ag " so I'll simply have to type in roughly what I'm searching for and then get the pop-up to refine the search and do selections. I imagine you have a similar approach, what's clunky about it for you?
Even with a CS background, I would expect a blog post that is supposed to be a "A Critical Review" to at least try to be fair and reasonable. It doesn't have to be neutral in my opinion. But it should clearly separate…
> I would not question their credentials and reliability over a word In more or less informal discussions, I agree. From my POV it's not about a singular word though, it's about the context: The author labelled the…
Even then the talk is about a clusterfuck _within_ the code base and how it got fixed. It clearly doesn't label the current state of the code base as a clusterfuck in general.
Even then there's arguably a stark contrast between >The clusterfuck hidden in the Kubernetes code base and the brilliant refactoring techniques developed to fix it and saying >[...] forking a large code base,…
I would say it is an interesting fact, since it's this "good 'API boundary'" that, as you said, enables one to separate concerns, be it between different teams in an organisation or between a service provider and its…
I mean, the title of the website is "Cloud Critical - Your service mesh is garbage". And the author says >No critical conversations about Kubernetes are taking place, aside from outspoken critics on HackerNews or…
>Income tax + business tax pile up to 50% already Is that for all your income or "just" over a certain threshold? >Even if you make some good money, that does not leave you with a lot to live. You said you travelled to…
I bind Ctrl-J to ":Ag " so I'll simply have to type in roughly what I'm searching for and then get the pop-up to refine the search and do selections. I imagine you have a similar approach, what's clunky about it for you?
Even with a CS background, I would expect a blog post that is supposed to be a "A Critical Review" to at least try to be fair and reasonable. It doesn't have to be neutral in my opinion. But it should clearly separate…
> I would not question their credentials and reliability over a word In more or less informal discussions, I agree. From my POV it's not about a singular word though, it's about the context: The author labelled the…
Even then the talk is about a clusterfuck _within_ the code base and how it got fixed. It clearly doesn't label the current state of the code base as a clusterfuck in general.
Even then there's arguably a stark contrast between >The clusterfuck hidden in the Kubernetes code base and the brilliant refactoring techniques developed to fix it and saying >[...] forking a large code base,…
I would say it is an interesting fact, since it's this "good 'API boundary'" that, as you said, enables one to separate concerns, be it between different teams in an organisation or between a service provider and its…
I mean, the title of the website is "Cloud Critical - Your service mesh is garbage". And the author says >No critical conversations about Kubernetes are taking place, aside from outspoken critics on HackerNews or…