skysight-inc/HackerNews huggingface dataset:
Scrum has prescriptive method of who is supposed to gather requirements, the meeting for requirements gathering, estimation for "understanding of requirements", and demo... well for demo'ing the feature back to "the powers that be".

Kanban doesn't prescribe any stakeholder methodology. It's not that it's not important, it's just up to the organization.

This is definitely a point of contention in Scrum because "oh this is so slow", "there are too many stakeholders", "why do we have to do it this way".

I'm at the belief - some way is better than no way. If you don't like Scrum, cool! Go build your own, but if you don't mind it, Scrum is good-enough^tm.
the problem with this approach is that humans suck and this is an invitation for trolls to upload your code to github. i don't even know how you're supposed to solve this.

you could proactively scan github for your code and try to get them to purge it if you find it i suppose, if that would remove your code from copilot. but even that is not a great solution because you would need to prove you're the actual author, and github would probably need to be involved in building a mechanism to do so, but they don't give a shit.

i think the reality is the LLMs have eroded copyright protections and trying to fight it isn't likely to pay off
You haven't asked duplicate duplicate or expected the people at SO to serve you.

Try asking a question along the lines of "why does this happen? see screenshot for details" with a text-only screenshot that uses three-point text as viewed by someone who matters. You'll have a different experience. Or try asking a question that's already well answered, and the answer could be found by searching for the headline of your new question.
Humans don't learn an algorithm by memorizing a particular implementation character by character.
Humans are intentionally loading up giant sets of curated data for training, purposes, into a super computer to produce a model which is an black box and have provided zero attribution or credit to those who made this work possible. Humans are tuning these models to produce the results you see.

In the case of ChatGPT-x, Open AI company which is disguised as a not for profit with a goal of producing ever more powerful models that may eventually be capable of replacing you at work while seemingly not having any plan to give back to those who’s work was used to make them insane amounts of money.

They haven’t even given back any of their research. So it’s ok to take everyone’s open source work and not give back is it ?

This isn’t some cute little robot who wakes up in the morning and decided it wants to be a coder. This is a multi-national company who has created the narrative you’re repeating. They know exactly what they’re doing.
Sounds like OP wanted a laptop. He has one. And his example showing that his notes are boring looking as compared to the notes shown in Apple's video, is such a defeatist attitude.
> Seems pretty factual to me.

But the instances where this happened during the 80s, Crimean leadership working to split from Ukraine are nowhere to be found.

Now, did they happen? How? That's my point, it's not easy to find anymore, unless one at least remembers the exact page and can scroll the history to the point this information was still present.

I remember reading them about those in February 2014 when I wanted to understand what was happening better, and I remember myself forming the opinion that maybe Crimeans didn't really want to be part of Ukraine from already quite some time.

But if a user reads it now, the overall narrative is much milder. Another person may form a different opinion.

Thus my point that edit wars can influence lots of people thinking.
IMHO this very discussion factors in whether you'll want a PHP stack or not.

If you're looking for pragmatic devs that don't care much about the trends, the community or peers' general opinion about a technology, going with PHP will get you this type in spades. Especially if you're looking for experienced engineers.

