jka

113 ms·

901.
by jka 5y ago
It's been on my mind with regard to excessive redundant use of continuous integration resources, and similarly during repeat pulls of bulky container images. That's just my anecdotal experience though, and without supporting data.
902.
by jka 5y ago
It's best applied in situations where both direction A and direction B lead to significant downsides, I think. Instead of choosing one of those and getting stuck with (and having to justify) the consequences, wait until the downsides c
903.
by jka 5y ago
For an alternative data source, Statista provides Mobile OS market share going back a little over a decade: https://www.statista.com/statistics/272698/global-market-sha... (this is based on web traffic measured by
904.
by jka 5y ago
Thank you for the correction, and I don't remember seeing the PrivacyIssues page before - that's a useful resource. Looking forward to reading a bit more about popcon & hwdb as well.
905.
by jka 5y ago
It's not practical in a lot of organizations, but something I like to do, when possible, in the face of a non-consensus decision is simply to wait. That might seem inconceivably frustrating for people who like to make continuous change
906.
by jka 5y ago
For anyone new to Debian: it's a Linux-based operating system distribution, available at various levels of support for multiple computer architectures: https://wiki.debian.org/SupportedArchitectures Debian includes an
907.
by jka 5y ago
"Do we believe that someone would go to the effort of setting up GPT to generate fake papers..." I'd say it depends on what their desired outcome is. If they know that other people are using AI to assess the literature about
908.
by jka 5y ago
Thanks for responding honestly. There's some more information out there now regarding the original story: It looks like there are twelve individuals who have been responsible for large amounts of the disinformation that is a concern,
909.
by jka 5y ago
> It is going to be difficult if not impossible to prove what it was This makes me think of the way that the tobacco[1] and petroleum[2] industries knew about the harmful effects of their products long before the causes were removed or t
910.
by jka 5y ago
See also https://globalprivacycontrol.github.io/gpc-spec/ for the (draft) spec.
911.
by jka 5y ago
I sorta get where you're coming from, but not sure I completely understand. What do you think this post flagging activity will lead to, and do you feel confident that those outcomes are worse than the impact of the flagged content?
912.
by jka 5y ago
Desktop environments, operating systems, communication and collaboration tools, web browsers, widely-used shared libraries, for example.. there are a large number of software systems that people rely on where stability, performance, bugfixe
913.
The Maintainers(themaintainers.org)
1 points by jka 5y ago|0 comments
914.
by jka 5y ago
In the same way that it can be difficult to justify spending a week to reduce technical debt within a fast-moving engineering team, I think there's a parallel challenge for industry to make the work of maintenance be seen -- and be rew
915.
by jka 5y ago
> This isn't some noble representative getting a bill passed through Congress to stick it to Big Tech for profiting off of outrage media, click-bait, surveillance capitalism, etc etc (I wish it were thus). This is the executive bran
916.
by jka 5y ago
Because misinformation is rife, dangerous, and is being weaponized. Ideally any measures to control misinformation - like societal restrictions during the pandemic - are temporary and rolled back when the situation is more stable. I don&#x2
917.
by jka 5y ago
Improving coverage is a good goal, although (depending on the codebase) I think it can provide a false sense of robustness. Generally more coverage is good, yes; but there can be an element of risk around "testing two inputs in isolati
918.
by jka 5y ago
Well deserved; congratulations, Łukasz!
919.
Bicycle sidecars as alternative to cargo bikes (2015)(eta.co.uk)
1 points by jka 5y ago|0 comments
920.
Optimize your pub crawl with openrouteservice (2018)(openrouteservice.org)
2 points by jka 5y ago|0 comments
921.
by jka 5y ago
In terms of tooling: use what you have available today that is accessible to the people who will need to read and write the documentation over the next few weeks and months. In terms of a categorization framework to arrange the documentatio
922.
by jka 5y ago
Probably people who analyze problems deeply, make very few commits, and then share their improvements without really even considering credit as a reward. The software industry has a risk of developing an influencer problem, and I'd gue
923.
by jka 5y ago
I'd be willing to bet a reasonable amount that there's a large future for "subtractive software development" (maybe a slightly misleading or unfair term, since it'd include bugfixes). Once we have multiple proven te
924.
by jka 5y ago
Unsure, I'm afraid - let me know if and when you find out; hopefully a good place to work :)
925.
by jka 5y ago
"Move purposefully, and have a healthy culture involving thoughtful service architecture, documentation, knowledge-sharing and problem-solving with attentive, well-rested and detail-focused engineers who trust each other."
926.
by jka 5y ago
In practice, how long it takes for any ingredient step is naturally going to be context-sensitive, and most recipe authors and readers appreciate that. (chef's experience, properties of the ingredients used, quality of equipment.. amon
927.
by jka 5y ago
Very relevant, thank you!
928.
by jka 5y ago
You have a point, but at the other end of the spectrum, writing precise legal terms can cause problems as well. If the terms refer specifically to "cookies" and "browsers", it'd be entirely possible that the adverti
929.
by jka 5y ago
There might be an opportunity somewhere around this area to combine the versioning, continuous improvement, and dependency management of package repositories with the Q&A format of StackOverflow. Something like "cherry pick this an
930.
by jka 5y ago
Nicely said. One small adjustment I'd suggest -- because I care a lot about setting incentives -- is that we generally want not just _more_ "why" comments, but in particular concise "why" comments that empathize wi

More ›