mechsy · HackerTrans

há 3 mesesdiscuss

Yes, it helps to keep the bigger picture (pun intended) in focus and something tangible to criticise. Same for design docs. Otherwise, the conversation‘s spotlight just keeps moving around and might even follow whatever thread one of the more prolific speakers just came up with, which carries the danger of derailing the whole thing and adjourning without a decision.

mechsy

há 3 mesesdiscuss

Yeah in a similar project getting line passthrough or similar to work (matching sampling frequencies etc.) to get a clean signal for the FFT proved much harder than setting up eg the ESP32 side of things. But it’s a lot of fun to play around accumulating values in the frequency buckets while trying to get the reactivity tradeoff right. Just don’t look directly into the LEDs in a dark room, maybe that’s a bit dangerous.

mechsy

há 4 mesesdiscuss

I too see potential in this - it started feeling a bit weird in recent years switching between Go, Python and Rust codebases with Python code looking more and more like a traditional statically typed language and not getting the performance benefits. I know I know, there are libraries and frameworks which make heavy use of fun stuff you can do with strings (leading to the breakdown of even the latest and greatest IDE tooling and red squiggly lines all over you code) and don’t get me started on async etc.

Funnily enough I’ve found Python to be excellent for modelling my problem domain with Pydantic (so far basically unparalleled, open for suggestions in Go/Rust), while the language also gets out of my way when I get creative with list expressions and the like. So overall, still it is extremely productive for the work I’m doing, I just need to spin up more containers in prod.

mechsy

há 5 mesesdiscuss

Absolutely! This is oftentimes my first easy task in the morning to kick things off. For many teams the temptation to let dependencies ‚rot‘ is real, however I have found a reliable way to keep things up-to-date is enabling dependabot and merging relentlessly, releasing often etc.

If your test suite is up to the task you’ll find defects in new updates every now and then, but for me this has even led to some open source contributions, engaging with our dependencies’ maintainers and so on. So I think overall it promotes good practices even though it can be a bit annoying at times.

mechsy

há 7 mesesdiscuss

Cancer sucks, I wish all the best towards a recovery.

You’d also have to ‘fix’ DNA: unless we can re-engineer a bunch of key enzymes and then re-encode the entire genome (or maybe key parts) with forward error correction without breaking everything else, it might work. You might also break evolution to some degree by making random point mutations less likely.

But what I learned so far is that as soon as you’d attempt something like this in bacteria, the fitness advantage from an evolutionary standpoint is negligible compared to the efficiency loss introduced by FEC, so your colony would get outcompeted by other bacteria unless there is a niche your resistant bacteria survive in (high radiation environments?). The efficiency loss induced ‘disadvantages’ would probably be less pronounced in mammals though - If (big if) you manage to not also break anything essential in the wonderful yet surprisingly efficient Rube Goldberg machine that is life.

mechsy

há 7 mesesdiscuss

True, opportunity cost is a factor, sorry if my reply sounded a bit brash. IMHO they are one of the few orgs who got this model right compared to lots of others who went the open core or support/consulting contract required OSS route.

mechsy

há 7 mesesdiscuss

If you need less scale/features go for glitchtip. If you’re not going for k8s, the self-hosted docker-compose version of sentry works fine including proper releases and support by the sentry team etc. Just experimental newly introduced features can be a bit wonky. They are doing much more than just throwing code over the fence. Also phone home telemetry is optional and there’s a switch for just errors mode. IMHO this really builds trust. With regards to deployment complexity: well it’s built for handling high volumes of events. I’d reckon this is more a consequence of scaling the project rather than a coordinated plan to push people to their cloud offering. If you do go for k8s or choose to deploy the stack yourself, you even get access to the full scale solution. But if you’re at that scale, you probably have someone hanging around who knows how to run your clickhouse setup. You still get the full sentry software and SDKs for free in that case. I think this is as fair as it gets with regards to the open source SaaS model.

comments