skysight-inc/HackerNews huggingface dataset:
Uber's last-minute bid to beat gig worker law is latest of many tries
Is eating meat a net harm?
This is all over the place and doesn't really present a coherent argument.

The author complains about developers who "want to show off" and then derides the use of frameworks. But showing off would mean not using off-the-shelf solutions, and instead trying to hand-craft everything.

The author complains about how frameworks bloat the page, but react + react-dom, as of version 16 (the most recent measurement I could quickly Google), weighed in at 109 kb (34.8 kb gzipped). Sure, client-side rendering means you wait for the JS to bootstrap before you get to see content, but React also has good support for doing initial renders server-side.

It feels like the author just spilled out his or her assumptions and prejudices without examining or researching them at all.
I think you've been lucky in where you have worked. You read some of the other responses and it isn't the case at all. I've seen some really tragic examples.

Pivotal has 3 regular meetings: daily morning standup (short), iteration planning (monday), retrospective (friday).

Any new stories during the week that haven't been pointed get pointed in the morning meeting.
I have a feeling however that this is in fact not broken but working exactly as intended. Corporate dark pattern just to gently "discourage" problem customers from contacting them.
'Quasi-programmer'? I don't think elitism helps your point.
Repeated from above:

Pivotal has 3 regular meetings: daily morning standup (short), iteration planning (monday), retrospective (friday).

Any new stories during the week that haven't been pointed get pointed in the morning meeting.
Give Yourself a Natural Breast Lift
> If basic computer operations like loading a webpage took minutes rather than seconds...

Wait, are you implying they don't ? What world do you live in, and how do I join?
I find being transparent with my team makes it a lot easier. There are internal deadlines and external deadlines. Former are internal ones which have no real consequence if missed and just keep a development rhythm (e.g. weekly iteration, monthly release, quarterly roadmap update catchup etc...).

The other type comes from third parties, generally, such as clients or the board. Once you separate these two types of deadlines, I find my engineers more understanding about having to meet external ones whereas blurring internal and external into one "deadline" simply causes people to either burnout or lose faith in management because everything is marked as urgent.
Receiving slow-scan television images from the International Space Station
YouTube promoting [Non-English] adult content disguised as Kids drawing videos
Seconded. It’s a quick read too.

I think Asimov said often people would ask him “What’s that story called where ...” and he’d cut them off and answer “The Last Question”.
Their console APIs already offer the lowlevel control from Vulkan and are much older than Vulkan, so no, it is not from the begining.
all semantics drift
This is probably the most balanced comment about meat-eating I've ever read.

I think the tax thing is key - I eat meat and I fly a lot. I know both of those things contribute to the climate crisis - therefore I'd be completely ok with paying some more money as tax that goes towards offsetting the environmental damage from those activities.

Lots of people think we needs to go back in development of technology and stop enjoying the things humanity has worked for a long time to achieve. Instead we should think about how we can make technology work better together with the environment and enable even more comfort and prosperity. Not force us to go back, rather find ways of moving even further forward.
Not only is this "no code", it is also "no data"! At least data availability statement is now required so we know data is not publicly available...
Auerbach did win the end though, although it took a 1.5-year legal battle and EFF backing.
TikTok claims zero takedown requests from China in first transparency report
> Webdev is a very fad-driven business

I think it is like this because it is kind of awful on so many dimensions, and we have hacked the browser to do all sorts of things. It's kind of amazing, but now we have to deal with it.
It's live and immediate and simultaneous, which you can only get with async or multithreading.

Async Python gives you the ability to set up functions that act upon multiple stdout/stderr streams and process them in real time.
Something from the APL/J/K world would fit in. Is there a proper book?
Igtor
Sounds like every agile team I've ever worked on - sprint and iteration is usually interchangeable.

The problem is that Devs making estimates tends not to be accurate IME. Some stuff is easy to estimate, but adding in new & significant functionality is notoriously usually hideously mis-estimated (either high or low). So much so that the numbers basically b come meaningless and can't be relied upon because every major new thing was a lot easier/a lot harder than expected.

The reaction to this is to split the task up, but this often requires that you do a lot of pre-work-work to architect and design the work so you know how it can be broken up, and that design work needs to be estimated so you are back at square one with wildly inaccurate estimates.
Some species of Eucalyptus I've heard need fire for their seeds to "activate"/germinate. They've also discovered a huge variety of Australian plants in valley's where the fire never reaches (think the Wollemi Pine); where everywhere else is really just eucalyptus. If fire could eventually start in an area you pretty much just have eucalyptus bush everywhere and nothing else.