If you want devs that care about thoughtful designs, elegant solutions and want to enjoy the community, it will be a lot more difficult (not impossible, but it's an uphill battle)

And this has little to do with PHP's viability per se, there's just so much baggage that most devs will self select in one side or another. A language's base design philosophy matters, and it's always better to chose a stack that matches your own philosophy.
Self-hosted Gitea.
This is actually a great suggestion I never thought about, but most users will never read it and assume the michael scott way.
Bingo! God it's so frustrating when people mix the two up and end up thinking the whole world agrees with their conclusion that you can get a better image from less data, all else being equal. People still argue this all the time and it's absolutely maddening.
A human who learns to copy code letter for letter does just that: copies code. Same with an AI.

The interesting debate should be what happens in the gray area, when you read a lot of code and learns patterns and ideas.
Kanban means constrained capacity. You decide on an upper bound on how many things are allowed to be in progress at any one time and if you need to start work on something new you finish things that are in flight to provide headroom to do that. The board is just a device to ensure good communication so everyone in the team has shared state.
Neither does copilot.
That does feel like an overly simplistic argument. Once again, lots and lots of things feed cancer, it's not as simple as that. There's also a big 'might' clause, which means it's something that's going to take time to understand. For example, IIRC, the role that NR might play in cancers is that it's a very accessible food source for them. However, compared to other factors, this might fade into the woodwork, especially if for example it's used as part of a protocol that lowers the chance of cancer (or at the very least, all-cause mortality) longer term. Ideally, at least.

Maybe an analogy to communicate the concept is that it is like putting a car up on jacks and taking out parts to repair another part. It's possible that it is not where you are long-term, or ideal to do extremely frequently, but it's important to keep the thing maintained and running.

That said, I agree very much on your last sentence as one of the best "simple" routines to get bang for the buck. My thoughts would be weight lifting specifically, chamomile tea at night (apigenin is something else), as well as some broccoli sprouts for NRF2 in there. Other than that I think that's probably the index fund-like strategy to longevity, so we're definitely on the same page there. :D :thumbsup:
Sprints and timeboxing more generally is not about enforcing deadlines. That's such a common misconception and I wish it would die.

Timeboxing is about committing only a small amount of time and money at a time, so you can choose to double down on winners and stop investing in losers, rather than suddenly finding yourself having sunk 3 months of time into something that turns out wasn't that good after all.

The question is not "How much can we definitely complete in two weeks?"; it's "What things are promising enough that we are willing to dump two weeks into them, with no promise of ever making a profit?"

If one month counts as a small amount of time and money for your organisation, then you're doing it right!
My experience is the opposite.

In ChatGPT i actually ask questions, get answer, and use its response to either refine my questions or look up documentation.

Since I know that ChatGPT can't really code, I use its responses as a hint. I leaned a lot when using it to explore the capabilities of languages and libraries I'm not that familiar with.

On SO, the opposite happens. I seldom ask questions, since the site has a reputation of being hostile. I look for previous answers and just try whatever answer I found on my code. If it doesn't work, I try looking for another answer, rinse and repeat.
There are people who do it...
I personally know a guy whit photographic memory
That's a very refreshing attitude. I had heard of Lunar but was reluctant to try it. Lately my policy has been "the less software the better" precisely because of how predatory most software is.

But not your software, it seems!

Your privacy policy has made me think it would be a good idea to try and probably buy your app if it works for me.

Thanks for being one of the good ones!
On the other hand, it requires only one determined person out of hundreds of thousands who, for whatever reason (trolling, principled open source maximalist, AI researcher, code archiver, etc), decides to mirror all code marked with this badge to GitHub.
That sounds sensible. Soo... How do you get your managers to this insight? In my company each team uses scrum and I think no one is really happy with it. Mine certainly isn't. I'm not even talking about the engineers: at least from my point of view everyone involved suffers from it. But I have the impression we lack responsibility for such decisions. Oh well, I think I'm just venting now :)
The problem is not that Copilot produces code that is "inspired" by GPL code, it's that it spits out GPL code verbatim.

> This can lead to some copylefted code being included in proprietary or simply not copylefted projects. And this is a violation of both the license terms and the intellectual proprety of the authors of the original code.

If the author was a human, this would be a clear violation of the licence. The AI case is no different as far as I can tell.

Edit: I'm definitely no expert on copyright law for code but my personal rule is don't include someone's copyrighted code if it can by unambiguously identified as their original work. For very small lines of code, it would be hard to identify any single original author. When it comes to whole functions it gets easier to say "actually this came from this GPL licensed project". Since Copilot can produce whole functions verbatim, this is the basis on which I state that it "would be a clear violation" of the licence. If Copilot chooses to be less concerned about violating the law than I am then that's a problem. But maybe I'm overly cautious and the GPL is more lenient than this in reality.
I use a self hosted gitea instance. Haven't had any issues with it, i can highly recommend it. Not super useful if you want contributions though xD
Scrum is kanban plus bureaucracy. The real underlying challenge is keeping bureaucracy low as an organisation grows.
Street Fighter II, paper trails (2021)
High-end plastics are intersting category just because they can be so exotic. You don't really see or hear about things made of stuff like Celazole etc so it is difficult to get a grasp how they compare to more commonplace materials
sourcehut - the hacker's forge
A key difference is that a company is making a proprietary paid product out of the learnings from your code. This has nothing to do with open source.

If the data could only used by other open source projects, e.g. open source AI models, I don't think anyone would complain.

You could argue "well, but anyone can use the code on Github" and while that's technically true, it's obvious that with both Github and OpenAI being owned by Microsoft, OpenAI gets a huge competitive advantage due to internal partnerships.
Could be. Longecity I've found to be an odd mix of people who are rather combative about whether things work or not and who are way too in-depth (in a good way) about their personal experiences about what worked or not.

At the very least, it's intriguing and out of all of the thousands of pages of medical literature I've read over the past half decade or so it's been one of the more interesting sagas to follow.
What you can do is quite limited. You're restricted to some preset eBPF program types, and each program type has a restricted set of operations it can perform (eBPF helper methods). So arbitrary modifications, absolutely not without adding a helper method and/or program type for this purpose. More program types and helper methods are being added all the time but overall it's pretty limited in use cases and operations.

If you want full control then kernel module is the way to go, but this doesn't have the same security and stability guarantees.
RasaGPT: First headless LLM chatbot built on top of Rasa, Langchain and FastAPI
Unfortunately there were not a whole lot of end-to-end examples of integrating Rasa with OpenAI nor functional boilerplates on github so I put a working prototype together in a few days and thus RasaGPT was bron.

RasaGPT is a python-based boilerplate and reference implementation of Rasa and Telegram utilizing an LLM library like Langchain for indexing, retrieval and context injection. FastAPI end-points are made available for you to build your application on top of. Features include:

- Automated hand-off to human if queries are out of bounds
- "Training" pipeline done via API
- Multi-tenant support
- Generate category labels from questions
- Works right out of the box with docker-compose
- Ngrok reverse tunnel and dummy data included
- Multiple use cases and a great starting point

Hope you like it, more @ rasagpt.dev
i'm arguing against the idea of achieving "immortality", not against anti-aging treatments. slowing the progression of aging but maintaining the same trajectory of life and death is a desirable thing. trying to avoid death is not.
This can also help to some extent: https://developer.mozilla.org/en-US/docs/Web/Security/Subres...
You can have a Vulkan driver that only exposes a video decoder queue and no raster/compute/copy queues, not a problem.
... until for profiting goes against developing a good service.

> I think github, after stackoverflow, is the best thing that happened to developers.

I don't think github is bad tooling (there are worse), but the best thing for developer?
I don't see anything on github that is greatly better than what we have in other services.
Even modified sensors (removal of the IR sensor filter) barely see above 1000nm, which not anywhere close to what you need for thermal imaging

> it would seem a bit weird to me if they just happened to be restricted to exactly the same part of the spectrum as our eyes as a hardware limitation.

That's a feature, for the leica m8 sensor "sees" UV and IR, as a result you need to use a UV/IR filter on your lens otherwise you get weird colors and blurrier images (since UV/visible light/IR all focus at different plans)

https://www.35mmc.com/14/02/2016/leica-m8-infrared-cut-filte...
>As soon as the average gaming PC... has the power of a 4080/4090

So, a decade from now

>As soon as the average gaming PC and console has the power of a 4080/4090

Ah, more like 15 years.

Then, shortly after that, the mainstream won't be client compute, but cloud compute and game streaming. Although, I wonder if 20 years to build out full fiber for almost everyone in rich countries is realistic. I might be over optimistic here, actually. Maybe 30 for mainstream game streaming.
You've clearly used a throwaway just to be contrarian, but have you considered not posting at all if it adds no value to the discussion?
:-P ChatGPT?
I think git itself is better, personally.
The most evil was Visual Basic where you could configure the default starting index (OPTION BASE 1), leading to weird bugs when multiple people worked on the same codebase.
> surely you are important to yourself.

Depends on how depressed a person is I guess. ;)
To be fair, when a programmer learns from publicly available but not public-domain code, and then applies the ideas, patterns, idioms and common implementations in their daily job as a software developer, the result is very much a "commercial product" (the dev company, the programmer themselves if a freelancer) learning from someone else's work and ignoring all the licenses.

