skysight-inc/HackerNews huggingface dataset:
Look into invoice factoring services. You sell your invoices to them and get paid upfront. They get a % of your invoice and/or a small processing fee.

Ideally you want a non-recourse factoring agreement (the one where the factoring company takes most of the risk of non-payment), but it might be difficult to get. It helps if you can show that your previous clients paid on time. But then again the freelancing platforms handled that for you.

In any case, it's worth asking around. Have your lawyer review the factoring terms before you agree to anything.
Sounds like a reasonable initiative:

> The NYC Bin is the official bin exclusively for properties with 1-9 residential units (including single-family homes to 9-unit apartment buildings) to set out their trash. It is available for purchase at a significantly lower price than similar bins at retail stores.

> The NYC Bin is the next step in New York City’s plan to get black bags of garbage off the streets and make our city cleaner and safer for all New Yorkers.
Binary secret scanning prevents serious supply chain attack on Python ecosystem
This. I don't mean it as a criticism towards the employer: if they ignored profit and favoured the employees they would go out of business and eventually that would be bad for the employees as well.

It's just how it is: your employer is not your friend. It's a contract.
...Which assumes I had a choice for a good chunk of my career. ;)

But yes, technically correct.
People are quick to break fevers, but probably shouldn’t, most of the time.

Fevers are there to kill the virus.

You only need to break them if they get high enough to pose a danger to the brain or other organs.

Which is a lot higher than a low-grade fever.
The original title of the article ("How To Survive 3 Years In North Korea As A Foreigner") sounds unnecessarily hyperbolic to me considering that the author led a relatively comfortable life (having a swimming pool, being able to play tennis and golf) with only minor inconveniences, while some North Koreans were actually starving at the time...
> It's really bizarre.

Everything seems bizarre before it becomes the new standard.
In Russia, if it is a foreign client, the OP would have been fined by the government for the amount that the client owes him, now that the OP publicly admitted the non-payment. This is done because there was a tax evasion scheme based on allegedly-unpaid invoices from foreign "customers". So it is already 300% of losses (100% due to the unpaid debt plus 100% from the fine plus 100% from the lawyer).
Only if you remember, which you, or someone else, is bound to not eventually
> “There’s been a systematic change where employees feel the employer is extremely lucky to have them,”

Aren’t they? I feel like that’s a healthy way of looking at it. Goes both ways though.

> “We need to remind people they work for the employer, not the other way around.”

What does this even mean? Remind how? And why isn’t mentioned that it’s supposed to be a mutually beneficial exchange?
As a palette cleanser and loin girder: https://www.youtube.com/watch?v=jVkLVRt6c1U (You already guessed it was Mike Monteiro.)

For this project:

Did they refuse to pay actively ("We won't pay you."), or passively (No replies to emails.) The latter might be incompetence.

As others mentioned, specific legal advice depends on respective jurisdictions, but an offical lawyer's letter sometimes wakes up legal when accounting is drifting.

Did you deliver the final access to the code / server / credentials? If not, gently bring servers, DBs, platforms to a halt pending final payments.

Future projects:

Contract, always.

Up-front commencement payments, always.

Price yourself higher in the initial quote, and ask for staged payments, such that by the time your delivery schedule is 50-75% done you are 100% paid.

You control the source code accounts, you control the server credentials, you control the database access credentials, you hand over final access after the final check has cleared.
The fact that layers are hashed with SHA256 is IMO a mistake. Layers are large, and using SHA256 means that you can’t incrementally verify the layer as you download it, which means that extreme care would be needed to start unpacking a layer while downloading it. And SHA256 is fast but not that fast, whereas if you really feel like downloading in parallel, a hash tree can be verified in parallel.

A hash tree would have been nicer, and parallel uploads would have been an extra bonus.
I'm... confused. Being able to intercept and modify syscalls is a neat trick, but why is it applicable here?

In python you generally have two kinds of randomness: cryptographically-secure randomness, and pseudorandomness. The general recommendation is: if you need a CSRNG, use ``os.urandom`` -- or, more recently, the stdlib ``secrets`` module. But if it doesn't need to be cryptographically secure, you should use the stdlib ``random`` module.

The thing is, the ``random`` module gives you the ability to seed and re-seed the underlying PRNG state machine. You can even create your own instances of the PRNG state machine, if you want to isolate yourself from other libraries, and then you can seed or reseed that state machine at will without affecting anything else. So for pseudorandom "randomness", the stdlib already exposes a purpose-built function that does exactly what the OP needs. Also, within individual tests, it's perfectly possible to monkeypatch the root PRNG in the random module with your own temporary copy, modify the seed, etc, so you can even make this work on a per-test basis, using completely bog-standard python, no special sauce required. Well-written libraries even expose this as a primitive for dependency injection, so that you can have direct control over the PRNG.

