skysight-inc/HackerNews huggingface dataset:
Type II Fun – fun only in retrospect, hateful while it’s happening
..or how to live in a cage and be cool with it
https://web.archive.org/web/20220321222926/https://plus.math...
I think you were misunderstanding something. Why would every code change cause a compile and test across the entire company? That is to say; not only does that not scale, it’s totally unnecessary*. Only the downstream consumers of a change are rebuilt and tested, like you’d expect (see: bazel and the monstrous makefile before that). In this sense, the fact that Google uses a monorepo is mostly an implementation detail. It has some impact on the company’s workflows and tooling, but not its software architecture.

* unless you’re changing a very common dependency, of course, and Google has tooling for this.
> "Screw It, This Works"™ Alliance.

Where is the conference and the website to download a frameable printable "Certified SITW Master" certificate?
… i.e. ‘There are even people who ordered in 2017 who still haven't got their phones’ is completely accurate.
When I joined Google in 2006, the message was "don't write anything in an email you don't want to see in a NYT headline".

Good advice for all digital communications. You have to assume the authorities, and others, are listening.
I have been around for a while too and I think I can answer the rethorical question: it's a great fulcrum upon which to build teams and spring careers, and by the time problems have calcified there's been enough turnover or promotions that the reason why they are in place is completely lost.
I do not say this with bitterness accumulated while building them: on the contrary, it's something I've usually realised only much later, when it was too late (and more than once).
Yes, most recently, any barnacle that can be stapled onto the monstrosity that is the Modern Data Stack. Before then, for Kubernetes. Before then, for the Hadoop ecosystem. (These all have value -- even we work here -- but the ecosystems can't possibly support all the co's in each.)

For whatever the things of the year, a VC team will fund say 20 startups with the hope that 1-2 do well.. and are ok for the rest to flop. It's expected that 18-19 we're bad ideas, but they all still get giant sales/marketing/engineering staffs that 99% co's won't in order for the VC to have it get a go and then find out which is the winner. That is why you especially shouldn't trust speakers, marketers, and sales staff from a VC co: the financials show it's 95% chance to not be as advertised and then disappear on you in some financial shell game.
Not a Startup, didn't follow Startup trajectory. They were building a tidy little business - except they moved past the little part.

When you start, you choose between investors+growth=exit or profitable+steady=tidy

