skysight-inc/HackerNews huggingface dataset:
The VEH target is visible if you know where to look. You can use something like Themida to virtualize/obsfucate the VEH if you really need the VEH to be encrypted.

It's actually not so easy to find the VEH because if you are injecting the VEH into a third party process from another process, then not only does the VEH not exist during static analysis of the binary at rest, but its program address changes on each execution. Moreover, the VEH can be encrypted at rest before it is injected into the second process.
In a large organization, this will change nothing. All you can do is be in a trusted position with upper management, and spend your political capital to prevent it. Even then, it may not work if some exec has implementing it as a goal to help their prestige/career.
I'm betting they open it and a singing frog pops out.

Hello my baby, hello my honey, hello my ragtime gal. Send me a note by wire, baby my heart's on fire!
Clever management technique in a shop full of blunt knives will only get you so far.

With my team, we’ve focussed on developing talent just as much as we have on getting the work done. By improving skills through senior-to-junior coaching and code review we’ve built a much more cohesive team that’s better at what they do and can complete tasks which they couldn’t do before. Dexterity and fluency with code was more important to us than organisational skills.

Perhaps I’m missing the point and Scrum is only for people at the top of their game? It didn’t feel that way the few times I’ve seen it — to be a little bitchy, it appeared to be quite the opposite.
And not very common in Canada.
Typical argument from an engineer arguing from math and not understanding that math does not describe human beings and their social relationships.
According to Wikipedia, the most famous students who would have been there in 1828 were Robert E Lee and Jefferson Davis. Also, the valedictorian from 1929, Charles Mason, was the student with the highest scores ever at the academy. He beat out Lee for valedictorian, with Lee holding the record as the second highest scoring student in academy history. (The third highest scoring student ever was Douglas MacArthur 75 years later.)
Transmuting Language Models with FFT, SFT, and Qlora on Colab
I had a team with a shadow backlog. Fun times
I work on a very small scale nowadays, but what I have found to be helpful is "weekend fun" tickets. Nice to have things that I wouldn't do otherwise but are fun when I don't have the energy for other stuff / when I consciously try to reward myself.
When I lived alone there was commitment in buying 4L of milk.

2L carton was about the same price.
If you’re going to have lots of unnecessary meetings, it’s important to keep them short or no one will have time to do work.
This is like complaining that because the shittiest sports team you follow doesn't win that playing that sport well is ipso facto impossible.
I heard an interesting perspective for startups - Kanban/Scrum is useful sometimes before launch, and not using scrum after is beneficial.

Mostly because launching changes so much.

Part of me does feel sometimes that ceremonies are for making sure the development practice is highly inclusive, including for new and less skilled developers still learning their ways. Another part of me thinks about how this also helps more people to be able to generally help with more of the codebase.

I think writing code for your future self or someone else, in a way you'd like to receive is critical to think about. This can include doing things the simpler way even if it's more verbose and more understandable. This isn't always possible, but more often than not, avoidable complexity also can encourage the engagement of a lot of ceremony around it. "Could this have been simpler?" is one useful question for code reviews.
Thank you; that does make more sense.
hey, it's a mistake the admin will never make again, so. be a cup half full person... you don't have to worry about the data any more also.
Very slick and opens up so many possibilities.

WebAssembly, WASI, like WebRTC/WebGPU/WebXR/WebAudio, just makes webdev, gamedev + native/networking very very interesting in this phase of technology where js frameworks are culty bloated/verbose and apps are the main thing for marketing/tools. Web apps + tools are opening up with wasm/wasi.