My non-educated hypotheses is that eucalyptus was a very dangerous weed that uses fire to basically kill everything else around it. It managed to kill via fire every other native Australian plant in the bush expect with the exception of some safe sanctuary spots (close to water, deep valley's where moisture content is higher) many years ago. Some other plants have evolved against this and adapted to fire however (think Australian grass trees).
>Windows does it.

Yeah, didn't say it's impossible. I said it's a tradeoff.

Windows does it and pays for it with slower releases, more engineers, bugs, strange interaction between old and new, several layers of UI and API code for devs to decode and for users to be confused with, less ability to move to new paradigms (why would devs bother if the old work), 2 versions of libs loaded (32/64 bit), and several other ways besides...

E.g. I've stopped using Windows for a decade or so, but I read of the 3 (4?) settings panels it has, the modern, the Vista style, the XP style, and so on, with some options in one, the others in the other (if you click some "advanced" menu, etc).
How do a add FAQ schema to Google search results?
As a developer I'm much less comfortable working with JS frameworks. It seems like each one tries to hijack the JS experience and create its own.

Does anyone have experience writing SPA/PWA without frameworks? I'm interested in the idea of minimal JS even at the cost of productivity.
How do I add author tracking in Google Analytics?
The course has been set, that's the way all banks are headed.

Challenger banks like Revolut, N26, Bunq, ... are all very reliant on smart phone apps. Even if they have web interfaces, you can't log in without authenticating with the app

Tangent: American banks might not be the best example here, given their reliance on ancient tech like signatures, paper checks and magnet strips. But they, too, will move in this direction.
What's funny is I think all of the major game studios that I know of essentially lock game engine per project once they're coding along. It's just expected that you stick with it for the rest of the project. Maybe 1 upgrade mid project. I had heard bungie used to, in the halo days, lock the engine 8-11 months out and the core tech team started working on the next game. The AAA studio I worked for essentially did that 3-6 months out.

But those were 2-3 year game cycles. Maintaining a project would be less fun. But it'd be like choosing to do a rails or react upgrade.
HTTP thesupplementcop com/keto-energy/
Keto Energy
In going keto, I anticipated that my HbA1c should have dropped. This test is a 3-month normal of your blood glucose levels, yet mine demonstrated no change. I accept this affirms my earlier low-carb and generally smart dieting was working superbly of anticipating sugar spikes, and furthermore that I was at that point at my low gauge for HbA1c and couldn't go any lower.These blood tests were done with the fine people at Thriva, who have the mission of enabling anybody to assume responsibility for their wellbeing. They post you a home blood test unit, you send it back and get your outcomes inside hours. Being truly nauseous, my heart was hustling at the idea of giving blood.
http://thesupplementcop.com/keto-energy/
https://www.youtube.com/watch?v=ipp7o1t7BDk&feature=youtu.be
I think you're doing it wrong. It shouldn't be any more complicated than writing events as a producer to a Kafka topic.

Gets more complicated when you add in distributed computing, redundancy etc... However those things are always complicated
In my experience with sprints, I see testing get dropped before stories do. Pointing should factor in testing as part of the score.

TDD/CI/CD is critical and these are part of the culture at Pivotal.
https://en.wikipedia.org/wiki/Proposals_for_the_United_State...
> then you need to be able to point to harms

Right. That’s why I included articles on people being arrested. Being arrested is very much a harm.

Here’s a woman who was arrested for tweeting rap lyrics. https://www.bbc.com/news/uk-england-merseyside-43816921

Do some research on how the law is being used for. On what people are being arrested for. I look forward to your report.

> Your objection here is apparently to either the fact that the law was enforced, or to the specific punishment.

My objection is to the existence of the law. Not only should there have been no punishment but there shouldn’t have been an arrest or even an investigation.
The London Rape Review [pdf]
out of curiosity what value do you see in morning standups? 15 yrs and i still don't see it (i've really tried).
I don't like to rely on my memory either! I forget the names of commands and use tab completion to list them.

You can just type bma[TAB][TAB] and it will list them all.

If you know the type of resource you are working with, you can use TAB completion to see it's commands:

$ stack-
stack-arn stack-exports stack-tag-apply
stack-asg-instances stack-failure stack-tag-delete
stack-asgs stack-instances stack-tags
stack-cancel-update stack-outputs stack-tags-text
stack-create stack-parameters stack-tail
stack-delete stack-recreate stack-template
stack-diff stack-resources stack-update
stack-elbs stack-status stack-validate
stack-events stack-tag
> 9/ We will finally move on from the Baby Boomers dominating the conversation in the US and around the world and Millennials and Gen-Z will be running many institutions by the end of the decade. Age and experience will be less valued by shareholders, voters, and other stakeholders and vision and courage will be valued more