The only leap here is the fact that the programmer has outsourced the learning to a tool that does it for them, which they then use to do their job, just as before.
Bit of a false equation to act as though a massive computer system is the same as any individual.

People put code on github to be read by anyone (assuming a public repository), but the terms of use are governed by the license. Now you've got a system that ignores the license and scrapes your data for its own purpose. You can pretend it's human but the capabilities aren't the same. (Humans generally don't spend a month being trained on all github code and remember large chunks of it for regurgitation at superhuman speeds, nor can they be horizontally scaled after learning.)

You can still be of the opinion that this is fine, and I may or may not be fine with it as well, I just don't think the stated reason holds up to logic and other opinions ought to "baffle" you
> Scrum is meant to protect the team from changing requirements mid-work

Do I need this protection? Why cannot I protect myself? Do I want this type of protection? Especially if it comes with all the negative downsides of Scrum.

Scrum is based on the imho often wrong assumption that a team needs "protection" of some sort. If your team consists of 16 year old youngsters only this might be true and this type of protection might be useful.

All this "protect the team from changing requirements mid-work" is nonsensical anyway, because no _really_ valuable work is done in 2 weeks. If the requirements _really_ changes you have to throw away the code for the old requirement. You can throw away 2 weeks of coding or 2 days. I'm pissed off more by 2 weeks of dead code. If the requirements adopts a bit its better to adopt early. And change in focus and priorities (which is _not_ a changing requirement): I'm happy to do so if I'm convinced it's for the good of the company and I'm happy to say "Sorry, this will have to wait until I'm done with what I'm currently doing. Please come back next Tuesday.".
> If the author was a human, this would be a clear violation of the licence. The AI case is no different as far as I can tell.