Runno (https://runno.dev/ + https://runno.dev/wasi) is a great idea and helps make interesting native stuff in a sandbox locally. Running all this directly without having to mash into assembly is a great idea. Awesome job on this!

> Runno helps you make runnable code examples that can be embedded in web pages. This is very handy for educational tools, it means:

> - You can make code examples that don't need users to install scary tools.

> - No need to run a server, it all runs client-side in the browser.

> - Your users can edit and re-run any code examples you make.

> - The examples are extremely customisable with HTML, CSS and JavaScript!
Ah, well, I only did PEX and ABS for my reno, very idiot-proof so I managed. ; )
My only issue with teh or kopi in bags is it no doubt leads to ingesting plastic especially when the drink is hot.
The post-WWII period and beginning of the Cold War (starting dates are somewhat ambiguous, though George F. Kennan's "Long Telegram" was posted in February 1946, and the Truman Doctrine declared on 12 March 1947) also saw an arms race, particularly of increasingly-powerful nuclear weapons (the hydrogen bomb was first tested in 1951 & '52), jet-powered bombers, and work was proceeding on what would be the first intercontinental ballistic missiles (the Soviet R-7 Semyorka, first launched in 1957), as well as the still-in-operation B-52 Stratofortress long-range strategic bomber (first prototype flight in 1952).

I've seen variants of Clarke's observation such as extrapolations of combat aircraft costs which lead to a single plane being shared amongst the US Air Force, Navy, and Army, with the Marines having dibs every few weeks, something similar.

The criticism isn't entirely fair, as there is an element to which a superior weapon or capability can utterly overwhelm numerically-superior forces, given an equivalent initiative to fight, and military leadership capability. The defence-offence advantage (that is, a defender virtually always has the advantage) means that yes, a technologically inferior force can wear down a superior invader over time, though shear weight of numbers (though often at immense cost), as with China over Japan in WWII (Japan occupied portions of the country but simply lacked the personnel to control all but a small fraction of it), the Vietnam against the French and Americans in Indochina, and Afghanistan against the British, Soviets, and Americans from the 19th through the 21st centuries. But at the same time in an initial assault phase technological supremacy can offer overwhelming advantage, as with the US in both Iraq wars and initially in the Afghan conflict, Nazi Germany against France in WWII (most notably radio-equipped tanks overwhelming the noncommunicative French forces), and presently in Ukraine where more advanced Nato munitions seem to be giving a critical edge over Russian massed forces and dumb munitions, though that's been a relatively closer contest, given that Russian leadership seems to have little concern for its own forces' losses.
Scrum puts "feel good" limits around the unknown qualities of time-to-complete and "divide and conquer"

You still don't really know when it will be ready, but you now have talking points with management about a) whats been done and b) how complex it is. This builds belief: Belief there will be a solution, and Belief you can find it.

Nothing not said better by others here, but I say this as a party who was dragged kicking and screaming into the process to be an agile product manager, hated it, and got out. I totally "get" why people want this. It's very rare to be a Bell Labs, or Xerox Parc, and have pretty much complete freedom to spend budget and deliver an outcome when it's ready.

I also have worked on large s/w projects which cost $16m to fail to work, and $60m in lawsuits out the other side. I know that the alternative (a massive proscriptive playbook of minute details of functions, UML, flowcharts, you-name-it) exists and works, or not (depending on your point of view).

Really? I think scrum was the wrong name. The process itself, is fine. Talking to your co-workers builds a sense of purpose and direction.
I'm also curious if it has anything unsavory to modern sensibility. For a point of reference, "Jump Jim Crow" was written in 1828, but it had yet to become the major hit it was destined to be and wasn't published in sheet form yet. The era of minstrel shows as mainstream entertainment was still a little ways off.
So if they weren't religious nutters why did you all go no-contact? Abuse is the only reason I've commonly heard for no-contact, with addiction and religious expulsion uncommon but present, were 12/13 of these families abusive or addicted? I'm just struggling to understand the relationship between the facts you've stated and the outcomes you've stated, I feel like I'm missing a lot of steps here. For reference, I am also no-contact and most of my friends are no-contact, most due to abuse, but we weren't homeschooled.
> That's interesting to hear, as someone living in a different country I always assume that the reason to homeschool is so you could give your children better education.

