skysight-inc/HackerNews huggingface dataset:
Shouldn't the workers in the rich countries be terrified of remote work? You essentially open up against competition from much cheaper places and you might end up moving there to be able to match the margins.

It's not that I'm against it - IMHO freedom of movement should be absolute and people should be getting the based jobs on merits and not on nationality, it's just that all this visa stuff that makes people drown in boats, stay in detention centres, leave the EU to keep the Poles out of the job market etc. exist primarily to protect local working markets. IMHO a people doing the same job in SF and Bangalore must be compensated the same but the fact that they aren't is exactly why it's much better to live in USA. That's also why you have H-2B visa quota.

I'm still puzzled about this, don't you think that this could have the same effect on your industry as the manufacturing moving to China? Especially for coders, don't you think that people in poor countries can code just fine? Technology is not only making the distance a non issue - recent developments are also removing the language barriers.

The money that even the junior US tech workers are making is at life changing level for most of the world. This will be tapped.
What do you mean the scale is different
That’s the thing - you need to consciously do things like that. Some don’t have presence of mind to do that and effectively waste everybody’s time.
> SQL may be a language for all those things, but unfortunately it's horribly bad at it.

Any piece of software used incorrectly will seem "horribly bad".

> Wilfully obtuse syntax

This is an opinion.

> Incredibly poor compositionality.

Another opinion.

> No testability worth the name

I would argue that "try it, observe side effects and rollback" as a language feature is more testable than many/most programming languages.

> The deployment model is a half-baked pile of perl scripts, and that's if you're lucky.

>> Any piece of software used incorrectly will seem "horribly bad".

I appreciate that you hate it. I don't even think you should care or learn it if you don't want to. But I think positioning things you don't understand or _want to use_ as "horrible" or "bad" or whatever is acting in bad faith. You're allowed to say that you don't like something and don't want to learn how to use it, without suggesting it's the tool's fault.

> So yeah, I use SQL like https://xkcd.com/783/ . I'm sure you have a bunch of cool data analysis tools in there, but please just shut up, give me the contents of my table, and let me process it in a real programming language where I have map/reduce/filter as regular composable functions that I can test and reuse, with a syntax that doesn't make my eyes bleed.

This comment directly demonstrates "I don't understand, I don't want to, just let me do whatever I want however I want", which is fine, but again, not the tool's fault you don't want to use it.

Quoting again because it's also relevant to this last comment:

>> Any piece of software used incorrectly will seem "horribly bad".
Hot take: ORM is dynamic runtime code gen.

Sometimes, you need dynamic code gen and you dont want to manually do it.

…but mostly, it’s a bad idea. You can’t easily debug the generated code, you can’t easily tweak the behaviour, and writing the templates for it is hard.

Mostly you can replace it with a hand written or pre generated (“compiles to sql”) solution… but I’d like to point out you can’t always and if you do need dynamic SQL please, use an ORM, don’t template your own half baked solution.
An extra NIC is fine if you've got slots, but you can also do an if_bridge in the main host, add the real nic and half of an if_epair; then move the other half to the vnet jail.

Potentially a non-vnet jail with the ipv4/ipv6 options set may also be an option. I used to use jails with those settings to squeeze multiple environments into a single host at Yahoo.
When I joined my current employer the biggest drawback was that unlike my previous job they did not allow remote work. Managers were against it because they were paranoid about people slacking off.

The pandemic hit, we transitioned to remote work, I was happy. Everyone quickly adapted and learned how to efficiently work from home. About two years later, two things happened:

1. Surveys and postmortems showed that remote work lead to increased employee satisfaction and productivity at our company.

2. Company leadership started talking about a mandated return to office.

People of course challenged this decision, pointing to the data, and no real explanation was given. Those who wanted to returned to office, but the mandated return was indefinitely postponed and eventually silently dropped as the manager primarily pushing for a return left the company.
I've found that if I get a specialist referral, the specialist's office will call me initially to get me into their system. It's true that subsequent appointment reminders will be robocalls.
Of course it's bullshit. I would say 95% of the JPQL queries do the job.
I am using IotaWatts to do monitoring of every circuit in my house, and it is a pretty great setup. I have a reasonable large setup given I have 9 panels to monitor with >120 individual circuits. I also have it monitoring my 20kw Solar system as well as 42kwh of batteries.

