skysight-inc/HackerNews huggingface dataset:
I've been a reviewer on PR for a couple of months now and it's been amazing. I've gotten to help dozens, maybe hundreds of developers improved their code, fix security, readability, testing and lots of other issues. Sometimes the PR is short and the review is short but sometimes it's much more involved and I've had the opportunity to really explain things and educate people in a way that no lint checker could. I'm able to apply the wealth of my experience and knowledge with specific guidance based on things I've learned from building software for 22 years. I can't think of another way that a company could gain access to that kind of guidance for only $699 a month.

I can go into detail explaining how to safely and reliably structure something and the feedback I get from the developers is positive and appreciative. I also collaborate with other reviewers about things we're seeing and I've learned a ton in the process because the other reviewers they've all got such a depth of experience and knowledge in different areas.

I don't do reviews full time, I have a day job, but I've been earning about $1000 a week doing it just some nights and weekends and that has been really great too.

Overall, I think PullRequest is an enormously positive thing for its customers and the reviewers. We're not trying to replace people's existing review processes if they have them. Our goal is just to add to our customers' capabilities and I think we're going very well at that.
How does GDPR allow a foreign entity to punish or fine a company based entirely in the USA? I am genuinely curious, I have wondered this for ages. Every resource I have looked at says that as a US business I need to comply with GDPR, and that I can face fines if I don't. But I have never seen the mechanisms in which those fines can be enforced. Is the US government enforcing those fines?
IMHO, the "centralized team" + "decentralized liasons" model isn't explicitly used nearly as often as it should be.

It usually happens in practice ("Sarah knows someone in security"), but there's no reason "devops liason" can't be an explicit 2nd+ hat for someone on a team to wear.

Centralized teams are necessary for budgetary reasons: one person on every team asking for a devops product will never make a coherent case to management for why it's needed, but a team will.

But having been on both sides of the equation, the central-decentralized relationship usually breaks down because there's always a new face on the right side of that equation, and that requires reteaching / recoordinating all the basics. More consistency on the user side (a hat) helps significantly.

And ultimately, it's a trust problem: do I (central person) trust this person who's asking me for something? If they're new to me... probably not very much. If I've been working with them for awhile... probably a lot more.
If I may engage you in discussion, friend...

> I can't understand how someone open minded enough to be cool with Perl and it's [sic] strangeness, would be upset by something as trivial as whitespace.

Thank you for the compliment of open-mindedness. Every language is strange to some degree until one becomes proficient. Notice your own grammatical error above. English too is strange until one masters it. But we won't blame people for making mistakes because bad code can be written in any language.

Whitespace is not trivial in Python. It has been promoted to logical operator.

Now everything that I type gets broken unless I use an editor to protect me. Oh, you might say, any modern editor should be capable! This leads to IDE dependence like Eclipse and PyCharm (both written in... Java).

There is none of this nonsense with Perl. I work on systems of every size with the simplest, most robust set of tools. I don't need a complex baseline just to write my code.

> It obviously isn't that much of a problem as it's one of the most popular languages ever and used [...] from children to Google's chief scientist [..] critical backbone of many companies [..] defacto language to build an API for.

C, C++, Java, Javascript and Bash are also very popular languages. The first three are more important that Python. And they are all unlike Python. Google has formally sponsored Python for some time, which certainly helps Python. Google has also been developing Go, which is itself a better language than Python in many ways. And Go solves the problem of formatting for readability in a sane way (go fmt).

An API can be expressed in many ways.

> It's fine to find it aesthetically displeasing

The above criticisms are objective.

However, I don't like how many lines idiomatic Python requires because of the whitespace promotion. At its best, Python allows clear, compact expressions such as lambdas.

At worst, Python is needlessly puffed with emptiness. Perl is as compact as the coder wishes it to be. It is easy to run perltidy and colourise the output for a formatted view if one prefers.
Once all cars are self-driving, I doubt they will exceed the speed limit by much. But perhaps speed limits will increase in some places.
I have a bit of a knee-jerk reaction every time I hear web3, and immediately picture somewhat interesting tech with not that many practical applications.

I'm possibly lacking vision, so I'm wondering if anyone could share interesting examples of that (old) new wave of technology?
Hmm, why would anyone even bother pulling out said pitchforks?

In my eyes, Go is a pretty reasonable choice: the language is decent, simple enough to be learnt in a relatively short amount of time, is reasonably readable and doesn't force you to work in a really low level of abstraction.

The runtime is also pretty good and the static executables that can be generated are a major boon in my eyes! None of the pain of Python's packaging challenges and performance that's generally pretty good when compared to many of the alternatives.

Sure, it's not as established like Java or .NET are, especially in the enterprise space, but nonetheless it is very capable for everything from utilities and small tools to web apps.