The attitude I was raised with is that parents will always have to provide supplemental education but the socialization school provides is much more difficult to replace.
> It's handy for people who want to drink 1-2 glasses of wine a day

In college one year, I had a randomly-assigned roommate who occasionally celebrated "boxed wine night", during which he would attempt to drink an entire box over the course of the night.

This is how I learned that boxed wine is apparently also handy for people who like to drink absurd amounts of cheap wine, since each box is typically equivalent to 4 bottles.

You can probably guess how "boxed wine night" usually ended for him. Even so, his academic grades were excellent, go figure.
Ask HN: What's the current market rate for software engineer after tech winter?
> There's no room for arguing, and there's no in-between — any software whose license doesn't belong to the OSI's list is proprietary software.

There's plenty of room for arguing. The FSF, in fact, approves a few licenses that OSI doesn't.
There are alternatives I listed, the choice is not between "unlimited time off" and "mandatory". "Unlimited time off" would probably stand beneath "use-it-or-lose-it" in my evaluation because with the latter I'd be able to collect my PTO balance upon resignation.

>And without those plans, accrued time off is lucky to hit 2 weeks a year.

I never had less than 20 days (4 weeks) PTO, not counting holidays and Christmas lockdown and since I did not bother to negotiate any special PTO, I believe thousands upon thousands of my coworkers had the same luck.

>So I have to not be sick or have emergencies for 2 years straight to get what is normal in the EU?

I believe if you took a SWE job for what the normal in EU you could have also negotiated 10 weeks of PTO on top of that.

>It's easier to force mandatory vacation than go through all that.

It might be easier that that, whatever that is, but it's not desirable for me.

>Where are you where you can accumulate "months of time off"?

In the last TNC where I worked, I cashed out over two months of PTO (it capped over 40 days, 380 hours or some strange number like that) when I resigned.

>Every plan I've had had max accruals of anywhere from 14-28 days

So? If PTO is so important to you just make it a condition of your employment, it's just money for the employer, take more PTO, take less other comp. It's as same as if it had been made mandatory except people who are not interested in long vacations can have cash instead.
Couple reasons 1) why use seconds when you can just measure a segment of a known distance? 2) pendulums swing faster or slower depending on altitude, 3) Problems with accurate measurement of seconds, swing time etc.
Then the individual goes on the dumber-than-life anti-communist rant. I love how he tries to create a bunker with "if you disagree you're into Scrum".

I dislike Scrum quite a bit, but oh gee ain't that a full plate for Scrum apologists to have a point.
In the city I'm aspiring to buy a house (a.k.a. somewhere near Tokyo), you only need to put the down payment if the construction hasn't finished yet. There will be no mortgage until after the house is ready.

I kind of think this may be a slightly better model in terms of homebuyer protection... (May not sound good for the developer though)
I agree it's rarely "done right", but I've been in career long enough that waterfall was still common early in career and horrible crunch time targeting some date at end of 9-12 months projects was inevitable - Scrum was a total breath of fresh air back in 2005-2006 and saved my sanity.

Basically we'd ask mgmt "what do you want next?" and they had to fuck off for the next 4 weeks while devs, ux, QA worked with no changes in plans until next demo and release. They were responsible for figuring out "when will everything be done?" etc.

I recently left a startup that said they were "doing Scrum" and it was just daily task tracking and pushing devs to overcommit to each sprint - that's not what I consider Scrum.
What I've come to realize, also from living in the US, is that most Americans just don't convert between units. Unless they really have to. That way the issue does't really come up much.

I notice it most when things here by chance are done in metric, but the units still aren't converted.
E.g. I might see something listed at 1000mL, instead of just writing 1L. Or 3500g instead of 3.5kg.