https://community.iotawatt.com/t/sorta-larger-than-average-i...

I have all of the data going into influx, with grafana for display.

During the build of my house I planned for this by adding additional space below the panels: https://www.garagejournal.com/forum/threads/jeffs-mountain-s...

However that was more of a nice to have, not something you have to do.

On the solar side, if you want per panel measurements that is something you can really only do with micro-inverters. I'm using Enphase 7A micro-inverters on each panel, so I also get direct data from enphase/enlighten about power production from each panel.
LA is not Manhattan but it’s not a generic sunbelt city either. It’s comprised of dozens of neighborhoods and cities many of which are dense by any American standard (10000+ people/sq mi). A number of neighborhoods that were previously oriented around the yellow and red cars still have walkable “main streets” (albeit each of these main streets are individually difficult to reach without a car).

But that’s kind of beside the point. What I’m pushing back on is the notion that you can live anywhere in the US and it’s just as good as anywhere else so you might as well live wherever it’s cheapest.

It’s not about suburbs per se since Orange County is as suburban as it gets and also checks some of the boxes I mentioned (although I’d argue not as many as LA). It is also extremely expensive.

I don’t care for the “soul” argument since it’s vague. I just specified something that is personally important to me and justifies living in an very high COL city.
Weird to list the companies and then order them alphabetically and don’t reveal any revenue numbers
ORM doesn't seem like an anti-pattern in my experience; sometimes they are very useful for certain applications, other times they aren't. This applies to all tools.
Wait, 4 days ago we were on the cusp of a golden age of medicine: https://news.ycombinator.com/item?id=36458515

I must have blinked and missed it!
If you scroll up this thread you will see where the discussion began.

Edit: For example, you’ll see where I asked my initial question here

https://news.ycombinator.com/item?id=36501689
Some odd Python "class" syntax in there.

## Python class called Car
def Car(make, model, year):
"""This function creates a new car object"""
car = {"make": make, "model": model, "year": year}
return car
I don't use. I don't care about ads, I'm more concerned about 3'rd party requests so I block them via uMatrix extension.
Yes I can’t imagine going back to doing big CRUD apps without AR, readability and maintenance would take a hit. The catch is you need a prior good knowledge of SQL to use it correctly. Problems happen when people don’t learn SQL and then don’t understand the queries AR is generating and the limits.
Password wouldn't recognize chess moves on row 7 or 8, and the best move was on row 7!
I used to go to this machine a lot in high school, and certainly drove past it a lot too; it was located pretty centrally in the Capitol Hill neighborhood of Seattle.

More than 20 years later I sent a close up photo to some old friends who immediately clocked it as “that” vending machine.

Simple curiosities like these make me happy.
> Not a coder, working as admin

The working environment which is conducive to a successful developer vs a successful admin are, most likely (in my experience), two completely different environments.
Agreed with this - the Home Depot stuff I’ve looked at is often warped or cracked. The prices they ask for it make me put my DIY projects off till next summer.
Design is about communication. Watch out for cases where what you want to communicate as a designer is not the same as what you should communicate.

I believe almost every “Saving…” indicator is an instance of that discrepancy.

They were appropriate back when on-the-fly saving was a fresh UX revolution, but today they’re nothing but self serving: us weathered designers, who grew up when the floppy disk icon actually represented the real thing, bragging about how cool our app is—it saves your draft on the fly! No need to press buttons, can you imagine?

Nowadays, as devices are constantly connected, latency is low, and constant saving has become the dominant and intuitive behavior, what the user needs to know is not that stuff’s constantly being saved; what the user needs to know is the extraordinary situation where you fail to save it.