We aren't talking verbatim generation of entire packages of code here, are we? Code snippets are surely covered under fair use?
Imagine if folks got royalties on commits, or the language model was required to be open as well.
It would greatly improve by some text revisions: "my code", "We", on a generic page without clear authorship or object, on a dedicated subdomain, on a hosting domain, without a signature or contact or kind of option for a webring.

It took me some time to get that this is a generic call (to be followed and reused), still with no clear ownership, rather than a specific claim to a specific code/project (or is it?).
Potayto potahto. We all know there's a difference between training a machine learning model and learning a skill as a human being. Even if you can trick yourself into believing AI is just kinda like how human brains work maybe, the obvious difference is that you can't just grow yourself a second brain and treat it like a slave whereas having more money means you can build a bigger and better AI and throw more resources at operating it.

Intellectual property is a nebulous concept to begin with, if you really try to understand it. There's a reason copyright claim systems like those at YouTube don't really concern themselves with ownership (that's what DMCA claims are for) but instead with the arbitrary terms of service that don't require you to have a degree in order to determine the boundaries of "fair use" (even if it mimics legal language to dictate these terms and their exemptions).

The problem isn't AI. The problem is property. Ever since Enclosure we've been trying to dull the edges of property rights to make sure people can actually still survive despite them. At some point you have to ask yourself if maybe the problem isn't how sharp the blade you're cutting yourself is but whether you should instead stop cutting. We can have "free culture" but then we can't have private property.
Could a human also accidentally spit out the exact code while having it just learned and not memorized in good faith?

I guess the likelihood decreases as the code length increases but the likelihood also increases the more constraints on parameters such as code style, code uniformity etc you pose.
>Time is the great equalizer, and the well to do's should not be able to purchase more.

The entire medical (and dental) profession is all about keeping you from dying when you're "supposed to". You're supposed to die in your teenage years of a tooth infection, or in your 30s or 40s of cancer, or any random age of an injury.

People in rich countries live much longer (and healthier) than people in poor countries because of access to modern medicine.

So apparently you think people shouldn't have access to any medical services?
A bird lover with the name "Timothy Wing" . That just made my day.
How about:

* Acquire treasure in dubious circumstances ("jury heard that Pilling, from Rossendale, Lancashire, was in possession of the coins knowing they should have been declared. Pilling has never disclosed the full identity of the person he acquired them from. Pilling recruited Best, of Bishop Auckland, County Durham, to try to sell the coins.")

* Spend years selling the treasure in a manner that makes it clear you understand that it's a crime ("Best, who sent an email which read: “They are a hoard as you know they are this can cause me problems all you had to do was say you didn’t want them and that was the end of it.”)

* Go to jail after remaining uncooperative and failing to provide leads that could recover more of the treasure
A licensor cannot predict the future. When the GPL was written decades ago, nobody predicted that BigTech would start using it on their servers to offer it as "services", and claim that they didn't need to distribute the source code of the customisations they made because they were (technically) not distributing the software itself but only running it on their servers. Anyone who understood the intent and philosophy of the GPL license understood this as a bogus and unethical argument. But it was believed to be legally tenable (1). So the AGPL license was created to counter this move and preserve the original philosophy of the GPL that users of a software should have access to the source code.

(1) Though I don't know if this has been actually tested in court - courts in India have more freedom to broadly interpret social contracts like the GPL, unlike the US courts, and a positive outcome in favour of upholding the license even in such cases could be possible).
Gird Up Your Loins
i agree with everything you said. what i don't agree with is that you can prove by induction that you want to live for eternity.
> I don’t know anyone who would recommend Intel.

I'd recommend them to some friends, and actually a colleague of mine got the A770 and is very happy with that (besides the relatively high idle power consumption).

In fact, if you want a lot of VRAM for relatively cheap, the A770 is your best choice, e.g., compare a list of GPUs with 16 GB or more video memory, sorted ascending by price here in Austria (includes German merchants):

https://geizhals.at/?cat=gra16_512&xf=132_16384&sort=p#produ...

Cheapest is the Intel A770 -> 379 € (= 315.83 € without VAT)
The cheapest after that is the RX 6800 -> 527€ (439.16 € w/o VAT)
The cheapest that actually can also do AV1 encoding is the RX 7900 XT -> 846 € (705 € w/o VAT)

Sure, the RX 6800 packs quite a bit of additional performance (but not all features the Intel Arc's got, like AV1 encoding), but 150€ more might make it unaffordable for quite a few people, and depending on what they do with the card the A770 can be enough for a lot of midrange games (or AAA on midrange resolution/details), video processing, rendering, ...

tldr; while not a hard recommendation for all general cases, the Arc series def. has its use, especially on lower budget and especially for use cases that do well with lots of VRAM or AV1 encoding/decoding for a relative low price.