- The point really was that the unused method parameter should in almost all cases be removed, not that some trick should be used to make it seem used, and this is the wrong trick!
- a = a; // misra
Actual code i have seen with my own eyes. (Not in F-35 code)
Its a way to avoid removing an unused parameter from a method. Unused parameters are disallowed, but this is fine?
I am sceptical that these coding standards make for good code!
- Dec 2023:
96GB (2x48) DDR5 5x00 £260 today £1050
128GB (4x32 ) DDR5 5x00 £350 today £1500
Wut?
Edit: formatting
- 100% test coverage is a bit of a distraction.
You can get to 100% by having tests that run the code, but have no assertions.
You can run tests that test unimportant code just as much as super critical code. There's no differential between the two. Of course super critical code should have a number of different tests that exercise it. Its not the same as testing every path, its testing different inputs and checking that you get the right results. Also see property testing.
Chasing 100% is like any metric that becomes a goal, it perverts the metric, and moves the meaning away from the metric.
Why is that? Well, we dont really want tests at all, if only people could write perfect software first time, we wouldn't need them. Stupid people!
What we want are reliable systems! So we use feedback loops between deployed systems and code to help us discover those places where we need more tests, or a different type of testing, and then we do that.
Of course if your test coverage is 0%, thats probably bad, but 100% is a non-goal.
You'll also find that if there are no tests in a system, when you need to add them, its really hard, cos its not designed in a way that makes it testable. So maybe the TDDs will help you! You end up with a system that you have high confidence in, and also is testable.. so when you find something that doesn't work how you thought, its easy to add that test right in there.
- "all your data are belong to us" ftfy
- Been saying this for years!
All the security theatre!
False urgency is red flag when it comes to emails and sms.. I dont see why people don't see the same when it comes to dependency alerts.
The vast vast majority of alerts are totally useless, when it comes to your actual deployed system, unexploitable and irrelevant.
Rushing to update causes make-work, churn and loss of focus on the real.
Don't get me wrong, I love secure systems, but dependency theatre doesn't make it.
Very very occasionally, you'll get a high priority signal, and then yes act on it immediately. Your deployment systems should be designed so that this is just another release. No expedited short cuts, just another day.
Reducing dependencies, defense in depth, validation, type-safe, null-safe languages etc all good.. endless dependabot PRs with no understanding of the reason or impact, bad.
- Real time pressure information is valuable when being reported from lots of geographically dispersed devices. Its a way of tracking weather fronts. The "discontinued" device is still a little google money printer.
- In my personal experience, if you are being dazzled by headlights from behind, its a tesla.
They have always been that way. Im not accusing them of being involved in "headlightgate", but it would be great if somebody did some research.
Beam patterns are always checked when at rest, just like diesel particulate emissions..
- Had to ban RU, CN, SG, and KR just cos of the volume of spam. The random referer headers has recently become a problem.
This is particularly annoying as knowing where people come from is important.
Its just another reason to give up making stuff, and give in to the FAANG and the AI enshittification.
:-(
- 1200/75 is enough for anyone? (0p)
- Would be interested to know about the a11y story on web and other platforms. Does it integrate with screen readers, accessible navigation tools, a11y apis, etc.
This is somewhere quite a few tools fall down. For example, for web: Rendering to canvas doesn't create the dom nodes required to hook into the tools, and creating the nodes appropriately can have a significant performance impact.
What about native a11y tools and tech.. there are some ios specific ones that you'd expect on an ios app for example.
- Relevant recent incident:
https://www.theguardian.com/uk-news/2025/nov/08/environmenta...
Obvs, uk gov does nothing
- Its true that aws is very expensive for a lot of use cases, as long as you only count the cost of the servers.
However, in most (every?) large organisations, buying a server and putting it in a DC, and looking after it, is hugely time-consuming, lengthy and expensive.
You need to get quotes, approvals, purchase, rack, commission, maintain etc etc. It is usually close to 1 year to get a server.
In some companies, even getting a virtual server takes almost as long!
With AWS, once an account and service is approved, boom, you are done.
- Perfetto is so nice.
Viztracer is a super library to capture perfetto compatible output from Python.
It helped me find perf issues in literally minutes.
https://raw.githubusercontent.com/time4tea/gopro-dashboard-o...
- Result<T> is a built-in in kotlin, but this enforces that the error type is a Throwable
If you fancy that an error could be just a type, not necessarily a Throwable, you might like Result4k - it offers a Result<T,E>
https://github.com/fork-handles/forkhandles/tree/trunk/resul...
disclaimer: I contribute to this.
- Super interesting to know. I wonder why they bothered!
Thanks for the info.
- Proguard obfuscation, particularly when you get to aggressive renaming (there are a lot of valid characters for a java class or method), flattening, overloading and inlining, can make it very hard to understand what is actually happening.
Its great to make this step.
- Agreed! But i didnt miss the example.... i also thought it was interesting that all the various examples of declarative or applicative did Date.now(), which i see as a big thing to avoid.
- Not a single person in this thread commented on the use of Date.now() and similar - surely clock.now() - you never ever want to use global time in any code, how could you test it?
clock in this case is a thing that was supplied to the class or function. It could just be a function: () -> Instant.
(Setting a global mock clock is too evil, so don't suggest that!)
https://github.com/time4tea-net/py-hole/
You can run it on your openwrt router - see readme. Its just a python script that updates a file that dnsmasq uses. No funny business, you are in charge of everything.
Disclaimer: author of said script.