The thing about memory ownership is that it's intrinsic (not incidental) complexity on a physical computer. If you don't want GC, you need ownership.
Not all languages provide ownership tooling though (e.g. C). Following Rust's success I suspect we'll see more ownership tools. https://twitter.com/migueldeicaza/status/1103427307451035648
miniblog.
Need therapy? I'm fascinated to learn there's an app this, providing a set of free features supported by a community: https://blog.time2track.com/a-psychologists-honest-review-of-7-cups-of-tea
USB 4 will recommend a standard set features that all devices of the same type should implement. This should simplify things somewhat over USB 3, where device and even cable compatibility isn't guaranteed.
https://www.theverge.com/2019/3/4/18246182/usb-4-thunderbolt-3-specs-features-release-date
USB is feeling a little less universal though.
A new speculative execution vulnerability in CPUs: https://www.theregister.co.uk/2019/03/05/spoiler_intel_processor_flaw/
Attacks only get sophisticated over time, and this is a great example of other researchers finding similar issues. This vulnerability is independent of Spectre.
Designing wire protocols: https://esr.ibiblio.org/?p=8254
Discusses extensibility, bug prone features, and network and CPU overheads in low traffic systems.
Ramping up with a new technical team, and asking the right questions:
https://boz.com/articles/career-cold-start.html
Blogged: How High Are Your Tests?
One sign your blog posts are successful: they give you something to refer to in conversation with others!
Blogged: How High Are Your Tests?
Several of the best jobs I've had, I heard about them through Twitter. When Twitter works well, it can be a fabulous source of 'watercooler conversation' across the industry.
Amazon moving to a serial number verification program to deter fakes:
https://www.theguardian.com/technology/2019/mar/04/amazon-to-give-power-to-brands-to-delete-fakes-from-website
Backdoored versions of popular software being distributed on GitHub: https://www.zdnet.com/article/researchers-uncover-ring-of-github-accounts-promoting-300-backdoored-apps/
Perhaps it's only a matter time before we see blue checkmarks on repos? I suppose the star count does help distinguish real repos.
I've worked on many projects where tests are have discrete levels, usually something like unit test, integration test, end-to-end test.
I've also seen elaborate arguments over what counts as a unit, especially in heavily OO codebases.
Given coverage data, how would you build a tool to decide which untested parts of a codebase most need tests?
The best I can think of is using profile data to ensure hotspots are tested. Not sure if it's ideal though: top level code and well-exercised logic would be highlighted.
Flux is an app for digitising receipts and business loyalty cards: https://www.tryflux.com/
These are both pieces of paper you often need to keep around. Receipts are particularly something you might need if you're expecting to need the warranty. Could be convenient.
Showing 2,236-2,250 of 7,549 posts