Sometimes a European might say "This way is 600m, but that way is 1.2km", an American would never say "This way is 800 yards, but that way is a mile".
A European might say "I had to carry 4L of water, so my bag got 4kg heavier".
An American might say "My bottle is 24 (fluid) oz, so it's about 24 (weight) oz", but if it's a gallon, they probably just say it weights around a gallon.

All I'm saying is that the conversion problem has turned out to be less of an issue than I imagined.
Simple because Americans don't run around converting their units every sentence.
I'm unsure. I was hoping to encourage a discussion as everything seems to be moving towards being framed over QUIC, like HTTP/3 for example.

Would love to know the pros and cons of BEEP vs. QUIC.
IMO it's because of this default in k8s storage class: https://kubernetes.io/docs/concepts/storage/storage-classes/.... Almost everything in a k8s cluster can be ephemeral... except your data! But they make the defaults insane and it eats a lot of people's lunches. It's honestly very sad. I fortunately haven't "lost" data in 25 years, but I still remember the pain when I made this kind of mistake.
> Our team gets publicly dinged if we "carry over" tickets between sprints

This is not part of scrum
When you're a beginner it's important to know the rules. Then as you develop your style you can decide which rules to break.
That’s always an option I suppose . Canada is huge, and its population isn’t. As a result there are unincorporated billages/whatever you want to call them, where you are on your own for services. I suppose it’s not a bad arrangement if you are up for it
I don't think you got the last sentence right.

I once noticed that people who are used to quickly read tons of texts often don't get the meaning of more winded sentences right. (I assume chatgpt would have the same issue.) But the fault was mine of course, since I did not distinguish between texts written to convey information and "literary" texts written for amusement.

In the age of LLMs it makes you wonder though, if all this writing advice isn't out of date. Concise texts are for AIs, wordy texts are for humans.
And there's the typical internet argument!

"I disagree with you and here's why!"

"I'm sorry that you're personally offended. See, you disagreed with my pure, sweet, logical opinion, which means you must be personally offended, because no REASONABLE person would disagree with me. And because you're offended, you operate on emotions, as opposed to my high-and-mighty self, who operates on pure, sweet logic. Thus I am right and you're a crybaby, because you dared to disagree with what I consider to be my pure, sweet logic."
The name "time capsule" and the formality around them is a 20th century thing, but people have been hiding messages to future people for as long as we've had the ability to do so.
While I do see LLMs helping programmers a lot, I'm not super impressed by seeing it write what looks like a lot of boilerplate. If things become so common that it can be replicated by an LLM, it seems like we need to be abstracting it away.
I’ve developed a more nuanced view on Scrum since working as a contractor for a medium sized software company, but adjacent to their normal dev teams.

I used to have the view that Scrum is a useless batch of meetings, that sucks the life and productivity out of the dev process.

Now, after seeing it from an adjacent (but not subjugated under it) perspective, I think it is a life-sucking batch of meetings that are good for one thing: taking developers who can’t or don’t want to see the overall business/architecture picture and getting useful work out of them.

Most of us here are not in that category. I’d wager a majority of HN readers can’t help but to seek out understanding of the business, where this piece fits, what it interacts with. For us, specifying everything upfront is useless. Estimating stuff is irritating because we need the flexibility to make smart decisions during dev. Retro meetings are lies because we can’t say “stop with all this and let me work”.

But if you’re trying to make a process than can take junior devs (not junior in tenure, but junior in the qualities above) and produce an output that scales almost-kinda linearly with dev count, it sort of works.

I’d argue that you’re way better off hiring 6 devs that can go from business problem -> technical solution in their head, without all the ceremony, instead of 40 devs who can’t and 6 PMs to wrangle them.

