skysight-inc/HackerNews huggingface dataset:
$5000 in a third world country is quite a lot.

For context, according to CEIC data [1], the average salary in Algeria is about $300 per month. That "dirt cheap" project of yours is more than a year's worth of labor.

Locally priced goods may be cheaper, but the US does benefit from a more direct shipping line with China (where most of these products come from, especially cheap solar panels). There's repair costs to be taken into account and if these become a necessity, you'll also have to take into account some kind of protection for when those without the means to buy one of these setups become desperate.

It's true that solar is relatively safe and cheap compared to other power sources, but projects like these are difficult to map to places where they can make a life-or-death difference. If things were that easy, we'd probably cover a patch of Sahara desert with solar panels and power the entire African continent for decades, with power to spare to export to other continents.

[1]: https://www.ceicdata.com/en/algeria/average-monthly-wages
The lifetime value of having a patent is much higher than the lifetime value of any specific patent. That's because the scam works whether the patent is valuable or not. Invalidating a patent costs them the time it takes to get a new one.
I have to agree with this.

Most of my immediate team are in another continent, others 100 miles away.

I'm used to working 'remotely' to my team, but still from the office. The office is my social space, where the company culture is, where I go out for lunch with work friends etc.

I've worked at my company for a while, so luckily already know a good number of stakeholders around the business. I hate to think how bad it would be for new starters joining the company and only really being exposed to their direct team.

Meeting people at the coffee machine or at a lunch area may not seem important but it's what made me love my workplace.

The C level has completely changed three times in my time here, but our culture lives on in the people. If it wasn't for those connections and sense of belonging, I may no longer still be working here.

I don't want to be forced into going back to my 3hr daily commute, but I wouldn't mind easing back into the occasional office visit.
Does your circle of friends on FB actually go to every county, water board, school board, etc. meeting and take notes? Because that was the old role of the local paper, which could often get scoops from a reporter whose job it was to go to those.
If these are from out of state what is to prevent them from just saying no? I'd imagine there is some interstate process that they have to follow in order to make it valid where Microsoft is headquartered.
Hold on, I'm going to go patent this idea. :)
Email broken for 3 days an no rollback / plan B?
That's too bad. I was hoping for conjecture.
Microsoft appears to believe this (or maybe just MacBU) because I've met employees who tell me they're not allowed to read any public code including Stack Overflow answers.
NASA publishes free software catalog for public use
It's also very useful for personal projects, where you are the entire stack. Strangely, it's still difficult to get that buy in...
My best advice would be to find a friend who is doing well and learn from them. Chat and meet up often. Ask them about work and stuff. Personally I give out as much advice to my friends as possible and have helped them get started in software development careers.

Knowing what you can and should ask for is so important. Recently management suggested that it would be better if I had a formal certification. I then requested that the company pay for me to go to university. They accepted despite it not being an advertised perk. If I had not seen my parents do the same thing previously I would not have known this is even something you can ask for.
India emits less than half the CO2 that the US does, and almost an order of magnitude less per capita. The US has a long way to go toward getting its own climate policy in order before it should be telling India to make changes.
>They sound like colleagues. As distinct from other employees or friends.

I think the point being made is that this is totally okay.

There's an undertone in this greater thread that "people you work with aren't really your friend" and it implies that these "not-really-friends" aren't pleasant to be around. But that's not necessarily the case. For many people, being around "colleagues" and making small chit-chat is enjoyable, desirable, and helpful, even if they aren't (and never become) your "friend".
Wasn’t the Martian LV an Ares series vehicle? The good old Shuttle SRB with a capsule on top. Those are kind of cheap as they are.
I can see that.
My point is that there are many reasons for not wanting to work at a FAANG, even for someone like me who has worked in one and could work, I guess, in others. My reason is that I make enough money currently not to want to work there. I was working a standard 35-40 hours per week at a FAANG.
There are also many others in non-FAANG tech who make half my salary and work much more. And maybe I will be one of them at some point, there are no guarantees in life!
Last I checked Algeria has a bit of solar energy hitting it.
:)
1. This is called a patent pool. It's very common.

2. You can't sue a parent troll for patent infringement, since they don't have any technology business. They are only "companies" on paper.
I'm in kind of the opposite position, as I feel confused about why I keep seeing so much resistance to higher levels of abstraction here.

> It boggles my mind that people look at something like Kubernetes and decide "You know what? We need more layers. On top of this."

I'm not involved with this project at all, but yes, I look at the massive Kubernetes deployments I've worked with, and conclude that toil and various other kinds of problems could be reduced with higher-level abstractions for declaratively managing configuration for all of these clusters.