Greatly simplified of course but Craigslist chose the second path.
Good advice, except for the hipster `&& \` stuff. Use the `—squash` flag instead.
You mean the "do not track" header? Advertisers won't respect any setting that makes it that easy to opt out.
>Not hearing enough about this reminds me of the overly cheerful propaganda

Ukrainian TV regularly describes the situation there - Kherson is lost, Berdyansk is lost, Mariupol is like Stalingrad when the defenders were pushed right to the Volga, Nikolaev - still not, and there is fighting around with various small villages and towns changing hands. Odessa - preparing for invasion, Russian Navy assault group is there and the smaller ships are hanging on the horizon periodically shelling the city. Some radars, etc. taken out by the bombing. I wonder what would you have to add/correct here.

Granted, Odessa falling will be huge in all respects. It would make the situation worse tremendously for Ukraine. It will also be a pretty tall order for Russian propaganda as for example i couldn't say which city is more dear to Russians - Kiev or Odessa. And Odessa will be fighting. It will be at least order of magnitude bigger/longer battle than Mariupol (especially given that Russian forces haven't yet encircled Odessa which is hard without taking Nikolaev,
and attempting to take Odessa just by an assault from sea onto the mined beaches would be very risky). So, it isn't exactly a given that Russia can sustain such a fight given the Russian losses that have already happened and are going to happen - Russia is already starting to bring in military college cadets as well as calling reservists. Russia also wants Belarussian forces to join, yet given the Belarussian society feelings Lukashenko is afraid that the Belarussian army will desert to Ukrainians and would potentially turn against him while hoping that staying off may allow him to not go down with Putin/Russia.

Russia has also significantly decreased close air support for ground forces because of heavy losses of planes and helicopters. Thus they mostly bomb the cities from distance using unguided artillery and unguided MRLS like Grad/Smerch as well as unguided air bombing from higher altitudes. That mostly hits civilian population and civilian buildings/infrastructure while having much smaller effect against military targets. And thus even after such massive multi-days bombings the Russian ground forces still can't move ahead much.
Having to give everything some weeks or months or years of outrage, and only able to subside when the new outrage target emerges has a tendency to make everything [feel] less stable.

Maybe it’s not less stable, we are just reacting to it more.

We act like no one has ever seen inflation or a stupid war or a recession. It’s got to be the worst thing that’s ever happened with no future left for humanity (I won’t even digress into the climate discussion, but I could).

I don’t think this is healthy. Being addicted to your own brain stress hormone chemistry isn’t a beneficial disposition. So I somewhat refuse to participate. I accept that 8 million in the world died of covid and that some stuff will cost more this year than last, and that I may not get the same proportion of a raise. Maybe I’ll go 8 years between new cars instead of 6, but am I really that abused by this?

TLDR; I stopped hyperventilating over every thing social and traditional media told me to be outraged about, and I’m happier.
A weather delay does not mean you get more time to get your payload onboard.
Building a Habitable Computing Environment[1] was a recent blush i had with a "literate" computing project, this time less about programming specifically & about system setup/config.

I confess I'd rather forgotten what literate specifically meant beyond code comments describing the flow, but i did find it to be a remarkably comprehensive & understandable document, a prime example of how we might teach & understand computing. Even if it did leave me puzzling out what a number of the many many many scripts were for!

Certainly the overall project of computing needs a lot of help, ways to explain itself. Ive seen tons and tons and tons of "dotfiles" projects, but none have gotten anywhere near to as comprehensible as this literate programming project, from what I've seen.

[1] https://tess.oconnor.cx/config/hobercfg.html https://news.ycombinator.com/item?id=30748033 (19 points, 1d ago, 0 comments)
Note that the Anbox developers have developed a more modern solution called Waydroid, you should look into switching.

Edit: looks like you're already aware of that :)
Thanks for the explanation, that is very helpful.
Before microservices were a thing, I had the chance to work on a couple of telecom systems written in Erlang/OTP, but it wasn't until years later that I realized we were already doing most of the things people were using microservices for, with the single exception of being polyglot (although Elixir and Gleam are starting to challenge that).

Small teams were dealing with specific functionality, and they were largely autonomous as long as we agree upon the API, which was all done via Erlang's very elegant message passing system. Scalability was automatic, part of the runtime. We had system-wide visibility and anyone could test anything even on their own computers. We didn't have to practice defensive programming thanks to OTP, and any systemic failure was easier to detect and fix. Updates could be applied in hot, while the system was running, one of the nicest features of the BEAM, that microservices try to address.

All the complexity associated with microservices, or even Kubernetes and service meshes, are ultimately a way to achieve some sort of "polyglot BEAM". But I question if it's really worth it for all use cases. A lot of the "old" technology has kept evolving nicely, and I'd be perfectly fine using it to achieve the required business outcomes.
> Even the most fierce predators don't go around attacking random shit for the hell of it unless they are actually hungry.

That is incorrect. Some predators do. You do, and you are not random. You are a threat on their territory and by your own admission, an aggressive threat with no respect for them as a pack or their territory.
You can say those cases are frivolous, but it hasn't stopped Robin Thicke from being ordered to pay out millions. Fair use doesn't always prevail in court or even within youtube when it should.

There is a chilling effect on creativity when this happens. There will be fewer people willing to risk a massive financial burden by creating something independently if sounding too similar to something else could get you sued into bankruptcy by a group that already has essentially endless wealth.

Currently, the industry doesn't even want the burden of dealing with the court system. They put pressure on youtube under threat of legal action to act on their behalf for free. It's the same with ISPs. The DMCA gave ISPs legal immunity from acts of copyright infringement committed by their subscribers, but only under very specific and poorly defined circumstances.

Right now, they are fighting in courts against half a dozen different ISPs to try to define that wording so that they can make unsubstantiated accusations against internet users and if an ISP doesn't cut the accused individual off from their service forever, the ISP can be sued for billions. No court case or evidence proving that the subscriber has done anything will be needed. If they say someone did it often enough, their service has to be cut off forever. Because some users don't have many options for internet access getting permanently kicked off an ISP can mean getting cut off from the internet entirely, but court cases are time consuming for the media industry so they are willing to let that happen if it means they can make your ISP into their free copyright police. So far, in the courts the media industry is winning.
Plain Text – Dylan Beattie – NDC Oslo 2021 [video]
I'm curious how the pinephone pro compares, I've been thinking of buying it.
D) is asserted in the article with no supporting evidence.
Do you visit a grocery store or similar establishment for at least 30 minutes per week?

If so then there is potential for charging infrastructure to solve your use case without requiring every person to have home charging.

DC fast charge infrastructure is growing at a huge rate. We have tested designs that are being mass manufactured and are installable in basically any parking lot with enough nearby grid capacity.

New charger locations are being added literally daily across the US and the world.

Tesla: https://supercharge.info

Others (US): https://fastcharger.info

It's definitely going to be a different model than gas stations, but I think we can continue to install huge amounts of DC charging capacity at stores and along highways, combined with slower AC charging capacity at apartments, office buildings, etc, easier than we could install enough battery-swap capacity to handle the EV transition.
It is arbitrary, but we have to draw the line somewhere.

It is not about money, tax is about money. This is about the extra work needed to accommodate for said obligations, it can involve several full time jobs, and the state considers that it is too much for a company of less than 50 employees.

Really, it is a lot of paperwork, and the more a company spends on paperwork, the less there is to pay employees.
Google slides printing clear PNGs as black? It's a bug with PNG format
Which Ukraine isn't. So what's the parallel again?

Your statement makes Ukraine parallel to Czechoslovakia, not Poland.
The opportunity will find you
No, this is a non-problem. If Microsoft stuck with Win32, just like how Apple stuck with Cocoa, this wouldn't be an issue.
The general idea behind any 'pure' Linux phone is to have a device that you can trust at least as much as a desktop running Linux. Security is definitely a key aspect for many. But it's also the flexibility of not being locked in to anything on the software side. Ideally, it also extends the useful life of the device as when vulnerabilities and bugs are found, they can be fixed rather than junking the device for lack of updates. It's still pretty early days re: 'full' Linux on mobile and so it doesn't look like much yet... it takes time. Desktop Linux didn't look like much in 1994 either.

I'm not familiar with GrapheneOS but I assume it follows the usual model when repurposing Android devices of taking various closed source blobs (i.e. drivers etc) and rebuilding the open source bits around them? If so, this approach usually locks you into a Linux kernel version to remain compatible with the blobs which limits you on kernel features and fixes as well as who knows what exposure the blobs have to offer, which also will likely never get updates.
Ukrainian forces have been shelling civilian areas in Donetsk and Lugansk for the past eight years killing over 14,000 men, women, and children. This isn’t even disputed in the Western press, it’s just not talked about so people like you stay confused and ignorant.
It's just a mindset.

People complain about things all the time. As you listen/watch/read/etc, listen to their complaints, and think about how you might make that situation better with technology you're familiar with. I find that I think of several ideas a week with this approach.

The next step is to think about the product definition. What _exactly_ does it do? How does it work? How much will that cost to operate? How much is it worth to the potential customer? Given those two figures, is this going to be an opportunity you want to investigate further?

If it passes the first simple tests, then you need to expand a bit: how many possible customers are there? Is it tied to geography or language or culture? How will you market the product, and what will acquiring a customer cost you? Do you have a free tier? A trial period? Can there be a premium tier?

If you can get past this basic analysis, then you need to put some more time into it. Most ideas won't get this far. You should now try to actually talk to some potential customers, see if your idea will actually work for them, and refine the product itself, its business model, and the implementation costs.

There are many, many websites that describe how to do this. If you're not already a reader, maybe try indiehackers.com as a starting point?
Smells like money laundering just a whole different level
I'd say this may be an overly cynical view of founders even. I don't think they're usually that calculating; my suspicion is that most of them believe their own hype and really do think their business is going to be the next Google. I'd say Adam Nuemann epitomizes this to me. He could be a calculating cynical genius, but he just seems like someone who in another time would have been either a rockstar or religious guru, but managed to hook up with a different crowd and everyone got caught up thinking an office sub-leasing company was some profound invention.
And designers.
Is type 2 fun a good idea? I haven't been able to decide for myself. I'm never sure whether doing these sorts of things has actually been a good use of my time. It probably helps me grow or something, but God does it suck a lot of the time.
with my own devices, every one. longest run i had was ~1 year. most were much shorter like 2-3mos
You'll find no argument from me on that score. It's just a matter of which is the least suck for any given person's needs at this point.
The problem with modularization and its supposed benefit of autonomy is that the universe disagrees. Everything is connected whether you like it or not.

A pure microservice ideally has no state, or if it does, its own data store. That's awesome, until the front-end team wants a joined result (query) from multiple microservices, and thus data stores.

What are you going to do now? Build a proxy microservice in front of it? With shit performance, no referential integrity, and hard dependencies? More likely, you won't do that, so the front-end is going to be looping calls. 50 network requests with each having parsing overhead just to render a simple list of things.

The autonomous team has their own roadmap, which in a connected universe (the one I live in) is a problem, not a solution. The business team really needs that mobile app to be shipped soon, but the micro service team has no room on the backlog for another 6 months to build the part needed. A business prioritization problem? Perhaps, but it just shows that autonomy is largely a fantasy. The reality is that as soon as something is "one team away" everything becomes dramatically slower and less flexible. That's the price of autonomy.

All of this is like a 100 times worse than the ridiculed traditional software stacks, but hey, I'm not complaining. In a perverted way I benefit from delusional tech choices. It keeps me paid.
Thanks for the detailed information. I appreciate it.
An outlier that predates the modern SV scene
Perhaps it's time I learned some erlang :)
Hungarian here! The Gömböc is awesome, I have a small aluminium one on my bookshelf.

You can get one here, I think they (I'm not affiliated) ship internationally: https://gomboc-shop.com/
Correct me if I'm wrong, but Lanai was designed by Jakov. Who sadly and unexpectedly passed away a few weeks ago.
Maybe, but in the 8 years of Russia occupying Crimea the media never called Ukraine an intractable quagmire for Russia, they mostly ignored it.
Another theory: type 1 is fun now, type 2 is fun in hindsight, type 3 seems like it would be fun looking forward but turns out to be awful.
China Eastern Airlines Flight 5735 Crash 21 March 2022
Oh sure, you always need to listen to the requests - especially for existing systems.

I had one set of legacy workflows I once replaced that rough went like:

1) Export data from system A to a CSV.

2) Remove/reorder a few columns manually in excel

3) Get manual approval from a manager

4) Email to different department

5) Upload to system B via their import function

The request was to just give us an "export with the right format," thus replacing step 1 & 2. But we also heard complaints from the team doing step #5 that it was pointless and could be automated, and from the managers in #3 that really they used a simple rule that if X < Y approve otherwise deny.

So we thought we could build a workflow automation that connected the two systems via API, with an automated approval and flag those that didn't meet the rule for manual review.

So we propose this, everyone agrees. We build a pilot, test it, everyone likes it. Then go to release it and find out that this ignores any number of cases where in #2 there where hidden workflows like "any time you see scenario W, send it to Jenny and she runs a formula on these columns to adjust" or "actually the manager never approves anything from this department related to an acquisition because of factor x, and it needs to go to this different group." There was about a dozen similar requirements. Could we have identified these sooner? On other projects we usually did, but this project went further than most before they were detected.

We ended up temporarily building that export button requested by the users originally and were planning to fix the API based workflow ... but then there was a reorg and priorities shifted. We never came back to project and AFAIK those groups still work via email. But they don't do nearly as much excel busywork as before ¯\_(ツ)_/¯
There's a degree to which I agree with this, but the advantage monoliths have is the "opinionated" frameworks (chiefly Rails, Django and the like) that hand-hold a less competent team towards a sane design.

In comparison, building a good set of microservices is a minefield of infinite possibilities, with each decision about where a particular responsibility or piece of data should live being quite significant and often quite painful to change your mind about.
This is why I try to never ask "why don't you do X" without making it clear that I'm using it as a forcing function to satisfy my own curiosity, rather than trying to sneer at folks. Often this requires being a bit more verbose, but I've personally always found a bare "why don't you do X?" without any other context to come across as sneering.

But yes, I also try to interpret it charitably as well too. I just also try to make my own curiosity clear on the flip side.
I think it's as good as it gets. The rough principal is there: You have one file, and you can derive the documentation and the program from it with different compilers.

The idea of reading code like a book seems extremely flawed to me, and any attempts to create such languages either look like regular source code with slightly different syntax or are barely comprehensible (e.g. TeX)
"Not a Startup, didn't follow Startup trajectory."

Every company was once a startup.
As I wrote above, the only time I've seen mine falter was at 6F (last year's mega freeze in Austin). It occasionally gets to 13F-15F in the winter, and the heat pump works in this environment without having to resort to "aux heat". I'm sure it's become rather inefficient, but it does work.
“ It was more relevant in a time when the majority of a country's economy was located in the countryside - where people physically grew food, produced goods on a small scale etc.”

This seems to describe Ukraine after Russia destroyed the city center…
I’ve always used knowem but I prefer this UI
Modern fire codes are good enough that I’d be shocked if a code compliant new building with no windows is less safe than a pre-1960s building with windows.
Fancy features will cost more. But just a plain old video file on s3 works fine enough for must purposes.
Relying on the distinction between reference and value equality here is clearly not a good practice - as a fix, the author recommends only using primitive types as dependencies.
I'm most curious how this impression is going to age over the next year or two, considering the new competition with the Pinephone Pro that's coming out. While Kudos to Purism is certainly due for developing the Librem 5 in the first place, and for kickstarting projects like Phosh[2] which is now used by many mobile Linux distros, they're really struggled (as mentioned re: timeline in this article) with shipping hardware.

Conversely, Pine64 hardware seems to have a pretty dedicated developer community among the various mobile Linux distros, and considering the significantly improved specs of the Pinephone Pro over the original model, I'm wondering how many people will opt for the even-more-expensive Librem 5 in the future after the Pro has been out for a bit and some of the early-adopter kinks have been worked out, considering the issues Purism has had seemed to have with reliably getting inventory out.

[1] https://www.pine64.org/pinephonepro/

[2] https://developer.puri.sm/Librem5/Software_Reference/Environ...
> a sort of family nickname

Huh? The cognomen is the individual part of a Roman name. Nothing "family" about it.
After having reviewed 300+ tech stacks, I can say with certainty there are use for AND against microservices. The benefits are numerous, they just tend to be overused and not implemented consistently the appropriate way.