Meanwhile, for applications that require CSRNG... you really shouldn't be writing code that is testing for a deterministic result. At least in my experience, assuming you aren't testing the implementation of cryptographic primitives, there are always better strategies -- things like round-trip tests, for example.

So... are the 3rd-party deps just "misbehaving" and calling ``os.urandom`` for no reason? Does the OP author not know about ``random.seed``? Does the author want to avoid monkeypatches in tests (which are completely standard practice in python)? Is there something else going on entirely? Intercepting syscalls to get deterministic randomness in python really feels like bringing an atom bomb to a game of fingerguns.
I'm going to say this as nicely as I can. Secrets Manager can fuck right off with their $.50/mo/secret pricing.

Moved all our secrets to S3 a long time ago and haven't looked back.
Fuel efficiency is more about plane itself (aerodynamic optimisation as well as weight saving) than about engines.
Symfonium [0] (which supports pretty much anything but koel) is a commercial android app, can cache & export, have rules for doing so automatically, supports a rolling cache, can decide via wifi connection if the cached or online version should be used. You can also choose if you want original files or transcoded ones.

[0]: https://symfonium.app/
I do think the high level of autodidacts makes it very different from anything else. It doesn't feel like a "trade", those involve building things with your hands. It's perhaps more similar to a "profession", like the much older ones of lawyers and doctors, but it hasn't developed the professional organization structure to go with it.

Disintermediation also makes a difference. It's possible - very unlikely for any one person, but possible, and keeps happening - to just bootstrap a product out of pure labour and very little capital. At which point they get to keep a lot of the returns. It doesn't at all fit a nineteenth-century economic model, so you can't apply the M word.

The "10x" phenomenon also makes a difference. Whether it's real or not, I think enough programmers believe it's real and want to be part of the 10x and somehow get a 10x reward. This is the exact opposite of a factory line or mass farmworker situation.

(there's lots of interesting business anthropology research on piecework vs hourly rate work, I believe)
Went too archaic there with the typo :)

PS. No. Me neither. No one, methinks (at least, no one now) ...

... it was meant skeptically.-
But AWS Secrets Manager does that already, without the Agent. It seems like the main value-add of the Agent is that you don’t have to manage a cache in your application code but still get the performance/cost advantage of having one.
I created my CV with React and Semantic UI since I was not satisfied with the amount of visual precision Word provides. The stack choice was due to personal ease of use, Semantic is probably an overkill.

Recently, I started turning it into a template and added some documentation. The next step is to feed the data (experience, education) through JSON so it's easier for others. It is automated to the point of generating a new preview GIF every time I push to master. I still manually hit CTRL+P to get the PDF though, it feels faster than implementing automation.

I'll hopefully do a Show HN in the future but until then, here is a demo on GitHub Pages: https://mrtysn.github.io/cv/
The markets can, notoriously, remain irrational longer than you can remain solvent.

But they generally can't do so _forever_.
the major engine OEMs aren't investing enormous amounts in optimising for a startup airframe program though, so at best you're getting a derivative of the engine on the equivalent sized Boeing/Airbus program with roughly the same fuel efficiency but worse expectations in every other relevant area (expected reliability, competitive local maintenance markets, type-rated crew availability, commonality with existing fleet, residual values etc, and probably worse aerodynamics and structural weight) due to the airframe program's relative immaturity
It will happen, maybe not today, maybe not tomorrow but there's a movement to do it. No matter your vote, no matter your opinion.

The solution is to create asap an opensource sideload-ready app to maintain private conversations. When dictatorship is a fact, revolution becomes a right.
> There are limits to how much of a good person you can be, those limits are set by the economic system we exist in.

> you should be upset about the system that is requiring those persons to act this way in order to stay afloat.

How would you change the system or modify the current situation in order to define new limits that are more, let's say, humane?

In the article, there is an example of an ex-Google employee that got fired via email, he couldn't say "Bye" to his colleagues after 20 years of working with them. That doesn't seem like a system with reasonable limits.
> If you are loyal to your employer and do not own a significant part of the organization, then you should take a good hard look at why you're loyal -- and whether or not your employer is loyal to you in return.

As someone who works at a 2 person company (my boss and me), it's the good relationship with him along with the relaxed work environment. Sure, we have to be profitable, but not exceedingly so.

> I will note, however, that there is also more to the story than simply "being disposable." An argument can be made that laying off however many employees also helps to preserve the ongoing livelihood of the employees who remain.

> The error is often not in the layoff. It's in over-hiring in the first place. And that changes the "how evil are these people?" equation rather drastically IMO.

Those are mostly a problem at larger companies, IME.