If you wanted to run workloads on 100k servers, how would you do it? Would you have a team manually configure each cluster individually, or would you consider that there are a lot of similarities between clusters, and you only want differences that are chosen intentionally, and look into some abstraction to help keep the complexity down?

If 100k isn't enough for you, is there any number of nodes at which you'd consider building some tools support for your work?

What about data center count and change rate? There are a lot of business models that benefit from running workloads closer to customers, so it's useful to have deployments in many datacenters and clouds across the world, and for this to grow over time. Do you really not see why some people are interested in being able to bring up a cluster in a new DC by updating a few configs rather than starting from nothing by hand with kubeadm init?

I apologize if I've misrepresented your position by misunderstanding something. I feel like I'm missing or misunderstanding something from your perspective, but I don't know what it is.

More generally, I think it's extremely normal for people to build higher levels of abstraction as things grow. It's usually worth considering abstraction or architectural changes in a system every time it grows by about 10x.

Some of the most painful platforms I've supported in my career have been those that didn't do this, and instead tried to grow through brute force. Something can be fine to do once, troublesome to do 10 times, and overwhelming to do 100 times.
Nuclear power is severely restricted and building a nuclear power plant in a country dealing with active terrorist movements is probably something to be avoided.

Solar is relatively inefficient, but it can't be used to build a dirty bomb or worse. With large patches of uninhabit{ed,able} desert, many African countries have more than enough space to build large solar farms if they can find a solution to the sand blowing onto the panels.
... what? Do you have a source here?

> The major correlates with high economic mobility Chetty identifies are racial segregation, income inequality, school quality, family structure and social capital.

https://www.huduser.gov/portal/pdredge/pdr_edge_featd_articl...
I think you could scare off a good number of these trolls by saying.

"I look forward to the discovery processes during this lawsuit as well as reviewing the prior art associated with this patent. I will be creating a blog to document this process for public consumption as soon as the lawsuit is filed."
I agree the UX is a big improvement. Just seems strange to call it a gift to the disadvantaged.
Sic semper tyrannis.

Didn’t even have the guts to be a tyrant. Just an evil toady.
> Correct me if I’m wrong, but is that even possible?

It's not possible because of comparative advantage - someone being better than you at literally everything isn't enough to stop you from having a job, because they have better things to do than replace you. Plus "being a human" is a task that people can be employed at.
Engineers should absolutely be writing unit tests and integration tests for their APIs. Personally I find that it brings a lot more integrity and a sense of ownership into the process when engineers are required to deliver tests.

I disagree with the problem's that you mention in this article:

Developers aren’t incentivized to prioritize QA testing

Developers are typically evaluated based on the quantity of software they ship, and how fast they ship it.

That's an organizational problem that is not universal and certainly won't be solved by a QA automation tool.

Developers’ job satisfaction goes down when they’re in charge of QA

Expanding upon one of the previous points:, we’ve seen that most developers just don’t enjoy doing QA.

This might be the case for manual testing but for automated testing the opposite is true. Delivering tests along with code increases integrity, makes debugging significantly easier, and helps clearly communicate the intention of each feature. This only works if there is collaboration between the developers and the product owner.

Clearly you have a viable product that works for many organizations, but it's certainly not a one-size-fits-all solution nor a best practice.
So what would you recommend as a wifi item? A lot of them seem to be crap, and don't you get issues with having +30 low frequency, low bandwidth wifi items added to your home network, along with the 30 other ones at your home already? How about remote exploits of those devices?

The fact that wifi 'can't handle a 100 small devices well' was sold to me as a reason to go z-wave 5 years ago.
I don't believe I said it does, those are your words.
I don't think you're quite understanding how the replay mechanism works. The original HTTP request fails because it can't DELETE or UPDATE something, so the entire request gets re-routed and then handled by the app again, from the beginning. So your SELECTs (as long as they're in the same HTTP request) will always get run against the writable leader.
Chocolate’s Transatlantic Journey from Exotic to Everyday
thats a dewpoint of 76F!!! dunno what its like a little more east but in the northwest that's unheard of.

Portland's dewpoint I think peaked around 65F.
I definitely like writing the story parts, and the actual replay header is about halfway down. So you're right about that.

But it really does result in globally distributed postgres.
Ocean thermal energy conversion plants [1] is another possible technology that could give us fine grained control over the weather. These types of technologies are more promising than technologies which only have a goal to fix climate change, because they propose something that would be useful to do independently of climate change.

The new nonprofit founded by Aubrey de Grey https://viento.ai/ works on this issues.

[1] https://en.wikipedia.org/wiki/Ocean_thermal_energy_conversio...
Hardware engineering, especially the type Apple does, is extremely hard to do when everyone is remote at their own homes. You can have multiple offices that work on different components, but at each of those locations there needs to be a physical office where the engineers can go to.