Edit:

> As Rails has waned in popularity, has any other tech stack taken that crown?

Actually, after re-reading the original post, i'm not sure what the question is, exactly. In my eyes, the languages that are fun are whatever allows me to solve problems and see results (which is where a lot of satisfaction lies for me) relatively quickly: so anything from aforementioned Ruby, PHP (with select frameworks), Java (with select frameworks), .NET (Core or newer), Python, Node and so on are still fun in my eyes.

Was OP perhaps looking for languages that feel more "fresh" and are more hyped, while still having vibrant communities around them?
XNA was the most fun environment I've worked in. No web bullshit, no heavy-weight game engine editor.
If you haven't already, you should check out the C projects from Justine Tunny. Specifically redbean, cosmopolitan libc and ape. https://justine.lol/

Whether you should use them professionally is questionably. But for me they made writing C fun again.
Ask HN: Software Engineers and the Gig Economy
Hi HN,

I am a senior software engineer and I am starting to work as a freelancer.

In between projects, I'd like to find short tasks (up to a few weeks) that would provide me a decent additional income (min. hourly rate > €60/$70).

I know about platforms like Upwork for Fiverr, but the rates on these platforms are significantly lower.

Is there any alternative for on-call developers? My expertise is mostly in Python, C++, Haskell and Scala.

Thanks
Not personally excited for this, but I think the next big thing will be the internet and computers becoming "hyper-transactional" through crypto. I believe this is what companies like Facebook are really pushing toward when they talk about Web 3.0 and the metaverse. It will still, for the most part, be the same internet accessed through phones and computers, but videogame-style micro-transactions powered by crypto will become part of most websites to access content. Since every site having micro-transactions would probably piss off a lot of the general population, I think there will also be an explosion of new ways to earn very small amounts of crypto online, by doing mechanical turk style tasks, playing a new game, creating a bit of content for someone, etc. Average consumers will earn these small amounts of crypto, then immediately spend them on the content they want.
> Screenshots work for your team because you set up and documented a process for managing them, and then taught your auditors about it.

Not really. We had no process before talking to the auditors. We told them that we didn't want to require employees to install the Vanta agent (for reasons mentioned) and asked them what they recommended. They said that screenshots would be fine. On a lot of these SOC2 things, I think people should just talk to their auditors early in the process and get a sense of what they are looking for and care about. There are some standards, but all of them are going to have a slightly different focus and the ones we've worked with have all been pretty reasonable about understanding the particulars of our company and what exceptions make sense for us.

> For what it's worth: a nit I like to pick with Vanta is that it sets a very ambitious bar for what a company should be doing with respect to IT security, where SOC2 does no such thing. I worry that things like Vanta lead teams into doing all sorts of stuff that might not be a fit, and certainly isn't required to pass a Big 4 SOC2 audit. What was your experience there?

I can't say it's really been a problem for us. Vanta and our auditors have both been pretty clear that it's not 100% necessary to have all tests passing in Vanta in order to get our SOC2 (again, it's helpful to just talk to your auditors). We run entirely on the Cloud (no physical offices or data centers) and honestly, some minimal GCP/AWS best practices and modern deployment approaches (protected branches, code reviews, standardized CI/CD) means that you're already passing about 90% of Vanta's tests on those things. We had to do a few silly things like change our resource labelling conventions to match Vanta's but otherwise nothing felt terribly burdensome or like security overkill.
Well I agree marketing is effective. But what's the argument for housing as a human right? You say "It doesn't really matter if housing as a human right doesn't fit some narrow implied definitions of 18th-century philosophers or statesmen." but that doesn't argue why it should be a human right nowadays. Lot's of philosophers and statesmen of today wouldn't agree it is a human right.
In a world where car ownership is limited, I can imagine that the car interiors would be changed drastically. Something like a subway car with hard plastic seats and easily sanitized surfaces.
a. Some discussions become the target of trolling and it's necessary to lock threads, unfortunately it happens sometimes. If somebody has made a rude comment then you may want to report that as a code of conduct violation. The developers are volunteers and don't have infinite time to handle all the work that's thrown at them. The disagreement with Pop!_OS was disappointing but I don't know who else you can blame for that, if Pop!_OS wants to go their own way then that is completely their decision. They aren't forced to contribute upstream and I'd say that's good for them and their goals.

b. There isn't really any funding to pay to fix those issues. They're being fixed by volunteers, so progress is slow.

c. I have no idea what this means, extensions are still there.

d. There are issues with Flatpak but all the other options are worse and are more unstable. Before Flatpak, there was just no way for upstream developers to make an "official" packaging for apps. The theming interfaces haven't really changed because those didn't really exist, those were a hack for the entirety of GNOME 3. Having one person implement a design and then gather feedback on it from the community is how open source works. If the community wants it then they'll use it, if they don't then they'll use something else. I'm confused how else you'd expect it to go. Talk is cheap, putting working prototypes in front of the community and then gathering feedback from there is what gets things done.

