HNHacker News
TopNewBestAskShowJobs

kakwa_

1,465 karma · joined August 10, 2015

submissionscomments
kakwa_··on Twitter’s Rebrand to X Could Be a Trademark Nightmare Thanks to Microsoft
I guess it's an explainable reaction given it was the other way around for years.

Go back 2 or 3 years ago and the level of idolization and fanboyism was just incredibly high.

Tons of 'Elon is a genius' or 'Elon could fix [insert global issue]' like comments.

It was just really annoying for a lot of people. And now, with Musk's recent 'reversals', some of these people are becoming very vocal, swinging things at the other extreme.

kakwa_··on Netscape and Sun announce JavaScript (1995)
I'm really confused, is JavaScript just a rebranding of Java applets? maybe with some minor overlays on top of it?

That sounds more like a marketing stunt to me.

kakwa_··on Dark Waters of Self-Delusion: The crash of Transair flight 810
> The captain's unclear headspace became evident by his protracted tirade. He was likely mentally unfit for the task of captaining that day, and the rant was evidence of it.

Reading through the article, that's not the feel I get. As presented by the article, the captain state of mind did had an effect, he was not at 100% of its mental capacities.

But reading through the CVR transcript, the communication between the first officer and captain was good, and the crew did fly the plane from take-off up until the end which implies that the breach of the "sterile cockpit" rule before take-off did not had any major effect. They were fully focused on the task of flying immediately before and during the emergency.

They simply both made mistakes/bad judgement calls.

In fairness, the captain did make more mistakes, and some of these mistakes maybe may have been avoided if he was in a different state of mind. But at the same time he was placed in a situation where these mistakes could occur and become catastrophic (very old and unreliable plane lacking maintenance and ways to easily troubleshoot an engine failure).

In my opinion, he, or any other pilot could have made the same mistakes even in a right state of mind. It's also an unreasonable assumption that pilots will always operate at 100% of their capacity.

kakwa_··on 11 years of hosting a SaaS
> We will never know, but what we know for sure is not implementing these advice made him successful

"Made him successful" implies a causality that is a bit too strong.

Indeed, we will never know for sure.

Maybe implementing these advice would have impeded development of other critical areas of his business.

Maybe it would have would have helped make is business more successful as he would have had a more reliable product.

Or maybe the business impact would have been neutral, but would have resulted in better quality of life/less stress for him and his employees.

But in general, the way I read this article is: they made good decisions overall, but as everything in the world, it was not optimal (switching platform too early, making some big mistakes like the credit card one, etc).

It's a very interesting read nonetheless, with clear take away:

* chose boring tech you know and focus on your product, not the tech, specially in the early days

* grow your infrastructure and complexity with your product needs

* accept you will mess-up but properly learn from it, and grow your organizational knowledge, structure and processes accordingly.

kakwa_··on Functionality that has been deprecated in Red Hat Enterprise Linux 9
Well, better doesn't mean good.
kakwa_··on System D
Système D has both a positive and negative connotation. There is indeed a resourceful part, but also an 'it's an ugly hack' part (but justified by the circumstances).

As an example, my parents used to leave in Africa, and at the time, the water supply system was unreliable, so my father hooked-up a 100 litters drum so that we at least had some water for essential needs during outages. Smart given the circumstances but a proper water supply would have been preferable.

kakwa_··on Show HN: I was frustrated with pricing of PagerDuty et al., so made one myself
Also, the cost of the monitored service being down far exceed (hopefully) any compensation for SLA breach.

Honestly, PD is probably the service I would the least complain about in our (large org) monitoring chain.

At least, it's reliable, which cannot be said of Newrelic for example.

kakwa_··on Tell HN: ChatGPT is fantastic for finding and solving issues in logs
As another side note, using ChatGPT as a search engine is not so great.

Recently, I was trying to find golang libraries for managing authorization. The first one was a well known library (I was incidentally trying to avoid).

But the others 4 were complete were completely fantasy projects. ChatGPT simply invented complete projects with descriptions and github urls.

