skysight-inc/HackerNews huggingface dataset:
>China should find its own path to creating a just society without slavishly and uncritically copying the West (but it should look abroad for good ideas).

The trouble is that doesn't seem to be the intention of those in power in China. Or is it your view that the elite in every society are sincerely interested in justice?
I work as a contractor for a bunch of local businesses and I think I can safely say, companies absolutely hate taking that kind of risk.

A bad developer or hire can produce bad work, be an hr nitemare and also destroy team dynamics.
> Speed limits are exact

And this is exactly the kind of worthless pedantry that masklinn called out.
## Short Term

- https://www.pipelinedaily.com/ for $49/mo, James will send you really good leads on Mondays.

- http://letsworkshop.com/ for $597 every quarter, Robert will send you leads daily.

- Get back to your LinkedIn connection and let your friends/connections know that you're looking for freelance work. I had always had LinkedIn friends/connections who gave me enough work, while I freelance in-between my Startups.

- As for the other advice about working for Agencies. You can try that too. I used to lead a 50+ team of designers and front-end engineers. I had a spreadsheet of my outside contacts (freelancers/contractors) who supplement my team, and for those special requirements.

## Long Term

- Maintain an updated Github (or Bitbucket, Gitlab) public profile, with few public repositories that a potential client can see and gauge your talent.

- Write a blog. You can go technical, or just updates about the works/projects you do.

### Plug

I run a remote-first design + front-end services firm, show me your work (Github, portfolio or otherwise), we might have something for you - https://alarisprime.com/
A couple points. First you could use surface mount ICs and fit a whole lot more circuitry onto one board. Soldering is harder but it should be better in every other way.

Second. The register file could be implemented with far fewer chips if only a single output was used. The A and B register select bits would need to go through a quad 2-1 multiplexor and the output would need to be latched for either A or B and some sequencing logic added to make it work. In other words it would take 2 cycles to read from both A and B operands.

Oh, and don't forget that in RISC-V register 0 is always read as zero so no actual storage is needed for that one.
If there was a big counterweight out at the far end of the cable, and it was sufficiently long enough, wouldn't the centrifugal force acting on the weight counteract the kilos lifted?
Game development has historically been very toxic. Long hours, average pay, and very high stress. Why do you recommend it?
The problem isn't estimates. The problem is in turning estimates into deadlines.

An estimate is probabilistic. There might be 50% chance I can get it done in a week, 70% chance I can get it done in two weeks, and 95% chance I can get it done within the month.

That is great for long term planning. However, if you use that to give me a deadline of two weeks then there is a good chance I won't deliver. This kind of pressure is toxic.
A lot of companies do that already, for machine learning dataset training.
while I'm not arcticbull, I worked for a period of time with somebody who was a minority and completely horrible at their job. Everytime my boss tried to get him fired, HR pushed back
I might say how those with power in the company feel. But not sure I'd say it's "just" that, it can mean the difference between dismissal or criminal charges vs a promotion in extreme cases, so not something to underestimate.
The Peacemaker
Tech Interviewing Is Broken – A Suggestion
I feel like there has been considerable improvement in the hobbyist PCB scene... Prices, process size, and turnaround time for low layer count boards have come way down. But still, like you say, >4 layer stuff gets crazy expensive fast. Maybe easy access to higher layer counts will be the next milestone.
"VPL"

I missed/mis-understood this bit. I think of the visual side as another slice of how code is constructed/works/understood. I've limited experience of VCL (windstorms) and thought it was terribly clunky, got out an editor and used text.

Visual coding has a place in geometric construction. This has to do with feedback maybe less so on understanding code.
At scout camp we'd send the new kids down to the waterfront for 50 feet of shoreline.
Nbvcxz 1.2.1 released – Now with 10x faster password strength estimations
I focus mostly on front-end work with the ability to work on iOS, PHP, Rails and Phoenix projects. A lot of the places I work at get a lot of front-end work in and need an extra developer for a month or two then they like me and keep me around for a bit longer.
The last release (1.2.0) introduced a new algorithm to combine the matches found within a password which provided better results, but drastically slowed down estimations. I spent some time profiling where that extra time was going, and optimized most of that slowdown away.
Quick advice: You can simply upvote the article. If you look in your profile, there is a history of articles you voted on, and you don't contribute to comment spam
Once you get over the initial effort of switching to surface mount and get a toaster oven/griddle setup, it can actually be quite a lot faster, especially for doing stuff in quantity. Using a stencil you can quickly place paste for all components, then hand place all components and bake it. Of course finding solder bridges and debugging can become a bit tricky...
An even more egregious form of negative work is a developer who is stuck using out of date programming practices AND has a large amount of influence at a company.