I was exceedingly lucky with most of my jobs so far, in the sense that I mostly got good work environments where employees are actually valued beyond mere numbers. I wish others would be as lucky as I was.
Could it be possible to run containers within this environment?

I ask because I personally think we are headed towards a future where web browsers are just sandboxed container environments where we download and run containers for each app...

Eventually, even calling them "web" browsers might feel a little odd, almost the way in which we "dial" a phone number today, even though we now mostly key it in on a touch screen.
To be a strong candidate for US government development you typically need:

* a security certification like Security+ or better

* a government security clearance, but contractor employers might work with you to get this started if you don’t already have it

* a bachelor’s degree. This isn’t required but it is helpful.

* having experience that is both well rounded and a specialization. For instance in JavaScript land where I came from nobody can talk through networking, the OSI model, security or any other real world value. This kind on knowledge, at a very basic entry level, is generally expected in government work. Expect to compete or work with former military who will have this generalized knowledge in spades.

In my case I had all these already because I am part time military. I still had to go get an additional cert as a condition of this particular job.
> That's a nonsensical definition. By that standard literally everything is political

The definition implies it, yes

> which means the word has no meaning.

I disagree, the "if everithing is X then nothing is X" applies only to thing that are in part defined as negative/contrapposition like being special, tall, a luxury, progressive, conservative, etc. it does not make sense when applied to things like being religious, having human rights, being moral.

"Everithing is political" means that nothing can be fully separated and insulated from the surrounding political atmosphere. I personally think it is not a constructive way to perceive the world, but it is perfectly self-consistent
I would argue that it happens more than you may think. You depend on an LGPL library? Tell your manager that either you can make the module that links to it LGPL as well, or that you can keep it proprietary but it will take "a lot of work". Often the manager will not value that piece of code so much and will allow you to open source it.

Your employer allows you to open source something? Push for a copyleft license and no CLA.

Your manager says that "we could consider open sourcing it"? Take this as a yes.

Learn about licenses, what they mean, and think about IP at work. Many times the employer does not get anything from not open sourcing the code. It's just that they don't care. If you do, you can push them towards doing it.

I am not saying that it will be bad for the employer! It may actually be good. I am just saying that it is better for you as a developer, so you should push for it.
> Certainly not true for the company where I work.

How do you know that? Even if so, how do you know that it won't change in future?
If you can convince your company to do that, you can probably convince them to use a copyleft license, I would think.
Ludwig von Mises

"In the market economy the worker sells his services as other people sell their commodities. The employer is not the employee’s lord. He is simply the buyer of services which he must purchase at their market price."
Many employee perspectives here will change the day they start their own company with their own money and hire people to work for them.
Why do you think "abnormal" is bad?
Also - every system that has ever existed has had some variant of this.

Output and effectiveness towards market needs has to matter or eventually the system collapses under its own weight. Churn has to happen, or ‘deadwood’ builds up through inertia.

And when the system collapses, it’s like a forest fire with a massive amount of dead wood - it burns everything to the ground, not to grow again for a generation. As compared to periodic wildfires that may suck, but for which sprouts pop back up again in the spring.
"Recycling bins, Not required, but recommended" I mean they've only discovered the bins, so I'll cut them some slack, but the road is going to be long until NYC has a decent, sustainable waste management system
You're paid to produce code, not to fight against open sourcing it.
Genuinely trying to understand.

Didn't the SR71 fly between LA and NY at above supersonic speeds? Don't military jets fly at supersonic speeds above land?

What makes this allowable in terms of sonic booms? Is it that they're much smaller and the their booms don't cause as much of a "wake" on the ground?
Also maybe it's true for OPs country, not in mine. It costs a lot of money to get rid of someone in my country. So that makes laying people off less profitable.

"it's profitable" hides a world of problem though. "it's profitable" over what timeline - just because an employee isn't doing something profitable this week, doesn't mean they won't be next week. It costs a lot to fire someone even in "at will" countries where you literally just tell them to F-Off
When I chose "might be" rather than "are indeed", that was to say it's not impossible rather than to outright agree. Other companies do have loss-leaders, I cannot rule out the possibility that Apple also does exactly what was asserted in the comment I was replying to.
At least it's part of your portfolio: you can show that code.

What's the worst case? The code just gets unmaintained and dies. That's not a problem at all.
> ask for a raise

The problem is that employers make this process as toxic as it possibly can be, using every trick in the book of emotional manipulation, making you feel like you're blackmailing them and literally destroying their life. Adds a lot of resentment on both sides every time regardless of outcome and it just accumulates.
If you don't need the granularity, you can store all the credentials that will be used by a specific caller(s) in a single JSON object and it will cost you only those $0.50. You can easily fit a thousand, maximum size is 64kb.
Realistic.

It's a job offer, not a marriage vow.