This, if I may be so bold, is what you should be communicating—and if you ask me how, I might suggest a single, completely unchanging line of text informing the user that their draft is being constantly saved (though ask yourself if even that is required; it might not be if you are dealing with digital natives) and an obvious, flow-interrupting error state when that doesn’t work as intended.
Igor Markov, along with Sat Chatterjee, seem to be pursuing a bizarre vendetta (after Sat failed to take over their project) against the lead authors of the chip placement work, not some sort of intellectually honest critique.

This was covered previously in the press and on social media, with statements from a variety of prominent researchers (e.g.
[1][2][3]).

The code is even available for the Nature paper's method, along with an FAQ: https://github.com/google-research/circuit_training#FAQ

[1] https://twitter.com/ZoubinGhahrama1/status/15122035096467415...

[2] https://twitter.com/JacobSteinhardt/status/15215993404137881...

[3] https://twitter.com/sguada/status/1521587406385807361
This is the old notion of what an FPGA is, and if you notice, these new devices aren't even called FPGA's anymore! They're called 'adaptive SoC's'. Only a small portion of the device is FPGA fabric. But still, even previous gen FPGA's wouldn't be shipped with defects.
> The causes of shortages are well established. Everyone wants to pay less, and the middlemen who procure and distribute generics keep driving down wholesale prices. The average net price of generic drugs fell by more than half between 2016 and 2022, according to research by Anthony Sardella, a business professor at Washington University in St. Louis.

> As generics manufacturers compete to win sales contracts with the big negotiators of such purchases, such as Vizient and Premier, their profits sink. Some are going out of business.

I'm confused, how is it that the prices are being driven so low that the supply dries up despite continued demand?
what's there to remember? NHibernate you basically use Linq, so if you remember Linq you remember NHbernate. The only extra bits are the setup and mappers, which are sort of trivial. The pain points come around because NHhibernate decides to lazy load everything or ends up doing crazy joins. But overall I found NHibernate not too bad, it certainly was fast doing a lot of basic CRUD type stuff.

However, these days I use Dapper.NET and SQL. Dapper gives a nice mapper for parameterized queries and maps results to types. I think it's a nice middle ground.
Bernie Sanders, Elon Musk and White House seeking my help says ‘godfather of AI’
Not for YC at least. They weren't nearly as big on crypto.

To be fair to AI, I know people who use it daily and it provides value to them. It's a bubble, but there's something underneath.

I've never heard of crypto providing any value outside of speculative gambling.
Being old enough to experience how it worked before ORM, ORM is godsend. Maintenance just used to sux, massively, comparatively.
As with anything, there are situations where it works well and where it doesn't, and the tech can be easily abused or misused. ORMs (in e.g. dotnet Entity Framework), particularly when working database-first, can be a great asset.

If you are working in DBs with hundreds of tables and all setup with proper foreign key relationships, an ORM can help navigate a complex schema and provide compile time sense checking when things change. Embedded SQL is a double edged swords with perceived performance benefits but with very difficult to maintain "hard coded" verbose SQL particularly for joins. I'm talking about when there are hundreds of tables, not when you have 5-10 tables.

I've no ambition to convince anyone one way or the other, but don't believe everything your read on the internet about best practices especially since people may be talking about something quite different to what you're looking at. Some people will be pretty shocking developers regardless of which tech is being used.
It doesn't seem to be 2x faster on AMD (but mandatory "bait for wenchmarks).

AMD ran a YouTube ad that claims it's a 30% performance improvement on RX 7000 series: https://youtube.com/shorts/BKzty6YdRNM

Of course it depends on the exact scenario, but in games it's already known AMD ray tracing performance is quite bad compared to Nvidia and Intel, so it's not surprising they're also slow in Blender.
> Whilst it looks like a pizza, this image from a Pompeian painting from 2000 years ago obviously can't be, since some of the most characteristic ingredients are missing, namely tomatoes and mozzarella.

There are more types of pizza than the now globally common tomatoes and mozzarella pizza. Heck olive oil and garlic pizza is thing, unless there is more specifics regarding the origins of pizza available it's possible it is indeed just a pizza.
As an SRE, I used to install one tool for every data format until I came across clickhouse-local. Now I use it for everything.

