p-squared

On a day-to-day basis, weight measurement changes are dominated by changes in retained water. This will certainly correlate with daily food choices, but does not really reflect meaningful changes in body composition. Average your measurements over something like a week in order to gauge actual progress.

Maybe Rust makes newtypes _easy_, but certainly C supports similar idioms by way of wrapping data in a unique struct.

> Three points define a plane; it's guaranteed not to wobble.

This gets repeated a lot. I think if you stop to consider the common case of non-planar ground, you will see that this mathematical factoid isn't actually super-relevant.

(I will concede that it's not trivial to add a fourth leg and make it co-planar to the other three. But this often isn't the cause of wobble.)

> Netflix has been using anti-consumer dark patterns for years.

Examples? "Trailers in your face on the main menu" is not a "dark pattern": there is no element of deception involved. It's simply a user experience that you dislike. Similarly, removing AirPlay support may suck for consumers, but it's not deceptive.

The key phrase is "who are not fully aware of their responsibility". The commenter is not wrong in identifying a subset of the candidate pool which has a high risk of inadequate experience for this kind of work.

The term "subsidy" implies that the state is actively paying out cash to Foxconn. If I'm correct that these are actually tax breaks, then the state is merely claiming less tax revenue from Foxconn than state law would otherwise dictate. That's tax revenue that the state wouldn't see at all in the absence of Foxconn. And if Foxconn's locally-generated revenue ends up being smaller than originally anticipated, then it would stand to reason that the effective reduction in tax revenue is reduced as well.

The article goes on and on about wasted subsidy funds (there are other valid criticisms of the deal, but this is the big one). The Foxconn deal may not be working out, but if everything is structured in terms of tax then the state finances are not really getting impacted.

My recollection from earlier stories covering this deal is that "subsidy" actually means "tax break". If that's correct, then the tone of this story is very misleading.

"Hardened SHA-1 hash" is a confusing way to characterize git's current hash behavior. There is no change in the hash--it continues to be SHA-1. The change is in git's business logic: it will detect hash inputs that look like a SHA-1 collision attack, and will refuse to proceed.

Yeah, it's extremely unlikely that a high-speed serial phy would even expose a primitive word size any smaller than 32 bits. Byte-by-byte decoding is extraordinarily difficult at these data rates.

> They have 18k classes because they came up with a rather clever way of allowing many separate developers to all work on different features of the same app, without stepping on each others toes.

What makes you believe this is "clever" as opposed to a poor engineering decision? I strongly suspect that FB might have delivered a higher quality product through a more traditional team-ownership development model. Throwing large numbers of developers at a single app is unlikely to lead to a well-architected holistic solution.

Location: Wisconsin; actively looking to relocate to a warmer climate.

Remote: No.

Willing to relocate: Yes, please.

Technologies: C++, C, Python, OCaml, Verilog, bus analyzers, JTAG debuggers, o-scopes, and whatever else gets the job done.

Resume: https://drive.google.com/file/d/0B4aVktLek0w0bnRDLVZlTTRCX1U...

Email: wi.is.cold@gmail.com

I'm a software engineering generalist, but my skills run pretty deep in both systems engineering and embedded programming. I'm comfortable working at any level from handful-of-KB bare-metal microcontrollers to Linux kernel drivers to complex multithreaded application design, and I enjoy the variety of working in multiple domains.

My most extensive experience is in block storage peripherals. I've written drivers for a variety of storage protocols and I've designed and built the software architecture for products that move data from storage device A to storage device B at improbably high speeds. But I'm not really looking to get pinned down as a "block storage guy," and would prefer to branch out in a different direction and learn some new technologies along the way. Maybe you have something interesting?

I'm not really looking for yet-another-web-startup opportunities. An attractive position will have challenging problems to solve, a meaningful product to deliver, and a team of smart engineers getting it done. It might involve a physical hardware component, but that's not a requirement. If you are building something on a Node stack, you should be prepared for me to not take you seriously.

Bonus points for use of functional programming languages with strong static type systems.

Location: Wisconsin; actively looking to relocate to a warmer climate.

Remote: No.

Willing to relocate: Yes, please.

Technologies: C++, C, Python, OCaml, Verilog, bus analyzers, JTAG debuggers, o-scopes, and whatever else gets the job done.

Resume: https://drive.google.com/file/d/0B4aVktLek0w0bnRDLVZlTTRCX1U...

Email: wi.is.cold@gmail.com

I'm a software engineering generalist, but my skills run pretty deep in both systems engineering and embedded programming. I'm comfortable working at any level from handful-of-KB bare-metal microcontrollers to Linux kernel drivers to complex multithreaded application design, and I enjoy the variety of working in multiple domains.

My most extensive experience is in block storage peripherals. I've written drivers for a variety of storage protocols and I've designed and built the software architecture for products that move data from storage device A to storage device B at improbably high speeds. But I'm not really looking to get pinned down as a "block storage guy," and would prefer to branch out in a different direction and learn some new technologies along the way. Maybe you have something interesting?

I'm not really looking for yet-another-web-startup opportunities. An attractive position will have challenging problems to solve, a meaningful product to deliver, and a team of smart engineers getting it done. It might involve a physical hardware component, but that's not a requirement. If you are building something on a Node stack, you should be prepared for me to not take you seriously.

Bonus points for use of functional programming languages with strong static type systems.

Location: Wisconsin; actively looking to relocate to a warmer climate.

Remote: No.

Willing to relocate: Yes, please.

Technologies: C++, C, Python, OCaml, Verilog, bus analyzers, JTAG debuggers, o-scopes, and whatever else gets the job done.

Resume: https://drive.google.com/file/d/0B4aVktLek0w0bnRDLVZlTTRCX1U...

Email: wi.is.cold@gmail.com

I'm a software engineering generalist, but my skills run pretty deep in both systems engineering and embedded programming. I'm comfortable working at any level from handful-of-KB bare-metal microcontrollers to Linux kernel drivers to complex multithreaded application design, and I enjoy the variety of working in multiple domains.

My most extensive experience is in block storage peripherals. I've written drivers for a variety of storage protocols and I've designed and built the software architecture for products that move data from storage device A to storage device B at improbably high speeds. But I'm not really looking to get pinned down as a "block storage guy," and would prefer to branch out in a different direction and learn some new technologies along the way. Maybe you have something interesting?

I'm not really looking for yet-another-web-startup opportunities. An attractive position will have challenging problems to solve, a meaningful product to deliver, and a team of smart engineers getting it done. It might involve a physical hardware component, but that's not a requirement. If you are building something on a Node stack, you should be prepared for me to not take you seriously.

Bonus points for use of functional programming languages with strong static type systems.