At the other extreme is the developer who is so entranced by "newer is better" mentality that they rewrite everything in an attempt to conform to "latest best practices", increasing complexity massively while introducing a bunch of bugs and huge dependencies no one ever actually needed. I've experienced that (and had to undo the mess) a few times.

Relatedly, just as there are "10x" developers, there are "-10x" as well --- it takes the average developer 10 times as long to fix as one of these takes to break.
Am I the only one who hates how it's become received wisdom that, to quote the article, "A skyrocketing real estate market, fueled in large part by the tech industry" is the main culprit for this?

What about height and floor area limits, surrounding communities on the peninsula that won't build, aggressive neighborhood associations in San Francisco, overly-restrictive building and zoning codes (wife is architect in SF, currently going through 2-year permitting process on one of her projects), and excessive developer fees?

It's telling that other cities, e.g. Washington, DC, are experiencing similar levels of economic and population growth, without all the hand-wringing, just by building more hosting stock.

It doesn't have to be this way. It's this way because SF's electorate chooses to make it this way.
> There's a reason you need regular communication: because people walk out of planning meetings with different ideas in their head, even when everyone thinks they agree. If you don't follow up often, nobody will get what they expect.

Regular communication is critical. Often developers forget that the reason this communication is heavily structured, and often in a less than optimal way, is because of the way managers are expected to operate.

For example I have standard weekly meetings because they allow me to block out that time slot. Sure it might be more useful to meet with you tomorrow instead but if I don't have standard times I will be swamped myself
Consumers are terrible at updating their IoT connected devices
Yes, I do have suggestions. A couple of conditions:

- Not thinking about it as a thing someone does.
- Not limiting oneself to places they judge to be the places to do that non thing (I don't know why people think it has to be in bar, club, gym.)

There's an enormous pressure on people that makes them do sad things. Going to meetups and "trying to make friends" is a bit sad because the premise is depressing.

You can meet people everywhere. Street, café, bus, beach, etc.

Here's a great way: have a standard reaction to someone looking at you. Warm smile (no need to show teeth, even), and a light "hi". Nothing fancy.

With anyone who looks at you long enough (old lady, big dude, police officer).

This prevents you from thinking of coming up with something to say, and trying to come up with something to say is what gets most people in trouble. It is also positive to the other person, simple. It is what you do with people you know.

The important thing here isn't really the reaction of the others. Some will ignore you. Some will think you're strange. Maybe they're having a bad day.

You will get in a lot of conversations with a lot of people in different situations. It takes the pressure out to "find friends" at meetups/bars/gyms at specific times because you can talk with anyone you want.
She is probably trying to salvage the acquisition and won't say anything publicly because it might make the situation worse. In fact, I bet Verizon would prefer that she keep a low profile right now.
The blog post reiterates what everybody probably already knows; similar content gets posted on HN semi-regularly.

On the other hand, I've also heard that most of interns' / junior devs' first projects end up shelved (i.e. net contribution = 0).

From a viewpoint of a mediocre developer, a far more interesting question is how to get into the feedback loop where you actually learn from your mistakes and the quality of your contributions improves.
What's the best free alternative to Eagle?
Similar thing in Victoria too. Larger companies will be a bit more careful and hire you as a casual employee in case they get audited. Some of the smaller companies and agencies don't really care. Sometimes they'll require me to bring in my own tools, which is fine it's all tax deductible. There's probably not a ton of work like this in SA. Maybe some people at Majoran and Hub would need someone short term but I think having so many head offices and dev centres on the east coast a lot of the work would be centered over there.
There is another kind of pernicious developer: the one who writes large amounts of seemingly effective, but ultimately bloated code.

What we often fail to realize is that 'code = cost'. Once written, code has to be maintained, and every line adds to the inherent complexity of the system.

I think we are all familiar with that old IBM (OS/2?) allegory of the dev who mostly spent time removing code from the system, and had to justify his salary because they were measuring 'lines produced' as a metric. If you can 'remove a line of code' from software and it still 'does the same thing' ... well, that's definitely worth more than adding code :).

Anyhow, it's worth considering that 'number of lines of code' is really quite a bad measure of anything.

Second - some people are really bright, but they struggle with clarity etc.. Perhaps it would be appropriate to put someone like this on a bug clearing team? They can 'solve problems' by tracking down issues, and hopefully fix them. 'Fixing' code is often much safer than writing new code as the patterns, standards, practices are already 'in place'.

It's a rather a paradoxical and intriguing business, writing code!
Who cares about poor unit tests in this case? It's all about the INTEGRATION tests that run on CI to make sure your bad developer can only fuck their shit up and not anyone else's. And if you have bad developers building your integration testing framework, you have bigger problems.
I'm not the author, but I've etched my own boards. My graduate thesis project contained a couple dozen homebrew boards by the time all was said and done.

I used a photo-resist process based on transparencies that I made in the department Xerox machine.

The biggest improvement in moving to real manufactured boards was plated-through holes. For that reason alone, I wouldn't go back. Not only are boards easier to route with PTH's, but they are also more robust -- it's harder to lift a pad off the board when removing a component.

Solder mask is a boon as well, especially for surface mount.
If you're lucky you'll skip to bedroom acrobatics
Kicad: http://kicad-pcb.org/

There's a bit of a learning curve, but it's a highly capable EDA suite.
+1 to this.

I used to work with a guy like that and it created a ton of tech debt. He would write new services using a new technology for each one, not to documenting or maintaining any of them.
More recent versions of Windows Server have definitely improved, but this is still pretty accurate. When given a set of tasks to do for Windows and Linux, the latter is always easier. If it takes x amount of time to automate something on Linux, it's 5x on Windows. Every time. Some of this is due to MS themselves, some of it is due to the software vendors, but it's a very real thing.
Only on the island of Manhattan. The other boroughs of New York City do not have the same concentration of households making this much.

The article's sources are listed at the bottom of the page, and they are primarily household income statistics.
The "convoluted code" gauge is a double-edged sword. You could also be working at a company with developers who have no experience with the benefits of functional programming. In this scenario it's those who write nested loops, branching if-statements, and mutating side-effects that are in charge and you're the bad developer for using fold and map. You could be seen as an elitist who likes to write clever, obfuscated code that nobody else can comprehend.

Not all positive contributions are worthwhile. One could simply blend in and add one more level of nesting, one more conditional, and mutate a few things here n there. After all, everyone knows what a for-loop is, right? Staying productive is important!

Well... until your most productive hours are spent chasing down errors you and your team designed.
Realm of Racket would likely have been a really good alternative.

Maybe NAND to Tetris.
If someone checks in code that breaks a bunch of tests, then you know right away. And the underlying assumption is that tests are written by multiple people with varying degrees of quality. Can bad code sneak through the tests? Of course! But to say it does no good at all is wrong.
I've found that code reviews are one of the best ways to increase code quality. Even just talking with other developers about why they've done things is helpful in thinking about simpler options and keeping things closer to the architectural vision.
Wow, you just described my side work as a freelance musician.
Even then... you don't need the DB and SSMS to be on the same box.

The installs are on separate ISO's now if I'm not mistaken...
This seems strange to me as well. How were they planning/tracking the work that needed to be done for their project?
Great Programming Quotes
Ask HN: Is monthly rent on Airbnb expensive than usual annual rental in SF?
If so, how much is it more expensive?
What visa are you currently on, do you have indefinite leave to remain (ilr)? Up until a couple of years ago if you had been in the UK for five years you could apply for citizenship depending on if you had ilr and then of course you would have no limitations to what you do as a founder.
Yep!

> It's telling that other cities, e.g. Washington, DC, are experiencing similar levels of economic and population growth

And not are all tech hubs. Nyc is more finance driven than tech. D.C. is a very different beast.
Let's call Aphyr ;)

https://aphyr.com/about
It's Official: Clinton's Popular Vote Win Came Entirely from California
As an aside, how to you accurately measure memory bandwidth? I've been looking for a good solution but couldn't find one.
The Flint water crisis – a visual essay
Yeah, a ton of data goes to music and video. On the plus side, I no longer spend a ton of physical space on these. Not sure what is more wasteful, tons of movies and music I don't get to on my computer, or bookshelves of the same.

And I still have a fair number of books.
> it's not like anyone is going to use tor for ddos.

Perhaps not DDOS, but yes, tor is absolutely used maliciously:

> Based on data across the CloudFlare network, 94% of requests that we see across the Tor network are per se malicious. That doesn’t mean they are visiting controversial content, but instead that they are automated requests designed to harm our customers. A large percentage of the comment spam, vulnerability scanning, ad click fraud, content scraping, and login scanning comes via the Tor network. To give you some sense, based on data from Project Honey Pot, 18% of global email spam, or approximately 6.5 trillion unwanted messages per year, begin with an automated bot harvesting email addresses via the Tor network.

Source: https://blog.cloudflare.com/the-trouble-with-tor/

Counterpoint: https://blog.torproject.org/blog/trouble-cloudflare
علائم هشدار دهنده غلظت خون+راه های درمان سنتی غلظت خون
Only if you assume it actually works, which is the most blatantly circular logic in this thread.

This guy could have said "I feel like a daily prayer in the server room would filter bad devs" and it would be just as proven as his feeling about whiteboarding.
Damn. I work like 60 hours/week and I barely make a thousand a month when is a good project. I have to get first-world projects.
That doesn't seem reasonable. They had the same routes to profitability as Google, but just didn't execute well.
That's very interesting. Turkey is a really intriguing place - they are on the threshold of so many thing, culturally, politically, economically. On some days they seem like a regular, modern nation ... the next day there is a 'coup attempt' and the Prez. is announcing mass jailings :)
I feel like it's a "right tool for the job" situation. Fortran was literally built for the purpose of numerical computation. Multi-dimensional arrays, non-aliasing arrays and pointers, multi-dimensional array intrinsics, intrinsic array binary operators... all come with Fortran right out of the box. Of course, C/C++ can do all of these things, but all of the proposed methods, at least that I have seen, feel like they are trying to hammer a screw.
To be fair, many debugging tool chains are crap with folds and maps instead of loops. And code is rarely written in anger, but often debugged that way.
There are both upstream problems (hiring the wrong people) and downstream problems (having process to catch garbage before it gets into mainline). You need both as you will inevitably make a bad hire somewhere along the way. For downstream prevention you need good processes to catch poor quality code. We've found that automated (static analysis [we like sonarqube]) plus consistent human code reviews goes a long way to ensuring a high quality code base.
Not all developers make positive contributions, but no single developer in a team of developers can make a non-positive contribution. They can't, because as a team, you've decided to allow this person to make contributions alone. You need to own that contribution. If you don't want to that responsibility, there is a solution: code reviews.

Anything that gets submitted is literally something you've agreed to support and are okay with being in the code base.
Migrating a host from one ZFS pool to another
The only google results come back here, so I'm guessing it's a place holder word for "a lot", like a bajillion.
Just questioning the implementation is enough to improve quality. Plus it helps people grow without putting them on the spot (if done right).
Sounds fair. If you want ownership, take the risk and leave the salaried job.
Love Your Homemade Quilt? Thank Technology
Randy Pausch, the last lecture

https://www.youtube.com/watch?v=ji5_MqicxSo&app=desktop
Sounds legit. Someone should look into this.
JoinRun and Chymyst – Join Calculus, Declarative Concurrency in Scala
If the numerics people can't agree on something, throwing the decision over to the core Rust folks is unlikely to result in something better.

So, the question still stands: What in Rust prevents an ambitious number cruncher with good design taste from adding the appropriate pieces to the language?
Agreed. It seems like the manifesto is designed with the idea that engineers should not develop any soft skills, primarily communication.

I find biweekly or monthly meetings with stakeholders to be extremely useful. I do not tie my work output to these meetings. They are just status updates, feedback, and plans for the future. I try to walk into them without a plan, just a set time for a conversation. Sometimes I don't have anything to show unless they "want to watch tests run." In which case I get a resounding, "No," and we move on. It is up to you as a developer to set the tone for these meetings. Frame it as a conversation, not a presentation.

Most process breakdowns and anger are rooted in the fact that people don't understand each other's job. Sitting in an office, and passing "quality" work under the door irregularly does not help. Management has no visibility into this and will eventually lead to confrontation. Being open and honest with communication builds trust which will lead to longer lasting happiness than sequestering yourself away.

I would agree that software estimates are hard. The simple solution to that is take whatever you think it will be and double it, triple it, quintuple it. Whatever works for you. Under promise and over deliver might be controversial, but I think it applies here. It's more about giving yourself room than wowing management.

Sometimes those misestimations are because you are blocked by other team. No one develops by themselves, no matter how much of a 10x engineer you think you are. This is where the trust you built with management comes into play. Use them as a tool to get things done across teams.

This manifesto is all about giving back the power to the developer to manage their own time. It basically says, "Developers do want you want. And management, stay out of their way." Its reactionary, because the author feels like Agile/SCRUM has been used against them. This is completely understandable. Feeling powerless is heartbreaking. But trying to implement something like this would never fly. And if it did, it would eventually be twisted just like Agile has. No manifesto will help you in this case. You need to learn how to communicate, and through communication reassert your power over your situation and the decisions being made by participating.
Because you are one ?
Yeah, in California it is similar except you need to use the bike lane if there is one and it is safe. But you are allowed to leave it for debris or other reasons. On single lane highways with no passing lane, if 5 or more cars are behind you, you are expected to turn off so they can pass. But most will just illegally pass.
This is such nonsense.

A motorist going 10 mph on a 30 mph speed limit street isn't breaking any law, neither is a cyclist. Driving slow on a single lane road is not impeding traffic anymore than red lights, yield signs, or left hand turns are impeding traffic.
> You will probably come across people saying that the programs are not idiomatic ("enough").

This seems to describe me. I am tempted to rewrite those programs more idiomatically. Thank you for pointing this out.
The "rules lawyering" is probably why they don't make the details of these rules public.
IPv6 allocations are generally /64s, or /56s, and are typically blocked as a full range.

Individually blocking IPv6 addresses, as /128s, would indeed be futile.