Like all things... this too shall pass.
Savantism is a separate concept from autism, though popular culture has somehow associated the two.
I realize my initial analysis is kind of wrong - everyone picking blue would also ensure everyone survives. So I think the color doesn't really matter if everyone is rational. So long as they are consistent. Blue is…
if everyone were rational, and knew everyone else would act rationally, then obvious answer is to pick red, because everyone would pick red, and hence everyone would survive.
modulo 2
root cause is believing anecdotes of people on the internet
> Alternatively, where possible set the server timezone to UTC so that no daylight savings changes will happen at all this is the way
NPEs are also present in a lot of languages with "stronger" type systems though. Is there a specific language you're comparing against?
out of curiosity (not meant snidely), do you have an example of a case where the weaker type system resulted in serious problems?
in tech? oft times you just look at your manager or skip level
Ah, I see what you're objecting to. Yes, it is build tag trickery, and wouldn't work without it
Yep - my point was that _test is not the only exception to the "rule"
You can also include package main files in a non-main package directory (usually sed when implementing go generate)
> contrasting craftsmanship and utility, since both are somewhat prized on HN I'd say they're prized everywhere, though "craftsmanship" is really subjective. and the HN I usually [edit/add: see] seems to have more a…
It hurts because it's true The amount of staffs at my place who build pointlessly complex bullshit that doesn't actually do anything different is too damn high
Thank you for this relevant insight.
You can still design for evolution and follow best practices. That's actually IMO a hallmark of good software design. The issue is when the evolution is random and rife with special cases and rules that cannot be…
I was recently having a conversation with some coworkers about this. IMO a lot of (software) engineering wisdom and best practices fails in the face of business requirements and logic. In hard engineering you can push…
every language has its problems; Go I think is pretty good despite them. not saying points raised in the article are invalid, you def have to be careful, and I hate the "nil interface is not necessarily nil" issue as…
Not arguing against you in any way, but IMO, if you're at a place where politics will dictate your _actual continued employment_, it's probably not somewhere I'd particularly enjoy working.
Not following the relevance here. I acknowledge and am aware this is very common, and it's a shame. But seems like a separate discussion.
Why does it matter if you don't get promoted? What if you like doing good work, making all that impact by osmosis anyway, but do it for the sake of just liking your damn job?
As someone who wholeheartedly agrees with this statement, I do wonder why this mentality is so prevalent. Is it just a consequence of natural selection? Those who want to grow and compete will inevitably dominate those…
> They inherit a codebase that successfully made enough of the right quality-vs-speed tradeoffs Or was lucky enough that all the choices they made did not blow up yet. I totally understand the value of technical debt.…
Google Datastudio, if you're fine with something in the cloud hooking up to your DB (and whitelisting the IP). Metabase or Apache Superset, as others have mentioned, can be deployed on-prem so it's a bit more…
Like all things... this too shall pass.
Savantism is a separate concept from autism, though popular culture has somehow associated the two.
I realize my initial analysis is kind of wrong - everyone picking blue would also ensure everyone survives. So I think the color doesn't really matter if everyone is rational. So long as they are consistent. Blue is…
if everyone were rational, and knew everyone else would act rationally, then obvious answer is to pick red, because everyone would pick red, and hence everyone would survive.
modulo 2
root cause is believing anecdotes of people on the internet
> Alternatively, where possible set the server timezone to UTC so that no daylight savings changes will happen at all this is the way
NPEs are also present in a lot of languages with "stronger" type systems though. Is there a specific language you're comparing against?
out of curiosity (not meant snidely), do you have an example of a case where the weaker type system resulted in serious problems?
in tech? oft times you just look at your manager or skip level
Ah, I see what you're objecting to. Yes, it is build tag trickery, and wouldn't work without it
Yep - my point was that _test is not the only exception to the "rule"
You can also include package main files in a non-main package directory (usually sed when implementing go generate)
> contrasting craftsmanship and utility, since both are somewhat prized on HN I'd say they're prized everywhere, though "craftsmanship" is really subjective. and the HN I usually [edit/add: see] seems to have more a…
It hurts because it's true The amount of staffs at my place who build pointlessly complex bullshit that doesn't actually do anything different is too damn high
Thank you for this relevant insight.
You can still design for evolution and follow best practices. That's actually IMO a hallmark of good software design. The issue is when the evolution is random and rife with special cases and rules that cannot be…
I was recently having a conversation with some coworkers about this. IMO a lot of (software) engineering wisdom and best practices fails in the face of business requirements and logic. In hard engineering you can push…
every language has its problems; Go I think is pretty good despite them. not saying points raised in the article are invalid, you def have to be careful, and I hate the "nil interface is not necessarily nil" issue as…
Not arguing against you in any way, but IMO, if you're at a place where politics will dictate your _actual continued employment_, it's probably not somewhere I'd particularly enjoy working.
Not following the relevance here. I acknowledge and am aware this is very common, and it's a shame. But seems like a separate discussion.
Why does it matter if you don't get promoted? What if you like doing good work, making all that impact by osmosis anyway, but do it for the sake of just liking your damn job?
As someone who wholeheartedly agrees with this statement, I do wonder why this mentality is so prevalent. Is it just a consequence of natural selection? Those who want to grow and compete will inevitably dominate those…
> They inherit a codebase that successfully made enough of the right quality-vs-speed tradeoffs Or was lucky enough that all the choices they made did not blow up yet. I totally understand the value of technical debt.…
Google Datastudio, if you're fine with something in the cloud hooking up to your DB (and whitelisting the IP). Metabase or Apache Superset, as others have mentioned, can be deployed on-prem so it's a bit more…