throwaway13623

3 ms·

1.
by throwaway13623 3y ago
I don't follow the news closely, so I was not aware that Copilot is based on ChatGPT or that MS had already integrated Copilot with Teams.
2.
by throwaway13623 3y ago
In this case the original title is "ChatGPT for teams", so the headline was actually editorialized when it was submitted, which is discouraged by HN guidelines. Normally it would be ok to capitallize words to match what many other
3.
by throwaway13623 3y ago
> - you've just made the coupling less robust In my opinion this depends on the use case. If one service has a strong dependency to a different service, it may be a case of "distributed monolith" and they should consider i
4.
by throwaway13623 3y ago
I agree. Guard clauses and chunk statements make code much more maintainable. It has little cost of implementing, but a huge return on readability and reduced complexity. Nested if-statements are often hard to read and easy to break.
5.
by throwaway13623 3y ago
> I have never seen Kotlin used in environments other than Android I have seen several companies that use Kotlin as a backend language (often with Spring). I personally don't find the differences enough to bother switching from Java
6.
by throwaway13623 3y ago
I think you may have a point. At mature companies, they have largely solved the product market fit and uses a stable stack that just works. I have worked worked for such companies, and developers jumped at the chance to use the latest (unte
7.
by throwaway13623 3y ago
I've worked in "enterprise" and have a different experience. The enterprise projects that I was working on switched to Java 8 in 2015. There were some legacy services that remained on 5 or 6 for a while, but they were mostly