skysight-inc/HackerNews huggingface dataset:
Ask HN: Digital nomads of HN, how do you do it?
Given the prevalence of people on this forum who are working remote jobs, I figure there's a good number of "digital nomads" here. What's your story? Where are you now? How do you handle taxes and what do you do if you work for a U.S. employer and need to keep a U.S. address?
His point is not really abandon all the insight porns - but rather pick only those that you can experiment with. And if all his advice do provide something actionable, he's living up to his words.
The version I like is “Anything worth doing is worth doing poorly.” Vacuuming the grossest parts of the floor is better than not vacuuming, even if I don’t bother to clean up all the toys and do a thorough job.
It is.

The industry has really build around 2 vendors for chips, and two vendors for software solutions for those chips, AMI and Insyde. These systems are generally pretty locked dow , but there are was to get to the Linux core(sometimes serial headers).
Big hydrogen subsidies in the climate bill that just passed the senate. Remains to be seen if it’ll build hype.
I wouldn't be surprised if the fraudster used Twilio's own platform to send the phishing SMS to its own employees.

If this is in fact the case, I wonder if Twilio becomes even more liability for such customer damages. Note: additionally, Twilio uses it's own Authy for MFA.
Please state your exact point.

One narrow interpretation is that one particular study that you did not cite got it wrong.

One broad interpretation is that we should not pay attention or give credence to the good faith estimates offered at the time.

I get tired of snarky one-liners that don't say what they mean. They do not promote useful discussion. My comment here would not be necessary if you took a few minutes to elaborate about what you meant.

Lastly: Estimates change. No model is perfect but some are useful.
I think you're on to something. The modern day chat-bot/answer engines seem very susceptible towards trying to answer fact-based, yet obviously incorrect questions. They seem unable to parse the entire question and instead focus on the most generic terms. For instance, the "What year did Neil Armstrong land on Mars?" example that shows up on HN from time to time.
I hope so, but the last two and a half years hasn't given me much reason to believe it will happen. Most people I know willingly signed up for a vaccine based social credit system without much question.
Yet here you are on a discussion about it, of many rust discussions. Many companies use it enough that most of the MANGA companies have openings for it.

How is that not mainstream by even your own definition? It’s consistently a part of the current zeitgeist.
I think this is somewhat similar to what I often do when I need to work on something and never seem to get started: Define the absolutely minimal next step very concretely.

Procrastinating on filing taxes. Next step is to log in to tax preparation app.

Procrastinating on cleaning office. Next step is to pick up a piece of paper off the desk and throw it away.

Whatever it might be, once I get to something absolutely concrete and absolutely doable... I can usually get started and make some progress.

It's much easier (for me) to procrastinate on "do your taxes" than "log in to tax prep app." Once it's that clear it's like... ok, why procrastinate on that?
I can't be the only one laughing that Twilio employees were phished with SMS messages.
Germany will not build any new LNG terminals when in a few short years they can just resume buying from the cheapest seller, before the first new terminal has even finished being constructed.

Simultaneously Russia is not stupid enough to completely cut off the gas and trigger a total crisis. They are pulling on the chains but they understand the risk to the relationship just as well as you do. Don't forget all the gas supply shortages to date have been justified in terms of required maintenances and problems due to western sanctions. That's paving a route for resumption of normal relations between both parties at a later date with no loss of face for either party.
Given Twilio is an SMS company it seems like they would/should have an “official phone number” that any company related SMSes would come from. That would make this kind of attack harder.

(Maybe they already have this, the article doesn’t say)

Very unfortunate incident, and rather scary if this is targeting multiple companies.
> legislation would likely move more quickly

I tend to think the slow pace is a feature not a bug. Could you imagine if something like Roe v Wade was flip flopping every 4 years on political whims?

That said, I do think a modern democracy should have more frequent digital voting abilities perhaps on a policy level. Voting for a person you hope will represent you, it’s a decent concept when you lack technology but as we know it’s heavily flawed as well. I don’t quite understand how we can build something like Bitcoin but can’t solve digital voting in a way that’s not constantly under threat of hacking/some Evil manufacturer etc.
> Because it also has costs, not just benefits.

That's not really true. Certificates have been free for a long time and every CPU made within the last 10 years has AES acceleration. You can google white papers from companies like Cloudflare and Google, which actually show speedups with HTTP 2 or 3.
I'm a full-stack developer with 5 years of experience in building SaaS and web applications. Began my career in video post-production and evolved towards product development with expertise in creating visual experiences.

Looking for a front-end or full stack product development role in a company whose product creates value for customers and has nice people. Relevant? ping me at noamraby@gmail.com or read further.

Location: Berlin

Remote: Hybrid with site in Berlin. I would like to see colleagues face to face at least once a week