I also don't really understand why you're saying this makes them the bad guys or comes at the expense of the rest of the community. Like, none of this affects KDE. KDE has their own middleware libraries and makes their own changes. They don't depend on any GNOME libraries. Even XFCE that depends on some libraries like GTK doesn't really have to deal with any of this. GNOME's issues with extensions don't affect them at all because they don't use the GNOME shell, they can package their apps with whatever they want and they don't have to use Flatpak, they probably won't use libadwaita or if they do they'll heavily modify it, etc.
Do you actually prefer the subscription hell we are in now with companies like Adobe deciding we can no longer actually own any software and have to continuously rent it?

Google actually seems like they will be first to full self driving. My biggest fear is that they continue to have zero interest in being an actual car company and keep all their Waymo tech locked behind their taxis and Lyfts are replaced by Waymos with no reduction in price, just a loss job for the person who would normally drive the Lyft. Other companies follow suit and the self driving car dream is ruined to make C suite executives richer.
So you’re saying if we really want out of the service get your account suspended instead of just never logging in again?
> So when we get a new interaction mechanism, we write a new connector. Done.

Interesting idea... but I'm struggling to get the full picture here... (I might be way-off here, but):

Is this about "formalizing" connectors? Such that, once a connector technology comes along (RPC, REST, Web Sockets, GraphQL, who knows what next), such connectors could be implemented on either side of the boundary layers and then "selected" via some architectural language? I think the semantics of each "connector" demands different design constraints on either side of the equation.

An overly simplified example: Java logging "appenders" allow dispatching log messages to different targets (stdout, filesystem, database, etc.) But, STDOUT doesn't "fill up", while file systems/databases do. DB's support querying, while STDOUT does not. DB's do get overwhelmed; should processing halt until such "overwhelmed" situations get resolved? Databases (should) include security; STDOUT does not. Etc.

If there were different "types" of connectors defined, each with different behaviors, and those could be easily chosen, then maybe. But even the "types" would be solution-dependent. Retry rules, idempotency, serialization rules, compensating transaction support, etc. These topics (to me) are far more important than simply creating new connectors.
I worked med-surg for a number of years, and every so often we’d get older adults admitted to the floor for peripheral vascular disease. Same thing happens: toes get dusky, then necrotic. The treatment is painting the toes with Betadine and wrapping with gauze. I never considered that this might be part of regeneration that doesn’t come to completion because of chronically poor blood flow.

There is more than one tale of nurses going in to rearrange the bedding or taking the gauze off only to find the affected toe had fallen off, and the patient not noticing it.
> Some people insist they make progress and listen 3x, but nobody showed any practical measurements of own skills.

Perception is a strong force, and being good at "evaluating your current ability", and more broadly being good at "evaluating how good you are at evaluating your current ability", is a skill in itself.

Awareness that you may currently be incapable of measuring these things in an unbiased way is a big step on this path, the next step being the realization that you probably are incapable.
Not really my resume, but I just created my Portfolio website: https://rjavaux.be/.

Let me know if you can find anything you would improve :).
but is formal verification required/needed to solve latest security issues?

I mean those related to: CPUs, NPM, External Libraries, parsers written in unsafe languages
hey everyone! Airbyte co-founder here.

We started Airbyte in July 2020 as an open-source approach to address the ever-growing data integration problem. We felt that the current ELT solutions were not solving the problem at all. Fast forward to today and we're super thankful to our community, without which we couldn't have this vision to power all data movement including the long tail.

Happy to answer any questions you might have :)!

Michel and I are also hosting a live session on Monday 01/11 where we will show the community the pitch we gave investors to raise that round. Don't hesitate to sign up: https://app.livestorm.co/airbyte/behind-the-curtain-of-airby...
100% agree. After postman asked me to make an account I uninstalled it and have been building my own. It's not all wired together yet but I'm using this fork of https://github.com/dylanowen/dot-http/tree/wasm-library

I wanted something where I could store and share my requests over git instead of creating some random account. I also wanted the api description to be text not a UI+JSON blob.

I also made this
https://github.com/dylanowen/sublime-dot-http
How to use ThreatMapper to quickly detect Log4j2 exploitability
Log emission can often have a negative impact on performance, especially since peak logs and peak traffic tend to coincide. I’ve seen P95 latencies suffer just because of logs.

> How much log data do you think cloudwatch and the other majors filter per hour?

How much do you think the major providers pay for that infrastructure per hour, and are you willing to shoulder that cost too?

