pondidum

9 ms·

1.
by pondidum 2y ago
I also think that printf debugging is fine, but there are better tools [1] - however they might be more involved to setup, or not be available in your codebase. [1]: https://andydote.co.uk/2024/11/24/print-deb
2.
by pondidum 2y ago
Thoughts after reading https://news.ycombinator.com/item?id=42219708
3.
Print debugging: a tool among other tools(andydote.co.uk)
3 points by pondidum 2y ago|1 comments
4.
by pondidum 2y ago
Go: go templates and fiber for http serving. I have a mini framework for adding some structure to the templates (folder per feature: contains controller, templates, etc, and some naming conventions)
5.
by pondidum 3y ago
If I understood correctly, you can achive this with `hx-target` and `hx-select` - I'm doing this in an app to replace an editor content based on which link is clicked. - https://htmx.org/attributes/hx-select/
6.
Kubernetes and Kernel Panics(netflixtechblog.com)
3 points by pondidum 3y ago|0 comments
7.
by pondidum 3y ago
Yes, and itel has instrumentation libraries which do this. However, no automatic instrumentation can do everything for you; it can't know what are all the interesting properties or things to add as attributes. But adding tracing autom
8.
by pondidum 3y ago
They all look fine in "mobile view" in firefox, and on firefox in android. It's all statically rendered html, and I don't see anything weird in the html either. Do you have a screenshot and some device info so I can loo
9.
by pondidum 3y ago
As other posters have mentioned, the incument companies rebranding to Observability definitely are expensive, because they are charging in the same way as they do for logs and/or metrics: per entry and per unique dimension (metrics esp
10.
by pondidum 3y ago
Yes, but going to this effort, why not move to tracing instead? A migration path I could see might be: - replace current logging lib with otel logging (sending to same output) - setup tracing - replace logging with tracing over time (I pref
11.
by pondidum 3y ago
Thanks, I have fixed the definition in the post! Turns out its just company slang for bating, rather than Finnish slang!
12.
Tracing: Structured logging, but better(andydote.co.uk)
263 points by pondidum 3y ago|129 comments
13.
by pondidum 3y ago
Agreed the amount of stuff showing in stack traces can be annoying - but it does depend on language. I agree 100% in javascript/typescript its annoying, and I would love to get rid of them, In go however, there isn't an extra stac
14.
by pondidum 3y ago
The only thing I can recall being a bit of a stumbling point at the beginning was finding "my" trace from a local environment. I just didn't know where to find it. Once I figured that out I've not had problems. The hig
15.
by pondidum 3y ago
Depends what you're trying to accomplish. We're using middleware to start spans for http and message handlers, and then adding `startSpan` where we need. I don't see a problem with `startSpan` everywhere as it's not much
16.
by pondidum 3y ago
Honeycomb's pricing is pretty reasonable - but looking at your volume, some sampling might help also
17.
by pondidum 4y ago
Only read the flag once! For multiple flags we tend to have the first step in the build read all flags we care about and export them to environment variables.
18.
by pondidum 4y ago
Sure you can use the environment variables, and if you have simple uses cases this is probably the best way to go. In this case, we're using LaunchDarkly's targeting to serve different variations to groups of users, and also using
19.
by pondidum 4y ago
It actually does have different error codes; I think I just forgot to update the docs: 0 - flag on 1 - flag off 2 - error I'll update the docs soon!
20.
Feature flags in a CI pipeline(andydote.co.uk)
59 points by pondidum 4y ago|27 comments
21.
by pondidum 4y ago
From the link further up the replies: > Deploy is the act of moving software into an environment and running it. > Release is the process of making a feature visible to a user or subset of users. In our case, we deploy often (10s of t
22.
by pondidum 4y ago
I understand that, but would counter with that it sounds like deploy == release, and that if that weren't the case, you could deploy more often. However, I will admit it is a trade-off; some engineering time does have to be spent to ge
23.
by pondidum 4y ago
What about secrets? I like to do short lived credentials using Vault (e.g. vault can create say db access credentials dynamically), but for things like API keys where I can't do that..? Is the Vault KV store the source of truth?
24.
by pondidum 4y ago
Oh now that is an interesting take! Would that still be required if a deployment and a release are decoupled entirely, or is it unavoidable? Genuinely interested!
25.
by pondidum 4y ago
You're right, hate is far too stronger term for this, I've updated the wording. Thanks.
26.
by pondidum 4y ago
> Do not make production changes on Fridays I ~hate~ dislike this advice. If you can't deploy on a Friday, you need to fix your deployment strategy. By removing Friday from when you can deploy, you're wasting 1/5 of your a
27.
by pondidum 4y ago
To address the purpose of make, this was written with a large multi workspace typescript project in mind: in the real project, there are many more make targets with dependencies on each other, and we don't want to waste time rebuilding
28.
by pondidum 4y ago
I would also highly recommend shellcheck ( https://www.shellcheck.net/ ) for useful error messages and warnings!
29.
by pondidum 4y ago
Oops, I'll fix that. Thanks
30.
by pondidum 4y ago
Correct, the state directory isn't being cleared. As this is mostly aimed at making ephemeral build agents faster, this shouldn't matter much in practice. Having said that, there is definitely some work to do on keeping the remot

More ›