- It works with every data format which I come across in my daily job. It support data formats like Protobuf, Avro, Cap'n Proto which regular tools don't support. Funny thing, it can even read mysql dumps.

- I can read the data stored in local or remote location like http, s3, gcs, azure and whatever location I can think of.

- I can SQL queries on the raw data and improve my SQL skills on daily basis.
Companies that are not WFH flexible will be less competitive. They will be less competitive in the job market, and operational costs (office space, middle management, wasted BS meetings etc.) will be higher compared with WFH companies.
waqi.info offers API access[1] as well.

[1] https://aqicn.org/api/
React Router? React Router Dom? Redux? Rematch? Jotai? MobX? Hooks? Classes? Create react app? Not create react app? Next? Gatsby? Preact?
Virtually the entire VFX industry has shifted to remote. Let that sync in.

The most hardware/GPU intensive industry of creatives dealing with ungodly complex technical pipelines, terabytes of 32bit EXR frames of rendered data, Houdini fluid simulations, compositing, color grading, the whole works... is almost entirely distributed now.

They've done it. Everyone can do it. And are doing it.
That’s why you buy NICs with hardware timestamp support and enable PTP.
You're right there are obviously economic incentives driving this but I think (in general) the things that annoy us grumpy nerds also annoy everyone else - we just might be more conscious about what specifically is going on. Over the years I have helped out many non-tech savvy relatives/colleagues/friends and things like changing program defaults, changing home pages, browser desktop (or mobile push) notifications, too frequent business newsletters, etc have been a common source of rage and stress - made worse because the person doesn't always know how to stop the problem. In fact, we're shielded from some issues - imagine how bad it is for users without adblockers.

But you're right - there's no easy way to deliver negative feedback for these negative practices - so they will presumably continue where commercially it's profitable (and not prohibited). I can hardly boycott every company/product which displayed arrogant behaviour - I'd have to live a hunter gatherer lifestyle by the end of the year.
It is kinda sad that one has to go through all the database technologies just in order to read a csv file nowadays.
During the last 10 years or so I’ve gradually been using less and less Windows. Used to do everything on Windows - now at home, it’s only for gaming and I’ve been dabbling with proton to hop off the sinking ship. Due to some proprietary windows tied software, I have to use dualboot at work. All development work is and has been done on Linux for a good while.

Don’t want to support WSL - due Microsoft being Microsoft, mediocrity and smoke and mirrors to leech on your telemetry. Am waiting anxiously for the moment to cut off the final ties with Microsoft OS.
The SPAN panels are interesting, and I considered them and a few others like them, but it is hard to use them without knowing if they will be around in 10 years. The standard panels from SquareD, etc are such a known quantity especially for parts availability.

You can get the monitoring part of the equation with CTs at least, and that is a start.
Exposed beams with detailing look great, not to mention the milage you can get using hybrid techniques such as steel I-beams masked with long thin jarrah inserts.

Natural edged shelves, island tops, tables.

South-West W.Australia has a lot of old craft skills kicking about - I was in the midst of a crowd doing glass blowing, cabinet making, solid and ply shell drums when I was writing pre-Google Earth not exactly KeyHole geo spatial processing and display software and we'd often going out to retrieve all manner of wood and rock that was toppled or exposed by storms.

It's not just jarrah stashed away, there's also wandoo, granite slabs, numerous burls extracted .. and a lot put back in terms of replanting, cool burns, 'artifical' hollows, culling ferals, etc.
this doesn't magically fix the problem

