HNHacker News
TopNewBestAskShowJobs

mfuzzey

317 karma · joined January 11, 2022

submissionscomments
mfuzzey··on Has Earth’s inner core stopped its strange spin?
In "real" science, ie stuff that has been proven by experiment, when new understanding is obtained the old stuff remains valid at laeast as a special case (otherwise it would never have been confirmed by experiment in the first place).

So, while we now know that Newtonian physics breaks down in some circumstances, where relativity and quantum mechanics are needed Newtonian is still good enough for most everyday and a lot of not so everyday applications (like sending probes to Mars).

It doesn't flip / flop like the "eating eggs was good yesterday and is now bad".

mfuzzey··on Google calls in help from Larry Page and Sergey Brin for A.I. fight
Isn't Apple maps only for Apple devices? If so no competition for GMaps.
mfuzzey··on Stop Building on Corporate-Controlled Languages
>before you cite “Linux”, look at who the top contributors are - all corporations.

That is true but no single corporation has control of Linux. Linux (the kernel) has managed to harness corporations to fund developers so they can work full time on it without giving said corporations "editorial control" over Linux.

Individual corporations that pay Linux developers have some influence over the type of things that are worked on (by paying people that specialise in some parts of the kernel over others) but they don't get to decide what actually goes into the mainline kernel.

Unfortunately the same isn't true of most languages where there is often a single corporation behind it.

mfuzzey··on It's time to stop texting
Here in France very few people use SMS to talk with friends.