Interestingly, looking at the urls, it seemed to actually be a composition of authors working on the subject and similar project in other languages.

I also observed the same behavior when I tried to find community resale/recycling centers (ressourcerie in French) in my neighborhood, and sure enough it generated a bunch of fake addresses.

It's logical in hindsight, ChatGPT is a generative AI after all. But these results left me scratching my head at first.

kakwa_··on Parsing the .DS_Store File Format (2018)
This article makes me wonder: what tools do you use when reversing a custom file format?

Personally, having done so recently to reverse a custom game archive format, I have only used the usual hexdump, strings, grep, sed, etc. I'm wondering if there are more powerful tools to do this kind of job?

kakwa_··on Dragonfly Is Production Ready (and we raised $21M)
Restricting Usage or Distribution makes it de-facto not OSS.

It's actually a slightly different form of an old debate. I'm thinking in particular about the Crockford license (the MIT-like one with "The Software shall be used for Good, not Evil." bit). It was determined to be non-free quite a while back due to such restrictions.

That being said, it hard to be a commercially successful software editor with an OSS model (RethinkDB comes to mind).

I do understand why BSL exists, but it feels to me like an unsatisfactory compromise.

kakwa_··on Dragonfly Is Production Ready (and we raised $21M)
Honestly, I don't think giving 21m to DragonflyBSD would be a good idea, not sure how the project could adapt back to a shoestring budget after the money runs out.

I would not be against giving them a few 100Ks so that they could get one or two full time developers however.

(joke (but also food for thoughts): alternatively, just "safe" invest the 21M. At 3% interest rate, that 630k per year, enough for ~2 to 10 developers depending on the geo. An OSS project can do a lot of things with this kind of budget).

kakwa_··on 40% of the code GitHub Copilot users check-in is AI generated and unmodified
In a recent personal C project (a custom archive file extractor), I have used chatgpt to generate tons of unit tests.

And honestly, I was extremely impressed. With a bit of context, it was able to generate almost correct test data for a fairly complex binary data format.

I've also leverage it heavily to:

* generate doxygen comments

* get usage examples of libs I never used

* create a whole bunch of utils functions.

And honestly for all these tedious tasks, it has done a far better job than I would ever had.

Comments were consistent in styling, the base examples were fairly good, and the utils functions were well made, specially the error handling (which I would probably have semi-consciously skipped tbh).

In fairness, I modified most of this code slightly to make it fit my project structure, or tweaked it a bit what the IA didn't quite get it right.

(it never fully understood some offset fields in the file format, but got pretty close to at times. And in fairness my naming for these offset fields was a bit questionable).

Heck, as a test, I even threw at it an RFC-like spec of the file format, and asked him to generate a python parser. The result was not 100% correct, but definitely a good start to iterate on.

In the end, this side project took me 2 weeks to implement with chatgpt probably saving around 1 week of dev. It also greatly helped improving the quality of the project (better doc, better tests).

kakwa_··on Ask HN: What would be your stack if you are building an MVP today?
Golang (most likely a rest API using the Echo framework).

Postgres and maybe Redis if I need a message queue or cache.

React for the front.

Nginx and certbot for the reverse proxy.

Everything hosted on a cheap OVH VPs.

Mostly because it's what I am familiar with. Plus it's cheap specially since I already have the VPs anyway.

kakwa_··on Fun with Gentoo: Why don't we just shuffle those ROP gadgets away?
As a student, I've actually put an overheating PowerBook G4 in a fridge just to finish an install
kakwa_··on Ask HN: How do you test SQL?
We apply the overall same strategy (individual DB for each test created from a template).

Our whole test suite (integration + unit tests) takes ~80 seconds to run for ~800 integration tests (each with their own DB) and 300 unit tests. And that's on my dev laptop (T14s, cpu: i7-1185G7) without much optimization (mainly fsync = off in postgresql.conf).