You can make the argument that software engineering won’t suffer as much with everyone being remote, but Apple probably doesn’t want to segment their engineers and give some more perks than others.

Also, for people like myself who can only afford a tiny, messy shared 1 bedroom apartment, having an office to go to is a blessing. Even with the 40 minute commute each way, I’m still more productive in the office than I am at home.
> Invalidating a patent costs them the time it takes to get a new one

The threat would only work if it were in respect of a large swathe of the troll’s portfolio. Agree it would be meaningless if done against a few of their patents, or if the patents were trivial to file for.
Well, looking at mars, solutions like "keep slamming it with ice comets till the weather improves" are on the table. On earth we'd have all the NIMBYs whining about impact craters spoiling the view or something.
It was written before gay rights was much of a thing, I think in the 70s. I'm fairly certain it's there as a normal law although.
I think you're referring to the part in the book where Ousterhout says he doesn't like to start with a test harness when writing a new abstraction or feature like some advocates of TDD would. I think that was some of the best advice in the book in my opinion.

Instead, Ousterhout recommends designing the interface for the abstraction you're building before you start writing a test harness for it, and I can't agree enough with that statement.

If you write a good interface, testing it will be easy.
If testing the interface isn't easy, then you have a bad interface.
(This is relative to the complexity of the code invovled, obviously)
This is the truth. Change doesn't happen until the decision-makers feel the pain of their decisions.
> federal law enforcement
>Most estimates are inherently given on a "if I am in a perfect working environment with no interruptions" basis and we don't even acknowledge _that_.

I had the experience of working at a company that had the practice of rigorously tracking engineer-hours. Through a time-card system. (this was for billing our clients). This way we always had a paper trail of how long we spent on a given task or project, and it was generally "against the rules" to bill hours you weren't directly working on that project.

This led to having an awareness of that imperfect working environment, and was a powerful enabler of making good estimates.

On the other hand: that documentation effort wasn't free either.
I remember when I toured a research nuclear reactor and I was talking with the nuclear phd student and I said something about an alpha particle and the protons and neutrons. And they were trying to say alpha particles aren't made up of protons and neutrons. Made me realize than that even an expert in the field might not know something that I would have thought was common knowledge.
Great man indeed. I just didn’t understand the comparison with Elon Musk.
I think that's because in the early decades Paul had the impression that the messiah was coming back any time now.
Who needs children.

If you read his letters in chronological order (not bible order) you can see the wind come out those sails. :)
And “ACME” is very likely already registered in any desired class for the particular good.

It also creates bigger questions about Amazon’s brand/trademark practices vis-a-vis forum selection where registration fees and criteria are minimal and rights are liberal.

Assuming it was successfully filed, actually returning the marketplace/reviews to OP would actually be more troubling…in other words Amazon would be willing to take the marketplace/reviews from a legitimate Trademark holder with an earlier filing date and give it to a legitimate Trademark holder with a later in time filing date from another jurisdiction.

Disclosure: I’m a lawyer and have actually represented a client that registered trademark A, sole the product on Amazon, then Amazon began selling a competing product with a similar (not identical spelling but pronounced the same) name they successfully trademarked B, ironically the USPTO rejected our clients trademark for C on the basis it was “to similar to B” whereas the USPTO never found B was similar to A. The difference between A and C being addition of a logo to the word mark.
Do the people that work there know it's a troll company I wonder? Maybe like working at an MLM company, you've rationalized it in your own mind as protecting inventors and creative people!
https://www.linkedin.com/company/ip-edge-llc
Do these theoretical AIs have desires? Then they're customers, so you're not unemployed.

If not, do they require inputs to run? If so then you can provide them.

If not, then you apparently don't need a job since they can provide everything for you.
A highly efficient multi-stage solar still has been developed at MIT [1].

An alternative to desalination is capturing humidity from the air, e.g. by isothermal membrane-based air dehumidification [2] or passively using condensation [3].

I’m involved in building a fund to invest in startups in this and other areas related to biosphere resilience, and would love to get in touch with people taking such technology to the market.

My guess is we will be needing adaptive measures sooner than most people expect.

[1] https://m.youtube.com/watch?v=iYodKQP72mg

[2] https://www.osti.gov/pages/biblio/1476418

[3] https://newatlas.com/science/passive-drinking-water-harveste...
You joke, but have you looked at K8s VirtualCluster? Separate control planes for each tenant within a K8s cluster.

https://github.com/kubernetes-sigs/cluster-api-provider-nest...
> but you need to grasp the concept and have an easy task to learn to program on.