They are now mostly just used by companies to send short notifications (like if you drop your car off at a repair place they'll send you a SMS when its ready to pick up). It's good enough for quick one offs like that and not much else.

Most people use whatsapp and some signal or telegram.

The US seems to be pretty backwards on technology. Chip based payment cards have been universal here since the 90s (maybe even before) while the US was still on magstripe for decades.

mfuzzey··on Theory-building and why employee churn is lethal to software companies
"Dig into how it works" may take longer than rewriting or it may not. And the rewrite may (and often does) run into unexpected difficulties too.

I think it's a mistake to make the "fix the old" or "rewrite from scratch" decision up front from a position of high uncertainty about the old system.

I'd go with a strategy of starting a timeboxed exploration of the old system with the objective of understanding it better, hopefully well enough to have a reasonable idea of what it will take to fix it. Then make the decision from a better informed position. Yes sometimes the decision may still be to rewrite because you now know that the old system will be excessively hard to change but in many cases you may find out that the old system wasn't as bad as expected.

mfuzzey··on Things they didn’t teach you about software engineering
I guess that depends on what you mean by "stand out" then. It is possible to stand out technically without standing out in a "how high in the org chart can you go" contest
mfuzzey··on Ask HN: Is programming culture immature?
>I don't want to use Windows, when I hunt for jobs I avoid jobs that do not offer mac/linux laptop. This is probably immature.

I don't think that is immature at all. As a professional it is perfectly reasonable to expect to have good tools. If, for what your job involves, Linux / Mac is significantly better (for you) you are right to insist on it.

If you were applying for jobs as a carpenter you'd be right to ignore any that only provided a hammer.

mfuzzey··on Coworkers are less ambitious; bosses adjust to the new order
>The company wouldn't employ you if you weren't providing them more than you cost them.

Yes that's true of course.

>It's never been easier to create enough value on your own terms to sustain yourself and not let someone else siphon out your value on their terms

Not so sure about that part. Maybe it's easier today but if you mean things like freelancing the problem is that you then have to do lots of stuff that isn't interesting to a lot of technical oriented people (like finding clients, negotiating contracts etc). The advantage of working for a company is that you can concentrate on the things that interest you and leave the rest to others.

Sure you'll end up earning less but, in my book at least, its worth it. But nothing says you have to "sarifice yourself" you can work for a company but still have a decent balance to have time for other things.

mfuzzey··on Battery replacement must be 'easily' achieved by consumers – EU
Maybe but not because it's a "fake" but because it's low quality. Anything that is dangerous and doesn't meet safety regulations should be banned. But there's nothing inherently wrong with 3rd party parts, batteries or otherwise.
mfuzzey··on Censoring Naked Yoga
This should be illegal.

Businesses like payment processors should not be allowed to refuse to provide their services to any legal clients. And legality is up to the courts to decide not payment processors or any other middlemen.

If enough people really want to ban porn (I don't know or care if this particular site was really porn) then go through the proper channels, and make a law explicitly banning it don't try to get private companies to do the work of enforcing arbitary rules.

mfuzzey··on EU-wide maximum limit of €10K for cash payments
>Stop pretending the government (any) has the “average” man’s best interest

"Average" people don't pay >10k€ in cash. So this measure won't hurt average people and may stop some money launderers / frauders so no issue with it.

And actually most EU countries already have lower limits.

mfuzzey··on Appreciating F-Droid as an app developer
The OS itself being proprietary isn't a reason to not have sideloading or alternative stores.

Windows is proprietary too yet you've always been able to download a .EXE from arbitary web sites.

mfuzzey··on Company, Team, Self
Problem is who gets to decide what is best for the company?

In many organisations most people may not have enough information to really know what is best for the whole organisation, even if they do have good ideas about their part.

And top executives often can't be trusted to act in the best interest of the company (rather than that of the shareholders, the stock market or themselves...). Short term vs longterm is also very imporant, the best way to make a quick buck today is often at odds with what is needed to remain relevant in 5 or 10 years.

mfuzzey··on Tesla has used space characters in internal emails to identify leaks
You are quite right that open source done purely in free time usually takes much longer to be "finished" but that is more a question of the time available to spend on it than absence of pressure.

OSS projects that have paid developers often manage to avoid much of the pressure that occurs in closed source.

Some OSS projects like the kernel manage to harness companies as way of funding full time developers without giving them too much say in details or deadlines. A feature ships in Linux when it is ready and accepted by the maintainers and Linus not when some manager says it has to ship.

Of course this works far better for large projects that are essentially a "commons" like the kernel, less so for open source projects where most of the developers work for a single company.

mfuzzey··on Embedded programming is like web development
Depends a bit what is meant by embedded.

On the higher levels of embedded Linux there can be a grain of truth in this (especially wrt asynchronous model).

But the lower levels of embedded (both on bare metal MCUs) and on the lower level parts of embedded Linux require hardware skills without a web equivalent. While embedded software developers aren't normally expected to actually design boards they do have to be able read a schematic and review it concerning the software aspects (eg are the components used already well supported in software, are the right debug ports available etc). And quite often you have to debug with an osciloscape or logic analyser. Basic soldering to build cables etc is also very useful.

Also a lot of embedded requires understanding and modifying large codebases (eg the Linux kernel) whereas in web development its more about using existing libraries and frameworks more or less as is.

mfuzzey··on How to communicate effectively as a developer
I think it's far better give the reader as much information as reasonable and let him decicde how much he wants / needs to read. That can avoid multiple round trips and makes sure the whole picture is available to anyone who may need it.

Particularly as often the same message will be sent to multiple recieients that have different needs.

Of course you should try to structure the message so that people don't necessarilly have to read all of it.

For instance I recently sent a message about an analysis of the feasibility of changing a piece of hardware to a group that contained

* Managers * Hardware developers (in charge of implementing the hardware modification) * Software developers (in charge of adapting the software to the new hardware)

So it started with a brief summary of the idea and conclusion "yes it will work" (for the managers).

Continued with a some comments, questions addressed to the hardware team "the aproach is fine but we still need to sort out X,Y,Z"

And finished with a detailed description for the software team of how we should integrate the new hardware whilst remaining compatible with the existing.

mfuzzey··on My dad's resume and skills from 1980
I think you probably mean mercurial (hg) which is indeed written in python. Subversion (svn) is written in C.

Mercurial actually wasn't a bad choice at the beginning of the DVCS era on Windows as git didn't work well on that platform initially.

mfuzzey··on Ask HN: Why do software companies still insist on Estimation?
No one is talking about "never delivering any working software". You definitely do need to deliver working software and should do it in increments. That both shows the customer you are making progress and (more importantly) lets them adjust their requirements as they go along.

Software is different from most other branches of engineering in that it is far less limited by physics and that the requirements are far harder to define.

For example the requirements for a bridge or a building are relatively straight forward (size, load capacity, climatic resistance etc etc). That's not to say that designing the bridge or the building is necessarilly simple (though it probably is for small bridges and houses because we have centuries of experience with them) but even for complex construction projects the requirements are relatively simple even if the implementation may be very complex (think channel tunnel or mileau viaduc).

In software there are much flexibility that most customers don't know what they want until they see it. They generally aren't capable of saying up front what they really want (and when they try to they are often wrong and end up saying "yes, that's what I said I wanted but now I can see it it's not good".

mfuzzey··on Ask HN: Why do software companies still insist on Estimation?
There are estimates and estimates.

As a rough ballpark figure (1 day, 1 week, 1 month, 3 months, 6 months, 1 year, 2 years, 3 years, 5 years) estimates are doable and reasonable.

It's also reasonbable and doable to let scope be the factor rather than time. "Tell us the most important thing and we'll do that and deliver the results every couple of weeks, tell us when what you have is good enough".

You can also do fairly accurate estimates when you're basically just doing the same thing as you've already done many times or when the customer doesn't have to give much input. Most of the construction industry is like this because it's older, goverend by physics and building codes and we have a few standard models for most things. Most of the software industry isn't like that.

However for something new, where the customer doesn't really know what he wants in much detail accurate estimates aren't really possible. In this case anyone who purports to give you an accurate estimate is either lying or using extensive padding.

Customers, and non techinical people in general, have a hard time understanding what things are difficult / important from a complexity perspecitve. Often seemingly "simple" (to them) changes are actually very complex, and sometimes the other way.

mfuzzey··on Simulating protected mode in the Z80 [video]
I did that too, on a ZX80 back. Well after a week of doing it using a book and caclulating relative jumps (the backawards ones were worse) by hand I thought "there has to be a better way" and wrote my own assembler in BASIC (but I didn't know it was called an assembler at the time)
mfuzzey··on Qualcomm: Arm lawsuit motivated by greed, 'payback' for opposing Nvidia takeover
If we replaced lawyers with engineers things would be much better. The engineering work these companies do if fantastic but then they go and waste their time fighting about legalities instead of further advancing technology.
mfuzzey··on Removing SMS support from Signal Android (soon)
Do people still use SMS?

I haven't for many years, for sending (except for one time I wanted to test a modem driver SMS function).

I regularly use Signal, Telegram and Google chat and used to use whatsapp until it was banned by my employer but the only time I ever use SMS is to receive automatic authorisation SMSs

mfuzzey··on I have come to bury the BIOS, not to open it [video]
The problem isn't with device trees. And actually, ACPI is just like DT really (but more complicated because it has "methods" in addition to just properties). The difference is that you don't see it so much because the PC vendor has already written the ACPI tables.

The major difference on X86 is that it is (for historical reasons) much more standardised at the hardware level than on ARM (at least on embedded ARM, there is more standardisation in the ARM server space). It also makes more use of discoverable busses like USB and PCI so the parts that need to be described in ACPI are smaller than the parts that have to be described in DT on ARM (as much is either "implicitly standardised" or on a discoverable bus).

And that is because all PCs are basically the same whereas there is a huge variety in ARM SoC hardware and boards, mostly for understandable reasons (there are a huge variety of use cases and price points in embedded systems).

If you were to build an embedded X86 system not using a PC architecture (North bridge, South bridege etc) but using the processor and your own design you would have exactly the same problem.

That said you don't have to have "hardcoded firmware images for every single device" in the embedded ARM world.

I build an in house BSP for a product family of ~15 devices based on 3 different SoCs and we have a single kernel and userspace (Debian based) for all of them. All the DTs are on the boot partition and the bootloader selects the right one based on hardware information (typically a small EEPROM).

The only part that has to be different is the bootloader itself (and then not different for every device but for each SoC) - so we have 3 bootloaders all supplied as part of the BSP and when building the install media we say which one to write.

Even that, in theory, could be avoided, at least on SoCs with the same ISA by improving u-boot a bit to make stuff like clocks configurable from data (the u-boot device tree) like the kernel already does. This may one day be possible once u-boot completely adopts the driver model.

mfuzzey··on Native Linux GPU Driver for Apple M1
GPUs tend to evolve over time rather than change radically. So even if the hardware is obselete before the work is finsihed the driver for the next generation will start from a much better point than the first one.

Also it will be useable for at least some usecases, even if not AAA games, before the hardware is obselete.

mfuzzey··on A CTO should be technical
Yes but you already gave plenty of reasons before resorting to "that's the way we do things". And I think that's fine. What wouldn't have been fine would have been to skip the explanations.

Most people, given explanations, will accept them even if they don't agree with them. And quite often they will realize that there is more to the issue than they originally thought.

mfuzzey··on The Lost Art of System Administration
Actually this was the much of the reason for the creation of the Raspberry Pi.

Its creator, Eben Upton was a director of studies at Cambridge university and realised that there were fewer CS applicants than in the past and that many of those that did apply knew far much less about computers and programming through there own "tinkering" than previously.

He saw that this was due to modern computers being far more opaque than the systems he had used as a kid (like the BBC Micro). So he decided to build something to address that issue that was open enough to understand the workings and cheap enough that people wouldn't be discouraged from tinkering due to the risk of breaking it.

It seems to have worked quite well...

mfuzzey··on What Should You Work On?
I think a big part of the "problem" is that the skill set required to be an "innovator" in some field (coming up with an idea and making it work) is generally very different to that of being an "entrepreneur" (building a sucessful business around it).

It's quite rare to find the two in a single person and very often the best on one side are the worse on the other.

mfuzzey··on Pay Transparency: European Commission proposes measures
The EU can take them to court. But most of the time the process is fairly automatic and member states just do it (they may be a little late occasionally)
mfuzzey··on Minitel: The Online World France Built Before the Web (2017)
Yes Prestel was the same technology as minitel.

But the French bootstrapped the ecosystem by giving everyone who wanted it a free minitel instead of a printed directory which didn't happen in the UK, due to that Prestel never really took off.

mfuzzey··on Ask HN: Why is software quality always decreasing?
I don't think it's just Linus (though he certainly helps).

The kernel, unlike many other understaffed open source projects, has lots of developers working on it (the majority paid these days). At the same time, unlike software built by corporations, there are no non techinical PHBs to say "ship it now and clean it up later".

Linux has found the sweet spot of getting companies on board to provide paid developers (it's much easier to do good work when you can allocate large blocks of time to it because your're paid to do it) whilst at the same time preventing them having too much say over the technical directions and timelines. Typically a company employing kernel developers will have a say in what they do (drivers, core kernel, ...) but not on how they do it.

But it's not really a model that can work for all open source software.

For related reasons I think that companies that build lots of software but whose product isn't actually software (like Google that is really an advertising company) often produce better quality software than pure software companies (like Microsoft) because the technical staff are left more alone by management who prefer to concentrate on the "real business"

← PreviousPage 4 of 4