Willing to relocate: No

Resume: https://noamr.link/resume.html

LinkedIn: https://www.linkedin.com/in/NoamRaby/

Email: noamraby@gmail.com

Tech: JavaScript, TypeScript, React, Redux, CSS, Node.js, REST & GraphQL APIs, PostgreSQL, DynamoDB, AWS, Jenkins CI/CD, FFmpeg, Adobe After Effects, Adobe Common Extensibility Platform (CEP)

No recruiters please.
As long as wealth inequality continues to exist, so too will immortality fail to exist.

Immortality has no tolerance for stagnant dynasties. Intertwined with mortality and death is one chimp tribe believing they are superior to another, biologically identical chimp tribe simply due to differing starting circumstances or chance (right place, right time, right background, “wow I must be a genius!”).

As long as our economy plays out via genetic and social lottery instead of true merit, rewards the unrewarding, and allows small groups to profit while large groups toil and suffer, immortality will be out of reach.

Might also want to be in space, too, since Earth has limited capacity. May also want to have more reliable energy that can come with us into the depths of space.

What do I know though, just some nobody.
Depending where the bot is and what time of day it is, it might tell you the wrong day of the week.
Stuff that you value. It is a simple and long term system specifically to maintain long term consistency. It just isn’t easy to do.
How low is Manhattan? Projections have always been around 50-100 cm sea level rise for the next century.
“you could probably match everything to a single person if you wanted to.”

You could probably match it to a single car owner but I'll bet you'd have a hard time matching it to a single person purely using data without some research, and people let other people borrow cars more frequently than mobile phones. Though you probably could fingerprint someone's driving style based on starts/stop cadence, turn velocity, routes, destinations, etc. and some insurance companies may already do it. They use this data to modify their clients rates automatically, already. That's why I opted to not use my housing insurer, Lemonade, to insure my car. I don't need surveillance capitalism invading yet another part of my existence.