(Hint: log ingestion is $0.50 per gigabyte in cloudwatch. So a terabyte of logs an hour is $512/hr)
The laws were not. The judicial decisions that made it far more difficult to hold people against their will - which ultimately drove a lot of deinstitutionalization; the asylums were closed mostly as a response, not a cause - are effectively irrevocable.
I'll take Obj-C over Swift any day. With Swift I feel like I have one arm tied behind my back and I'm constantly wrestling with it in order to do what I want.
Better, simpler data flow frameworks. Represent all your business's logic declaratively, or at least succinctly. Connect up all the inputs, batch or streaming. The platform automagically maintains your data, always consistent and up-to-date. Apps are just views on top of this that trigger more events later. Find a bug in some of your logic? Fix it and the entire dataset refreshes, with policies on how you want to deal with external integrations that trigger off the back of that. This is what a lot of enterprise data infrastructure already looks like, but cobbled together and slow and buggy. I don't think adding no/low code on top of that really moves the needle. Make it painless and joyful from beginning to end.

If you're thinking of wearables, I personally don't think there's anything interesting there until someone can work out a decent high-bandwidth way of communicating with your device. Gimme something like subvocalisation that doesn't require me to wear something stupid or talk out loud.
Rec Room raises $145M at $3.5B valuation for its user-generated gaming platform
The devs do. We have a system that slowly releases software to production in stages, and devs watch their deployment and a-b metrics to make sure the deployment is working.
In Germany any website is required to have a contact e-mail with a human at the other side.

I used to see this as an example of German overregulation, but I changed my mind when I could use it to recover my account at a big social network. In any other nation I would have lost my account for good.
I think my most recent experience was a LIDL that wouldn't take a beer bottle from REWE.
Actually delivering on that would be impressive. And I'm not a Facebook property user.
> This is all well and good, but then we need a serious alternative funding model for websites.

Why?

Without competition from free-but-funded-with-$billions ad-supported services, most of the valuable stuff would probably be replaced by volunteer and non-profit efforts.

Others would survive by charging (more) money.

Some would be replaced by protocols (several social networks would be among those replaced). Clients & hosting may be paid, or not. It'd work out fine.

Most of the rest isn't valuable.
If you do business in the EU, you likely have money there. Might be hard for a company that isn’t international to be fined though. However, California has privacy laws now and could fine a US company.
Garbage collectors don't want to handle glass when it's mixed in with the other waste. So it is already collected separately. Might as well recycle it.
In practice it's worked out ok https://mobile.twitter.com/ScottGottliebMD/status/1472664060...
Electricians probably make more than half of the folks commenting on HN.
Deno is the thing I think I can realistically hope for as a technological breakthrough in 2022.

If it does it can become huge. Not because of TypeScript as a native language. Not because it can create binaries. Not because it has an audited standard library or any other good reason.

But because it includes a simple but flexible way to prevent itself from doing things the author didn't want it to.

If we are extremely lucky other platforms will pick this up.
thanks malthus
Bugs are evolving to eat plastic
Yep! As I said, not quite a 1.0 release but a bunch of people are using it in production.

And yeah, I think if you want to use SvelteKit the endpoints need to be in something that compiles to JS — not 100% sure.

But it's quite possible to hook Svelte itself into any stack you want. SvelteKit is the bundling up of a bunch of nice defaults whereas Svelte is completely stack agnostic.
Just checked, there's ability to phone home given particular driving conditions for safety.
The link contains a link to the discussion on QOI v2, https://github.com/nigeltao/qoi2-bikeshed/issues.
IDK maybe some sort of Xray like beams were used for better penetration? If the stories are even true, it could have been as simple as changing the curtains to remove listening devices or vary the resonant frequencies.
Haskell, because:

1. every other mainstream language is one step below the Abstractions Ladder and Haskell knowledge converts naturally to any other $mainstream flavour of the day.

2. every other academic/research language either directly or indirectly assumes you are familiar with higher-kinded interfaces and compositions that all practitioners of Haskell are familiar with, which converts naturally to the desire to achieve more (dependent types and formal proofs, effect systems, and so on).

3. map/fold/traverse are ubiquitous patterns across all FP languages, even their syntax and signatures hardly ever vary.

4. you begin to understand and appreciate simple mathematical concepts in the context of industrial programming.
> The grocery business alone must be build on the commerce of poor people, right?

How often do you see grocers advertising own-brand baked beans? If you see baked beans advertised at all, they're drawing attention to the fact that their Heinz beans are 1p cheaper than $COMPETITOR's Heinz beans.

I'm not convinced that advertisers spend much money on pitching to poor people. Most of the ad pitches that I see are for high-end products like cars, holidays, and household appliances. There's not much point in advertising to people whose weekly budget doesn't stretch to luxuries. They will buy only what they need; they don't have choices.
We need R0 to be under 1.