In fact, I just ran a quick test, and just putting the DB on a tmpfs cuts that time to ~40 seconds.

So overall 0.1 to 0.05 second per test on average, same ballpark as parent (and it's kind of an over estimation actually since we have a dozen or so of slow tests taking 5 to 10 seconds).

Note that the tests are run in parallel however.

kakwa_··on Ask HN: How do you test SQL?
We do that too, in fact it's not only the DB that run in docker, but the whole build + CI process.

Our overall strategy is to create a master "test" DB with a test dataset, and for each test, copy this master DB to a test specific DB (CREATE DATABASE <testdb> TEMPLATE <master>) so that tests can run in parallel without interfering with each other and without the significant overhead of a "from scratch" DB initialization.

For schema migrations, we build the "branch/PR" version and the "main" version, then we check that 'init DB with "main" + migration with the "branch/PR" version' results in the same schema as 'init the DB directly with the "branch/PR" version' using apgdiff.

This strategy could probably be extended to migrating from every older version by building each tag, but we don't have that need.

We could also probably improve checks on the data itself however as for now, we only check the schemas.

Few things to note:

* it's still possible to run the tests outside of docker and use a local DB instead with some light setup (it's faster than running everything in docker when developing)

* docker argument --tmpfs <dir/of/db> is quite good, assuming you have enough ram for your dataset

* few configuration tweaks on the DB, like max connection might be necessary.

Overall, we are quite happy with this setup as it permits to implement end to end integration tests quite easily without spending too much time mocking dependencies.

As a general pattern, I find instantiating dependencies internal to your service (like a DB or Queue) to be the way to go, with mocking only for external dependencies (like external APIs) or exceptionally to reach a specific code branch (specially error handling sections).

kakwa_··on First LNG tanker arrives at Germany's new floating terminal
> it’s incredible how fast Germany built these new terminals.

Except they weren't really "built" in 9 months. Höegh Esperanza (the floating terminal), was commissioned in 2018.

https://en.wikipedia.org/wiki/H%C3%B6egh_Esperanza

In reality, oversimplifying wildly, it took 9 months to negotiate the contract and "plug" this preexisting terminal into the German gas network.

However, it's still impressive that our societies have tools like that available to handle unforeseen situations and crisis.

kakwa_··on France bans Office 365 and Google Docs from schools and public administration
The Gendarmerie also contributes to OSS quite significantly.

Lemonldap (SSO solution) for example.

kakwa_··on Why Twitter didn’t go down: From a real Twitter SRE
That's likely optimistic.

Maybe the user facing site, but that's just the tip of the iceberg.

There are plenty of internal/backend/restricted systems to support and/or monetize this part.

And that's not counting the huge number of support people & moderators needed.

kakwa_··on Boeing's 737 Max Software Outsourced to $9-an-Hour Engineers (2019)
The $9/h is obviously click baity, by itself it doesn't mean the software was malfunctioning.

But it highlights a general policy of outsourcing to the lowest bidder. This is generally a symptom of badly managed company placing spreadsheet profits above everything and seeing product development and Engineering as a cost center, which given the current Boeing situation, is quite telling.

kakwa_··on Europe's Newest Nuclear Reactor Eases Finland's Power Problems
> do you think the gas taps will just be turned back on?

Well, kind of, whatever the outcome, Russia will have depleted much of its military strength and will need to reequip its army. That costs money, so they will be more or less forced (or even willing in case of a coup against Putin) to sell gas to the EU.

The real question is more what the EU will do. Most likely, the EU (or each country individually) will really want to diversify their energy sources and maybe be more self-reliant to not be subject to one actor like it is right now.

Nuclear may be one of the responses, but it's far from the only one.

On a side note, Russia is providing ~25% of the EU's uranium right now (in fairness, this dependency is easier to circumvent compared to the gas one).

kakwa_··on Europe's Newest Nuclear Reactor Eases Finland's Power Problems
Yes, but most of things built during wartime are quick expedients, not long term planned things.