It's great if there can be rapport in a public company (as opposed to private) but that culture is a luxury trim at best.
I'm not sure what you're getting at here. The OP is a 3.5 inch floppy drive, I don't think I ever saw a 5.25 inch drive for Amiga.

I remember some people used to day 3.5 inch floppies "aren't floppy", but it was just the case that was more rigid than the prior formats; the actual rust-on-plastic was still "floppy", opposed to a hard drive platter that is rigid.
I've done it pretty successfully ( https://artsy.github.io/blog/2019/04/29/how-did-artsy-become... ) and now regularly look back at prior source code and blogs as I work on something else but with similar patterns

I would say that getting to a point where this sort of thing is possible requires a huge amount of out-of-bounds culture and technical work though. Probably outside of the commitment range of folks who just want to work as an employee and not think about work outside of your paid hours
It may be expensive, but that's unlikely to be due to infringement.

Most code written by most companies has been written a thousand times already, and there is nothing illegal about recreating a library which behaves the same as something you wrote at a company.
Split the layer up?
Well, the environment itself is a container. Supporting Linux "namespaces" used to implement containers is also a possibility.

As described in the project README we provide a GitHub Action workflow to convert Dockerfiles into bootable images for WebVM: https://github.com/leaningtech/webvm
What’s wrong with https://github.com/distribution/distribution?
Hate to break this to you, folks, but as a human, you are disposable.
API & Server-Side Test Automation
Discover seamless API server-side test automation solutions at Zapple Tech. Optimize your testing processes with advanced tools tailored for efficiency and reliability. Explore now for enhanced performance and flawless integrations.
I think you still don't get my point.

Indeed today there is a lot of devs that don't engage directly with people.

But my point is that "not engaging directly" IS A CHOICE of these individuals, not a fundamental characteristic of the role. And that in fact the role itself requires more engagement than what a lot of devs think they should have.

Please stop reducing "math" to "math teachers". Do you even know that teaching math does not require having enrolled in a math major at university? Any STEM degree will do (and sometimes not even STEM). Also, you can also teach computer science (or worse, if you want to teach math, getting a degree in computer science is as much an option as getting one in math). If it's your criteria, then again, computer science is as people-oriented as math, because people doing computer science can become teacher too.

> But it's less people oriented than solving other people's problems by engaging them directly

But, ideally, devs SHOULD engage directly. They don't do it by choice, and it makes the product of their work LESS GOOD. It also creates strange situation where you need plenty of manager and very constraining processes such as scrum or other planned processes where the devs have to be explained what the people need because they devs are not able to simply ask themselves.

Computer science is more people-oriented than math, in very large portion of the user cases, it works better when the dev engages directly with the people they work for, while for math, people who do math for a living, the majority of the roles involves working on research and development with a very much smaller window of potential interaction with people of varied backgrounds.

> It's just less people oriented than most other jobs.

No, it is not. Intrinsically, the role of software development has way more elements that require interacting with people than a lot of other jobs.

In practice, computer science has cultivated a subculture, in which they started painting the picture of the asocial nerd working in their mancave and glorifying this aspect. The consequence is that women are less interested in computer science not because computer science is intrinsically not for them, but because the stupid mentality that is cultivated by to many people in this field. The consequence is that socially inept people will be more interested in computer science because they see it as a good fit for them.

But, again, when you look at it, on paper, there is absolutely no reason to say that computer science is intrinsically a good fit for socially inept people. If they want a brainy work where they can beaver down on their own little universe without interacting with people, math is 100x more suitable for them. Computer science requires understanding what the client want, and the client surface is big and their background is very varied, which means the dev need social skill to interact with them.
Having done freelance work with customers in different countries (US mostly but France, Japan, China and UK). Americans are not more likely to screw you over than companies in other countries.

But yes, the rest of advice is good. Also when it comes to contract, do be careful about IP rights (more for the customer than the freelance). I've seen some customers get screwed by not clearly stating that the freelance employee transfers their IP right.
In the UK we’ve had these exact bins since the 90s. I actually thought it was a joke. Why would you need to buy them? Surely you pay for these in tax?
In Russia, they'd be using an offshore entity for billing anyway :)
Amen!

Fortunately I only had this problem once, and for me, the way to resolve it was first, with the client. Nagging, explaining to them that if they do not pay, I will sell their invoice to a invoice collection agency, that, if they choose not to pay will affect their credit rating and reputation blah, blah.

The trick is to do this in a serious way, but not overly confrontational and to be clear that all it takes for them is to pay the invoice.

After 6 months of this dance, I said, enough is enough, and initiated the procedure of finding an agency, and then, lo and behold, they paid.

In retrospect I should not have waited 6 months, but your learn with experience. =)
But this only works for public repos right? I assume docker pull wont use a s3 api key