node clocks are unreliable by definition, it's a fundamental invariant of distributed systems
I feel like I read about Airbnb's collapse every other month. Anyone showing random data on twitter and expecting a brand- which is literally a verb and doesn't even require paid marketing - to collapse 40% is laughable. I must also point out that a 40% drop is not reflected in the stock price (which is actually up quite a bit) or in the forward guidance. It is also interesting, that supposedly data driven people in Hacker News would fall for some random tweet.
You can't read SAME csv in a parallel manner but you can still read two different csvs in two separate threads? I think that's what they meant by "parallel csv".
It’s been so long I sometimes forget why I left. Thanks for the reminder.
False. I've developed enormous systems fully using stored procs for data layer and it's absolutely not the "best way to do the data layer". Next you'll be saying triggers are a good idea.

Yes they can be fast, and they're controlled by the DBA, that's why you'd choose them. Injection is not an issue in modern data access layers, that's a 1999 problem.
VisiData is amazing. It's one of the coolest open source projects I've seen in years. I use it extensively in my research.
This sort of shallow minded statement always boils down to “but we should still censor the stuff I don’t like and of course I assume everyone agrees with me”

Sorry but it’s obvious you’ve never worked on this issue. It’s not easy.
Any chance you could translate that joke into HN-speak?
Unfortunately, this sentiment can rarely be expressed before someone has come full-circle. An apprentice cannot have that insight. A journeyman is too busy DRYing things up and peppering their code with patterns. It's only once you've felt the pains inflicted upon you by all those "one true ways", when you've survive the betrayals, only then you can finally accept that there are, in fact, no solutions, only trade-offs. Congratulations, you've become a veteran.

Despite all the good souls trying to turn programming into a discipline with sharp rules and well defined constraints, it remains a craft. Part prickly, part gooey. As far as I can tell, if it has tenets they sum up to four, in that order: code has to be correct, bug-free, reasonably efficient (i.e. enough for the problem at hand), and maintainable. The last two bits lie in overlapping shades of grey. You either learn to be comfortable with it or you will yourself to make black and white observations, which you turn into rules and patterns (or anti-patterns, as the case may be). Then you write an article or a book about them.

And on the wheel goes...
Every non-trivial project that uses an ORM will, at one point, fetch the whole database.

Either by someone accidentally creating mappings that do it without noticing or someone not understanding that there's a whole-ass database in there and they just fetch everything local and filter with a for-loop.
Python's pandas library has ability to seamlessly work with csv by importing/exporting them as data frames.
> At this point remote work is nothing new[...]

I couldn't agree more. In fact, historically, the norm has been for the work to come to where people lived with their families, rather than for people to leave their family homes to "go to work". This was at a time when the prevalent type of work was farming and craftsmanship in relation to goods that were easily transported. A craftsman's workshop was usually in the same building as their family home in towns and cities, and rural areas operated a "putting out system" [1] where travelling tradespeople brought supplies and collected finished wares.

With industrialization, the factory became a thing, and it somehow got into our heads that factories are the success model that everything else should be modeled after. Offices that don't do factory work started looking like factories. Schools started looking like factories. Public administration started looking like factories. Everything became a factory. ...this trend is hostile to human nature and relatively recent when looking at it on historical timescales.

Recent advances in telecommunications have made what little advantage there was to factory-like offices obsolete, and it's time to "return to normal". And by that I mean remote work, because remote work is "historical normal".

[1] https://en.wikipedia.org/wiki/Putting-out_system
These boards are amazing for the price. About 1/3 as expensive as a Zedboard and way more capable. It's confusing, but real. I use both for work & personal projects.
Try staying in a hotel with two kids
> Decisions that were made at a whim's notice, like implicitly converting numbers to strings sometimes, and sometimes implicitly converting strings to numbers!

I see this as a problem that's horribly inflated by those who don't use JS on a daily basis.

Practitioners of the language largely don't care, because in actual code you rarely see cases where it would matter.

Now that we have template strings it's even less relevant.
i will never be surprised by the transcendence of pizza
If you mean static methods inside classes, I don’t think those are any different than a namespace. They should be thought as such (e.g. java’s Math::sin, not sure how it’s done in C#)
Enjoy https://jdebp.uk/Softwares/nosh/guide/per-user-dbus-demand-s... and https://jdebp.uk/Softwares/nosh/guide/commands/dbus-daemon-l... .