For example, in both WW1 and WW2 a lot of capital ship constructions were canceled in favor of cheap quick to built ships (like cheap destroyers or submarines).

The liberty ships are another example, these things were kind of obsolete at launch and not really geared toward lasting that long (5 years engineered life span).

Lastly, we are not exactly in a wartime situation. Some emergency decisions need to be made (temporary LNG terminals for example), and also Europe needs to have an hard look at its energy policies, but that's a long term and for more complex set of decisions.

A long term commitment to nuclear energy is not something that could and even should be taken in the heat of the moment.

kakwa_··on The super-rich ‘preppers’ planning to save themselves
"Après moi, le déluge" (Louis XV).

For ages, people in power position have been at the same time, both nihilistic, knowingly pushing toward the cliff and afraid of an impending collapse.

This is both creepy and reassuring, despite all that humanity has survived (with blood and tears but survived). This elites on the other end? Sometimes they did, sometimes they didn't, and at the very least not in the same position of power.

kakwa_··on AI-Generated Bible Art
I'm really wondering how many out of these are almost copy pastes of existing pictures. I just saw down the list an almost verbatim copy of the well known photo of the heart in the Amazon, so I'm really skeptical.
kakwa_··on Using the same Arch Linux installation for a decade
Personally, I am using Debian Sid. The only somewhat painful part are the proprietary Nvidia drivers when a significant kernel upgrade occurs, but it's usually just a matter of selecting an older kernel in grub for a few days. Other than that, it's really up to date, and with an extensive choice of packages.
kakwa_··on Oncall Compensation for Software Engineers
Another big parameter is how many people are in the on-call rotation.

If the rotation is spread only on 2 or 3 Ops in the team, well, being on-call every other week, even on reliable systems, can really suck (given you must always make yourself available).

Things can get even worse in periods with a lot of PTOs like Summer or Christmas. During these periods, if the team is small, being on-call 2 or 3 weeks in a row is not uncommon.

kakwa_··on OneDev – A Lightweight Gitlab Alternative
Just in case, check the number of workers (assuming you are using mpm worker and not mpm event)
kakwa_··on Notre Dame rises again
Well, that's only a recent development (compared to the life span of these historical buildings).

A lot of these Cathedrals managed to survive long period of neglect with minimal to no maintenance.

There is a bit of survivor bias in there, but it's also a testament to the durability of these buildings.

kakwa_··on Notre Dame rises again
Another beautiful cathedral around Paris is Amiens.

It's a more recent cathedral than Notre-Dame, and consequently higher, nearly as high as Beauvais in fact, but this one didn't collapse (even if she needed a very costly iron belt to stay that way).

It's also located near the quite nice Saint Leu neighborhood with tons of restaurants near the main canal. And right next to Saint Leu, you have the Hortillonnages (crisscross of waterways and small gardens) which are also worth a visit (it's possible to rent boats to visit them).

It's only ~1 hour away from Paris (Gare du Nord) by train, and definitely worth spending a day there in my opinion. Just don't be afraid by the sight of the tour Perret when exiting the station at Amiens ^^.

kakwa_··on Being on call sucks
Compared to the article, many on-call situations could suck even more.

In a past assignment, I was on-call for a service managing thousands of customer instances each with a different version of an highly customizable application (basically an SDK) developed by another team.

The result was on-call being basically a working day, getting paged on average every hour and at worst needing to track 2 or 3 war rooms in parallel.

Also you felt powerless because while being accountable for the availability of the service, a lot of the issues actually came from customer implementations overloading their instance or product bugs which would get ignored for years and if a fix was done it would take even more years to be deployed due to the difficulties in updating the application.

The only saving graces were:

* It was in a large international org, so it was "follow the Sun", no midnight calls, only 8 hours shifts (11:00 to 19:00)

* I live in a country were it's a legal requirement to compensate employees for being on-call

Now, I've switched to a team were we handle on-call on services we control end to end (code and deployment), and it has been far less stressful.

← PreviousPage 5 of 19Next →