In the case of red light cameras (https://www.thepublicdiscourse.com/2017/01/18093/), I think the legal consequences are so comparatively minor that nobody bats an eye when this gets flubbed. When it comes down to this being used as evidence in a major crime, that will probably be harder and surely defense attorneys will be all over it. From a commercial data privacy perspective, it's probably enough of an edge case that their customers wouldn't care much.

I think civil cases may be the more interesting venue for this inconsistency. I don't know if it's still true, but in file sharing cases, folks often didn't question the idea that an IP address could be mapped to a specific person. I'd guess this wouldn't be that much different than having a series of witnesses spotting a license plate without getting a clear view of the driver?

Strange times we live in.
> I see and hear a lot of complaints around inheriting code bases that are less than stellar.

I think this has to do with a common mindset among developers. If they don't immediately recognize familiar patterns and structures then it's the fault of the code. Many folks value readability and believe that code should be written for other humans to read and understand. Yet what we consider readable varies greatly among individuals, programming languages, and communities.

More experienced programmers won't be so easy to jump to conclusions. They may realize that it takes time to understand why code is written or structured a certain way. They recognize that it will take time to learn and appreciate the code.

However experienced programmers also develop a sense of taste and style. They build opinions based on experience and if they see a pattern in use that they associate with negatively then it's likely they will not have a good opinion of the code base.

Less experienced programmers are trying to build their sense of taste and style and will associate with whatever they perceive makes them superior. They often have an immediate and strong reaction to a code base. Their opinions and feedback are often couched in absolute terms.

Personally I've inherited great code bases. One of my favourites was a messy, old C++ web application written in the 90s by someone without much experience at the time. It didn't use any standard libraries, had no tests and documentation was non-existent. It used the file system as the database storing XML files all over the place. A single-threaded CGI application: something I wasn't unfamiliar with.

You would think I would have held my nose while dealing with this code base. Yet I consider it a good one because the team that came before me did a lot of work to wrap this monstrous code base in Python and started writing tests for it: a lot of tests.

Those tests enabled them to start synchronizing the data the application normally stores in XML files into a Postgres database. When I came on I had a completely different idea of what legacy software was. The engineer handing the project over to me gave me their dog-eared copy of Michael Feathers' Working Effectively with Legacy Code.

I like that code base because I learned a lot from it. I kept adding more tests and started adding more functionality and replacing the old C++ bits slowly but surely. Eventually we were able to get rid of the XML stuff, the email system, and replace it with Python code. The application was running the whole time and making the company money. It was a great learning experience.

One of the qualities I've come to value the most in an engineer is tenacity. When someone inherits a code base and can roll up their sleeves and make it something better than it was before: that's someone I want to work with.

Too many developers raise their hands, complain that this code is terrible, and suggest re-writing it. Or they burn out and find new jobs else where. Me? I like to stick around, figure things out, and make them go to 11.
I think I speak for a lot of people when I say the last thing I want is for my local power grid to become a low regulation real time market. We've seen the flaws of the Texas approach, and doubling down on it with a sprinkling of IOT tech on top is not gonna go anywhere good.
While most would call it luck, most self-help "insight porn" from the 1800s would say it is "fortunate" because you are in control of influencing it with your previous actions.

If a complete stranger became your big customer from the same scenario, that would be luck.
I can’t think of any sentiment that I commonly hear that’s as ghoulish as that. As if the moral value of a human life is somehow less than her lifetime net carbon emissions. My only solace is the hope that people who believe that sort of thing will go extinct and be replaced by people whose values are closer to mine.
No, they aren't. This is like saying "Iterators are in the language to walk over hash tables." No, they aren't. It is one of the things they can do, but it isn't what they are there for. What they are there for is to present a sequence of values. They aren't there to walk over trees, or walk over hash tables, or indeed, walk over data structures at all. Even if you think that last one, you don't understand them, because there are iterators that don't involve data structures at all.

You'll be stuck with a wrong understanding of them as long as you think that's what they are. That is one of the things they can be used for, but that's all. It isn't what they are. There are plenty of "monads" that are not being used for "side effects" and are perfectly pure no matter how you look at them, such as the list instance of monad. Rather than arguing with me about how if you bend the list a bit and sort of redefine "side effect" and if you squint a bit, the list instance really is related to "side effects", just don't look at it that way.
A month ago I had a call with Twilio sales / onboarding to consider switching to them from our current IP phone provider. Ironically, I was unable to complete the process because my current work number, which is IP based, would not pass their "put in your number so we can make sure you're a human" verification test because IP numbers are not supported.

I do [edit: NOT] use my personal cell number for anything for security reasons, so even after their insistence that it was safe to use I refused and therefore I was unable to get past the first step of the signup process and went with another provider. After reading this I am feeling validated that I didn't cave.
Precisely.

Amnesty International should have worded their recommendations very carefully any damage to the party under attack.

It would be by now impossible to recover the damage done to Ukrainian civilians or to civilians in general. Amnesty International has discredited itself forever unfortunately.
I suspected that it is artifical, but never RE'd it, holy shit.

I hope EU fines them
> I would also think that you are not capable to run a real ad campaign

That seems like a hell of a leap. There's nothing wrong with bringing attention to your other projects, especially at zero cost.
Monzo froze my account for over a year with no explanation and only released my money after I reported them to the financial ombudsman. Switched to Starling and couldn't be happier with the decision. Monzo's customer support is a clown car, Starling's is fast, responsive and professional.
Black Hat and DEF CON talks of all time
Hi, I work on the PRs team. Happy to answer any questions about this change!

This was posted in the changelog section of our blog, where posts aren’t attributed.

Our roadmap, including PR improvements and features is here: https://github.com/orgs/github/projects/4247/views/1
Can you point out what war crimes is Ukraine committng?

I read the article by Amnesty International and I could not spot any.

Yes, they make crazy accusations and demands but I did not notice any war crime described. If would like to reread the parts where in your opinion it has been described.
Rumors, delays, and early testing suggest Intel’s Arc GPUs are on shaky ground
> PHP + the framework/scaffolding we had was very forgiving of these mistakes. The application would continue to chug along even with a lot of warnings and some data induced errors.

I work in PHP every day, and this is something I've picked up from seeing other resources online. PHP with its automatic casting and loose type comparisons is forgiving. This would be great for getting things to run quickly and making it easy for early web development for a beginner, and I think this has a lot to do with PHP's success and ability to get new developers interested back in the late 90s and early 00s.

The issue with this is it encourages bad behavior if there isn't a style guide for the team in place. Sure, we can pass around a string representation of our integers and it doesn't matter because PHP will handle casting for us whenever, but this leads to sloppy and hard to read code in my experience.

Modern PHP has leaned towards a more powerful type system (relative to its previous). I'm really happy with the static typing that the language has added in and I think that's a huge reason for a lot of the old gross PHP code.

Another one is the easy intermingling of server code and HTML. Again, this is powerful for fast and newby development, but ends up introducing complexity and mess. Writing a SQL query inside of a loop inside of a <table> tag? You can't tell me that isn't at least a little confusing to look at.

Fine language with a good trajectory, and it's legacy helped shape the web, but damn can you get your hands dirty.
I kind of love that your service starts at $1 a month. It's just enough friction to keep spammers away over freemium, and it validates demand through people paying money, however slight.
This is why I don’t get the recent pg hate that’s been happening on HN. He’s always done this, but now people are saying he’s out of touch because he’s rich/white/old. Majority of things he’s blogged are no-nonsense observations.
Alternatively, if you don't have a (good enough) GPU, you can also run it on Google Colab using one of the many available notebooks.

For example, this one [1] works very well.

Google Colab comes with a fair amount of GPU time for free.

[1]: https://colab.research.google.com/drive/1TBo4saFn1BCSfgXsmRE...
"we need to talk" is what you say when you're delivering new unwelcome news.

We need to talk. Look, no one want's to say it because we love you and don't want to hurt your feelings, but your breath is really bad. I'm sorry to have to say it but really it's ok just if address it I promise we'll never mention it again and no one holds it against you.

Wars have always been happeneing and happening everywhere, and they've always been exactly as bad as this or worse. It's not new and it's not news. There is nothing uniquely bad about this one, and this article brings nothing to light the way it purports to, and the trivializing "we need to talk" wording is just plain weird.
It's funny because they open by calling it a "sophisticated" attack... just not true.
I think the underlying idea is spot on, if not the specifics.

Biology, sequencing, health, bioinformatics etc. is going to be huge business.

As of this writing, I believe whole genome sequencing is in the range of $400 with the cost (slowly) dropping exponentially. When the cost of whole genome sequencing gets to be within $100 or below, we'll see a huge influx of whole genome sequencing and all the side effects that come with it, like sequencing colds, flu and other diseases in real time, at home genetic testing, etc.

Not just baby screening but made-to-order organs, personalized medicine, etc.

I think the timeline is going to comparatively long, on the order of 10-20 years, but it's my belief it is coming.
My first company got its investment because one of my co-founders talked about it to a random stranger at a bar, who turned out to have money burning in his pocket.

I second your advice to get lucky.

Most of my 27 year career has followed as a domino from that. Once we'd paid back his investment and exited (for a pittance; the ISP marked we'd entered had become impossible for a small player), his lawyer happened to get a question from another client if he knew any software developers locally. That job led me to meet someone who left to start a company, and I followed. There I met one of the co-founders of my next startup. That startup hired a lawyer who later went on to hire me for one of his startups. The co-founder of that startup hired me for my current job.