But I can also see how a company ends up there - go through a tough hiring year, or even just make a few poor hiring decisions, and now you have people on the team who need handholding and supervision. That’s what scrum is; it feels like micromanagement because it is. It forces junior-performing devs into a productive state - maybe 5% of what you’d get out of a senior-performing dev without scrum, but it’s something non-negative.
I've personally never been in a project where I've felt that the team was doing well thanks to scrum but in spite of it.
Another issue with several .asd files, no readme and not sure how to start. I am interested as this is simpler than the one here. At least the programmer has a test ROM sort of. Just not sure how to start.

As might be noticed, I have spent a few days here to try to sort out a way to start a simple (and possibly) interesting simple lisp project. NES as said in that web page is great. Just no good starting point (or may I say too complete as a starting point) for lisp project.
I guess for (1) I would imagine it was easier for an independent group of scientists to accurately measure a pendulum, than to travel all the way to the north pole in a straight line through Paris.

But I guess they were using the stars or something so maybe it's not as hard as I'd imagine. Also (2) and (3) are great points.
Thanks so much for the link.

My own experience has been similar.

Start with keeping a very flexible core and codebase.. feed it with launched code from a plan that balances bug fixes, progress forward, and customer needs from the business.

This meant having a backlog, and by scoring each item on criticality where 1 was critical and 6 was someday/maybe, and whether it was internal facing, or external facing (customer is aware), you could almost start selecting what was done and ready.

Would love to hear anyone's processes they used that have worked well for them from start to growth.
> Scrum is not for developers; it's another tool for managers to feel they are in control.

Bad managers would certainly like to do this but this is not what scrum is about
Matchbox Educable Noughts And Crosses Engine
Well, 1 glass = 250ml, so 1L is 4 glasses. That's really not a lot.

Milk in bags probably last more than a week (the opening is very small so there's not a lot of air that gets in), but I've never not finished milk in under a week so I can't say.
>I'm sure all their competitors do the same for the same reasons.

Trading firms tend to build a lot of their own tech, but
Jane Street is special in that they build almost everything in house. Ocaml is practically their own language. No other competitor comes close to this level of owning the entire ecosystem, including programming tools.
Velero can be configured to run on a schedule, but the scheduled command was apparently not the exact same command they were using to perform the manual tests - the scheduled job was missing part of the command, basically.
This would also mean they did not have a staging environment for verifying a botched deployment. Very unfortunate and a double disappointment for finding out backups were missing.
agreed, Agile and Scrum are not the same, and if you read person's followup comments, even he says "he believes in Agile" but hates Scrum.

Yeah, most aspects of Agile (iterative development, MVP...) are fantastic and it has made most types of engineering lighter, more team-focused and well more agile.
Gravel is purchased by the yard, not by the cubic inch or mile.
I developed an alternative called “Hot-Potato Agile” while at Google. I got buy-in to try it, but then was laid off in January just before we could start. So if you have a team that likes sprint cadence but hates the scrum busywork and is open to an experiment, let me know! I still want to flesh out this thing’s rough edges.
Prettu much. OF belongs to this list.
I'm not a fan of such relativizations. Today's understanding of just about anything is unimaginably more complete than it was 200 years ago. The amount of thought that tends to go into such projects today puts to shame all that 19th century people did or could have come up with.

When trying to predict how people in 200 years will view today's civilization, looking back 200 years into the past is a poor approach. Just because phlogiston theory was garbage, doesn't mean we should expect our understanding of combustion to turn out to be equally flawed. I've read about modern time capsules containing descriptions in hundreds of different languages, including pictograms and algorithms, instructions for bootstrapping data retrieval devices, earthquake safety taking into account plate tectonics tens of thousands of years into the future etc... Such projects today are most certainly not just putting a bunch of stuff in a closed chamber and leaving future generations to puzzle about why.
Okay so where is all the media blaming the economic issues on US? I sure haven't seen any on TV.
> old

> since 2010

I guess I am getting old, too. I have a server running Arch Linux (same installation but updated and rebooted, though) since early 2011 and I would have not called it old by intuition. I just realized it's over 10 years now and not something like 4 like I was "feeling" still. :(