I don't how the first part of his prediction leads to the other. By the time Millennials/Gen Z take control they'll be just as old amd curmudgeonly as the Boomers. All in all the article seems pretty light on justification.
Before the internet, it was a handful of newspapers, radio, and TV stations which where the gatekeepers to public discourse.
Nice privacy policy.
Swift as a C Language REPL
I'm posting this because it's a detailed look at how people who've made an allegation of rape interact with the criminal justice system, and why some of them disengage once they've made a report.
It would be interesting to be able to visualize dependency relationships.

It's easy to see what's blocked, but being able to identify blocking tasks that aren't yet in progress is important.
It does, because it's an outliner with a progress bar and some tagging bolted on top. It does look nice though, in a way non-Emacs users might appreciate. I can entirely imagine myself - from the alternate reality where I didn't know about Org Mode - using this for personal projects.

But enough with the criticism. I like how this looks like a nice, self-contained product. And I love that the author understands that tasks are subdivisible to more than one level. I'm really, really fed up with the usual issue trackers and project management tools we use in this industry - all of them limit your tasks to one, at best two levels.

(I wish someone one day would recognize that tasks don't form trees, but directed graphs; Org Mode, being an outliner, doesn't handle this, but I'm surprised no other tool seems to handle it either.)
Some of worlds most useful and powerful data structures are the projection of an event log. The tables of a RDBMS, the balanced writes of a SSD, and even the classic: double-entry book-keeping.

Even the data stream of a TCP connection is a projection of events, which is why (and how) we can reconstruct them by replaying captured segments.

So just because there are some lousy executions of a general architecture, doesn’t mean we should recoil from the basic idea.

My takeaway is that successful event-sourced structures are crafted for the domain they represent. I’ve developed a couple for my own work, for very specific aspects of an application, and they work well in context.

If your experience has been that a general-purpose ES framework leads to shitty, hard-to-maintain apps, I’d say that’s evidence for the corollary.
I'm shocked it's only 25. I would have expected an order of magnitude more given the number of features and sheer reach of Twitter. That can't possibly be right.

Not sarcasm btw. I think you're underestimating how much work there is.

First, there are a ton of features: lazy-loading tweets, retweet, favorite, lists, all the stuff related to analytics, settings. Simply maintaining that stuff with security updates and bugfixes is a significant commitment.

Then there's accessibility and localization to consider.

Next there's fix and feature experimentation. They probably don't release new features and fixes to everyone at once. Instead they roll them out slowly, or show different versions to different users, compare, analyze and iterate.

Browsers update approximately every 6 weeks, so that's something to keep abreast of. At Twitter's scale, a CSS rendering bug that affects 0.1% of sessions will be seen by hundreds of thousands of users.

And it's not just "a Twitter client". It's THE Twitter client - the canonical one. It has to have higher standards of performance, quality, and reliability than a random Twitter Android or iPhone app.
Python has something similar, you can cancel() any async task and it will throw a CancelledError inside the ongoing operation.

I'm not sure how it would solve backpressure though, because canceling a task is normally done by the caller, while backpressure comes from the other direction of the call stack.
You just need a contract detailing the conditions of what happens in case of dispute up front.
I like the fact that people are starting to get fed up with slow software. Maybe this will increase demand big enough and we can start seeing new performant software popup
Agreed. Even if you are better served taking three days off and digging into blog posts, a small project, etc, on your own, how often do you do so? Do you feel like your employer would be cool with that?

One way I've seen this done is with hackathons, but they're uncommon enough to be notable whenever an employer supports them.
Out of curiosity, how valuable are these three meetings in a typical week? What do you get out of each of them as a developer?

I've worked at a few places that follow more or less the same practice and I've found that the planning meeting is hugely valuable but that standups and retrospectives are a waste of time more often than not.
My take on this article is it doesn't worth implementing your own spinlock. The OS can take advantage of their implementation details while you can't portably implement it. The OS implementation changes in the future or varies.

Even if you use _mm_pause() to let CPU know it's doing spinlock, for the eye of the OS, it still looks like a busy thread, it can't be distinguished from non-spinlock computation heavy thread.
If the story estimation isn't accurate, then the velocity goes haywire and this shows up in the reporting in Pivotal Tracker.

So like you said, devs learn to get better at forcing the PM's to split the stories into smaller chunks. Smaller stories are almost always easier to accurately point since it is always 2 (1 point for the story, 1 point for testing).

The numbers are not meaningless though. That is why velocity is an average of 3 weeks. A single week doesn't blow things out of the water and if it is a new project, the expectation is that we won't know where we are at all those first 3 weeks. It gives a built in ramp-up period for the project.

Agreed, the PM's role is SUPER important. For this reason, at Pivotal the PM's usually have a developer background.
Eicar Test QR
the greatest concern to centralized systems like Signal is not ease of use, its censorship and de-platforming. In China, Signal servers are outright banned. No servers, no secure communications.

In the United states players like Cloudflare have demonstrated twice the can and will de-platform entire communities for controversial speech. senator Joseph Lieberman, with a single phonecall, had wikileaks immediately deplatformed from AWS. All it takes is a violation of a term of service and that service vanishes.

Increasingly Moxie seems to value the developer experience over any project goal for Signal. its still AWS, it still depends greatly on google services and play store for distribution. Begrudgingly hes added a secret-ish link on the signal website to download the APK directly, but he still ardently refuses to publish the package on FDroid.

and as for his "federated services are stuck in time" argument, these are glaring architectural issues that have plagued his application for five years. The only tangible evolution of signal in the past year has been new cat and dog stickers that no one asked for.
Being wildly expensive and vulnerable does not necessarily mean it can't provide $13B of value
I do think nuclear will have a resurgence. You don't have to make nuclear as safe as clear air to use, only reasonably safe with a plan to handle the waste. Nuclear is already safer than coal in terms of people killed by power generation.

Finland is building the world's first long term storage depot for nuclear waste and I think the same could be done in many other places.

Plus, all the push for nuclear is for new nuclear with better efficiency in the fuel used and passive safety futures. I don't think that a significant part of the grid will be powered by nuclear in 2030, but the newer models should be coming online by then.
This article lost me at the notion of using Brave.
I worked as an AWS instructor (not for AWS directly, for one of the big technology training companies) a few years ago. Some of the other instructors had been to numerous re:invents and said that the two real reasons to go were:

* Networking with other attendees

* Getting to meet face to face with AWS employees
I mean that conclusion is true of basically every complex system. That's the whole point of hacking together an MVP first, to see what really matters.

However it's silly IMO to use that criteria as an example of why not to do event driven architecture. It's well understood in the eda community that you generally don't start with streaming systems unless you know you need it from the start.
Star Trek thought differently:

https://en.wikipedia.org/wiki/A_Taste_of_Armageddon

Worth a watch on this subject.
I agree that the whole typical 'what did you do yesterday' is indeed lacking value.

The standups are mostly just pointing the stories that need pointing, covering any questions and picking the pairs for the days work (pivotal is 100% pair programming). The meetings can be done within 5-15 minutes at most.

I'm currently living at a yoga retreat center in the mountains of Vietnam. I can see from the practice that the first few minutes of silence is good to clear the mind. I think having standups is a similar good way to start the day with a positive attitude.
I love Trello so I checked it out..
Seems like a really good idea.
I would use it, but I would worry about losing all my shit if it moved to a payed model.. Maybe keep the existing features free always, and only charge for future features?

Also visually, its white with lots of almost white / grey stuff.. Its really hard to see anything!
relatively covert backdoor
The problem with little upfront planning is the team might spend too much time on certain features in the beginning and get crunches at the end to deliver an MVP experience at the agreed upon deadline. By signaling early that a deadline may be missed, there is an opportunity to make course corrections in the spec or shift folks from other projects to deliver a higher quality experience at the agreed upon deadline.
You might be interested in Software Craftsmanship [0] manifesto. There are many communities and initiatives around the world gathering folks with the interest in producing high-quality software. From the few of the folks I have been working with that are involved in SC, I can definitely recommend the movement and so I'm also exploring options in joining some local meet-ups and/or events.

[0] http://manifesto.softwarecraftsmanship.org/
I just asked the same thing because I've had that experience too. I'm curious: are you usually working on things that require close collaboration between team members?

My hunch is that standups are pretty useless on teams where each developer is working on an independent change where there isn't much opportunity to get blocked by teammates aside from waiting for code reviews and the like. That's most of the teams I've worked on, and the standups inevitably turn into a verbal form of, "Hey manager, here's my status report for the day even though you already know all this because I've already said it in Slack," because you have nothing to ask of the other people on the team but you're required to say something every day.
They have no case: https://www.youtube.com/watch?v=5lde-iLJHV4

Warning: he reads nearly the whole thing over 2hours, skip the first minute.
Show HN: Xroom.app – Conference Rooms on Steroids
I mentioned it because I used to assume that serious degradation is just something batteries do, but I learned that this is wrong and proper battery management all but eliminates the problem.
It's literally the same party. Policy has evolved for this dramatically different world, but its ideological foundations are still closer to its heritage than any real alternative.
Upon expanding the answer, this is the explanation I saw.

"The National Union Party was the temporary name used by the Republican Party for the national ticket in the 1864 presidential election that was held during the Civil War."

Since Lincoln's final election victory as President was under their ticket, it's not a crazy answer to give. It's not the answer one expects (I had never heard of it until now) but it seems to be technically correct.

https://en.wikipedia.org/wiki/National_Union_Party_(United_S...
Upterm: Secure Terminal Sharing
Show HN: Watch the endless stream of handpicked tech product videos
democracy with free speech fails in special circumstances. it needs an authoritarian component to prevent more authoritarian form of governments from taking over.