There have been interludes that did not follow so directly, and there are certainly things I've done to help things along, but there are also many more examples of luck involved along the way too. I'm sure I could have gotten a lot less lucky and still done ok, or been more lucky and done better, but overall I've come out of a lot of things disproportionately well.
I thought about this for a bit and came to the conclusion that I have, but not because the codebase knocked my socks off. Instead, the codebase didn't have any of the signs of bad practices. Most everything was where I expected it to be, there was sufficient, but not stifling test and review practices, etc. It felt natural to work within.

So I don't think that a good codebase does any one particular thing well, it just avoids the bad parts of bad codebases. Via negativa in practice.
we're talking about the circuit, the bit between the distribution board and the plug

I went and checked and mine are actually 32A
> Do you have a choice in terms of what fuel you can use for your car because I don't.

>Give people cheap EV and people will drive them. Where are they today? I am not a Musk die hard fan, but if Tesla had not shaken up the car companies and threaten them we would not even have electric vehicles today.

>What did we have 10 years ago? A hybrid from Toyota and a few other car makers and that was it.

The way you juxtaposed this is weird. You're implying that if there isn't some pain-free way for consumers to quit fossil fuels then they're not responsible and it's all on governments/corporations. Fossil fuels are currently used because they're the cheapest source of energy, so it's entirely unreasonable to expect that you can quit them without making personal sacrifices.

>Yet, it is still not legal in France(among other countries) to do so for example. Why? because the government does not want people to stop paying 60% taxes each and every time they go to the pump to refill their tank.

>Supposedly it will be legal soon but guess what, they are still going to tax the used cooking oil as if it was oil from the ground. So where is the incentive to switch?

That makes sense considering that the fuel taxes are for funding roads, not as some sort of carbon sin tax.
The Pareto Hypothesis for Getting Hired
I would argue that a lot of the time, people do not inherit a "bad" codebase. They inherit a codebase that successfully made enough of the right quality-vs-speed tradeoffs to survive long enough to be inherited by someone other than its original author.

It's easy to spend a day with a codebase (that others spent years writing) and call it "bad". I'd argue it even feels pretty good to take that stance of superiority. But you're viewing it with literally zero of the context of the time in which it was written. You see none of the constraints, none of the pressures, none of the alternatives presented in the moment.

Particularly for a young or small company, if you're "inheriting" a codebase it's because it's existed and been in operation for a while. Yes, it may still be bad. But I would advise taking time to consider whether it's actually, within the lens of yesterday (or 2 years ago)... good?
Org-Mode Reference Card
There is no good reason they can't provide updates without scooping up all your data.

As a minimum they could keep vin/installed software version number and date times. It would be an acceptable compromise.