"We have to reinvent the wheel every once in a while, not because we need a lot of wheels; but because we need a lot of inventors." -- Bruce Joyce
This is awesome! Would it be possible to make this for other repos as well, such as Go language, or Kubernetes? Do you have a plan to extract a reusable foundation out of this project?
https://lotnet.com/
This is really good advice.
I suspect "the 0.01% own and run all production by themselves" isn't possible in the real world. My evidence is that this is the plot of Atlas Shrugged.

If they're not trading with the rest of the world, it doesn't mean they're the only ones with an economy. It means there's two different ones. And the one with the 99.9% is probably better, larger ones usually are.
The battle of open-source licenses
First off congratulations!

I was also confused as to what Meltano actually is or does, but everyone here seems to be so excited and genuinely happy for you and that made me super curious. It must have taken me several minutes of roaming around the website and docs before I finally figured it out though!

The main problem, I believe, is that there is too much copy that describes how the product will make its users feel etc. and far too little that tells us about its technical capabilities and its use cases. That notwithstanding, the copy is beautifully written and it has a very nice and smooth flow.

Being a developer myself and have seen/operated similar systems before made it not too bad to connect the dots. But that could just as well be exactly what you expect from your target audience!
Ahh the mountains of praise for Google Wave, I remember it well
How are POST requests replayed into different regions? Does your edge proxy hold the whole POST requests (body and all?) just in case it needs to be replayed?
pretty sure the author is describing how the "runtime reconfiguration" described in the next two sentences of the lawsuit after the one you quoted is a memory allocator, not confused and thinking "dynamic RAM" means "dynamically allocated memory"
They will have to sell if the Bitcoin price goes down enough that their measly revenue from their obscure enterprise software can't cover the loss from their Bitcoin investment.

He can keep holding, but it will lower the morale of the employees as well as himself. Unless you think Microstrategy has completely become a hedge fund, they have products to build and they will even lose what's left of their customers if things go bad. You really think the guy can keep holding when he lost hundreds of millions of dollars through BTC? (At the moment he's still in the positive even after the crash, but I'm talking about when it goes down further) Also he can and likely will get into trouble with the SEC when things get bad.

This is not the first time Saylor did stuff like this. https://www.computerworld.com/article/2589923/update--micros...
That's gotta be a very short term thing though hasn't it? Honestly Amazon is two, maybe three, knockoffs away from me never using them again (currently: 0). I can't be arsed with faff.. that's why I use Amazon.

It'd be daft for them to not be curbing this!
I'm very sorry I gave you that impression.

When Jamie Dimon discussed the warm relationship between Obama officials and tech in a public speech at Stanford, I assumed it was (1) common knowledge and (2) socially acceptable to discuss in public.

I think the current administration has made excellent personnel choices in the regulatory agencies. I am hopeful for the future.

But I don't think I "called out" anyone. I understand that expression to mean "seeking to direct reflexive mob anger toward a specific individual". It's the practice that's troubling, not the people.

I actually believe that most of the people engaged in this practice (revolving door) have impeccable moral character.
OP using the term "butthurt" shows a certain dismissiveness, no?
> 1. Use immutability by default, even in languages that make that harder than it should be

What I've come to realize is that whenever people talk about wanting immutability, they really want value semantics. Value semantics can be achieved without immutability - the best example is Swift's structs. They can be both mutable or immutable, but they can never be shared, i.e. there can never be more than one reference to a single struct value. This means that modifying the value has no effect on other references, because there can be no other references.

This makes whether or not the value is immutable irrelevant, or at least not necessary. You get the same benefits - you can reason about your code locally and not worry about your changes modifying unknown parts of the program. Local reasoning is the end goal, and value semantics is the mechanism of getting to that goal. Immutability is only one way of getting value semantics.
> > Patent trolls are Americans that are destroying American manufacturing and small business

> Why should the identity of their victims matter? Also, are they?

Because this is a fairly American problem with the American patent system in particular and the ultimate target of pieces like this are American lawmakers and voters.

It's not that only American victims matter, it's that this problem is fairly American in nature and scope.
This line appears to suggest otherwise.

> Dynamic ram? Can I poke fun at them for not knowing what RAM is? Yes I can.

He's trying to nitpick about the term "dynamic" in this context, which he has misunderstood to mean "dynamic allocation" (i.e. the alternative to "static allocation"). The phrase "static or dynamic RAM" is basically never used to refer to memory allocation, it refers to the physical construction of the memory. This is especially true if the paragraph is next to a block diagram that includes an ALU... They are five levels removed from any sort of allocator.

The rest of the paragraph doesn't describe a memory allocator, it's describing runtime reconfiguration of a circuit, which you can do (and often do do) using a statically allocated configuration block or even a hard-wired dedicated memory. Again, nothing to do with malloc.

Whether a configuration memory is SRAM or DRAM based is immaterial, but patent language likes to make a point of enumerating the possibilities.
The ABCs of DAOs