skysight-inc/HackerNews huggingface dataset:
I am on the other side of low code, building the builders for the most part, here is what I see.

Low code is very easy to sell. All you have to do is make a boogie man out of the IT department, and play on existing frustrations. Then play a demo where a sign up form is made in ten minutes and say your IT department would have taken 3 months. You just make sure to walk the happy path during the demo and don’t stress the tool.

Many things could be low code. Why do you need a developer for a sign up form if you are just making an API call in the end? Wiring up a form shouldn’t take html, js, and a serverside language.

On the flip side, don’t put your core business logic in low code. Low code builders assume anything complex will be offloaded to a specialized system. The best ones provide escape hatches by calling remote APIs or calling a code module.

Low code gets sold to smaller customers because it’s touted as a developer replacement. But really it’s most powerful in larger enterprises where individual teams may have technical people who have business knowledge but not much much IT power. It’s easy to get them to configure something in a SaaS they already use, than get a custom solution from IT. Also low code often comes with guardrails and permission sets tied to existing users.

I see low code as a tech equivalent of the last mile problem in logistics. It addresses a large number of concerns with simple tools, but doesn’t scale well and needs to work in tandem with a stronger central system. End to end low code is a trap, but low code at the fringes is a multiplier.
It's not exactly a secret. The US dollar's proliferation is an extremely good thing to happen in the world - our modern banking system is one of our greatest inventions.
Frameworks at all levels of _aaS are great, given the stipulation that your greenfield requirements are completely boring.

This falls apart when:

* legacy systems/data must be integrated

* the requirements get interesting

There is just no substitute for a good working understanding of the tools, and that means staff that can go past the low-code facade when needful.
> culture is a communal property

Public domain / communal property is also part of copyright, so it's not as if this is some forgotten concept that needs to be restored to the discourse.

Georgism is underconsidered, though.

> By focusing solely on the legal implications and ignoring the historical context of cultural storytelling

The legal implications are human implications and as much a part of culture as anything else. They have to do with what's fair and how rewards for effort are recognized and distributed. Formalizing this is less important in cultures that aren't oriented around market economies, which seems to be what much of this "rich tapestry of folklore" discourse wants to evoke and have us hearken back to, but that doesn't describe any society that's figuring out how to handle AI.

> we might actually limit the tools of cultural expression to comply with some weird outdated copyright thing is just...bonkers.

What's bonkers is the life in the literally backwards idea copyright is (or should be) mooted or outdated by novel reproduction capabilities.

Copyright became compelling because of novel reproduction capabilities.

The specific capabilities at the time were industrialized printing. People apparently much smarter than the typical software professional realized that meant some badly aligned incentives between (a) those holding these new reproduction capabilities and (b) those who created the works on which the value of those new reproduction capabilities relied. The heart of the copyright bargain is in aligning those incentives.

Specific novel reproduction techniques can change the details of what's prohibited or restricted or remitted and how and on what basis and powers/limits of enforcement, etc etc. But the they don't change the wisdom in the bargain. The only thing that would change that is a better way of organizing and rewarding the productive capacity of society.
Oh, sweet. That's going to make the branch I'm working on right this minute easier to deal with.
Aren't there apps that just show the embedded text inside a QR instead of just opening the URL in a browser?
Sure but the quantity that’s important is your sampling accuracy. Even on a visually smooth beach there is enough variation for that to significantly impact the results. This closely relates to numerical integration where often you’re dealing with fixed sized steps and for example can simulate significantly stiffer materials with a smaller timestep.
This is described in Annex IV, V and VI [1]. You must do a conformity assessment and provide a declaration of conformity. For non-critical software you can do the assessment yourself see the first five points in Annex VI.
The only thing that maybe requires a bit of effort is that you must write some technical documentation including a cybersecurity risk assessment during the assessment if you have not already done so. For critical software the process is of course a bit more involved because it requires certification by a "notified body".

[1] https://eur-lex.europa.eu/resource.html?uri=cellar:864f472b-...
There are plenty of federal agencies that are underfunded or being tacitly defunded, DHS is absolutely not one of them.
I like the idea, but got this when I tried to run it on my Mac:

> lips
node:internal/modules/esm/resolve:853
throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
Artificial Intelligence – 60 Minutes [video]
Covid 5.0
What kind of projects doesn't need all those things, but yet is still too complex to just do in LibrePCB? To me the nicer and less keyboard driven UI(last I checked, haven't tried KiCAD in years) makes Libre worth it.
https://archive.ph/hd08K
Surprised there's not more Lex Fridman recommendations. This past year I really enjoyed his discussions with Roger Penrose, Stephen Wolfram, Sam Altman, John Carmack, Sam Harris, Jordan Peterson.. but if I had to pick one it would be either Edward Frenkel or Joscha Bach.
Hey,

Every testimonial is real.

Not every testimonial is from Twitter.

Yoni's is from WhatsApp.
James' is from Facebook Messenger.

A bunch of the others are from the Product Hunt launch:
https://www.producthunt.com/posts/inbox-zero-2

The images/names for some aren't for privacy reasons. Although they'd probably be okay with me replacing those with their real names/images too.
As far as I can remember, Amazon never had perks for employees. Except for free coffee and tea in the kitchens. That's it.

I remember back in 2002 (?) when the 2-pizza team idea was introduced. My manager said he would find out how we could expense the pizza. It turns out that the pizza was merely theoretical: the team should be sized so that, if there were pizza, then 2 pizzas would be enough for the team. But that doesn't mean that pizza would ever be ordered or expensed.
Give evidence.
OpenAI's Annualized Revenue Now Tops $1.6B
I use n8n.io hosted locally to abstract away authentication when building complex api integration mvps that I use to show as possible and working, and then that gets sent to engineering to convert to something that follows better best practices.
> I suspect you’re mistaking not wanting/being able to speak English for not wanting to interact with non-Japanese people.

Language doesn't have to do anything with it, it's more base than that. On a crowded subway for example, Japanese people won't want to sit near a white person or might get up and move if you sit near them.
> "It's already happening, so give up on it." I'm sure it works out great for taking action and solving problems.

It's an observation & prediction, not a problem solving attempt...
As mentioned:

> The result will be me rolling a new account (against site guidelines), as I have no other privacy preserving way of handling the issue.

I intentionally stay anon online - it's how I was raised and how I think everyone should be. All of my various accounts have sprinkles of mistruths - nothing important enough to impact the discussion, but enough to keep it difficult to link them. I doubt dang (with good reason) would accept an email from an obviously burner address - what would be the point?

And "behaving" is the complex part. As I don't know what I was invisibly banhammered for, I'm unsure what needs correcting here.
My first hobby project was a yo momma joke spammer for AoL in Visual Basic 3.0. Forgive me I was only 14. The VB chatroom on AOL was my teacher.
Yes, it's inconsistent with Perl. But there are many things in ripgrep's default regex engine that are inconsistent with Perl, including the fact that all patterns are guaranteed to finish a search in linear time with respect to the haystack. (So no look-around or back-references are supported.) It is a non-goal of ripgrep to be consistent with Perl. Thankfully, if you want that, then you can get pretty close by passing the -P/--pcre2 flag.

With that said, I do like Perl's philosophy here. And it was my philosophy too up until recently. I decided to make an exception for \< and \> given their prevalence.

It was also only relatively recently that I made it possible for superfluous escapes to exist. Prior to ripgrep 14, unrecognized escapes were forbidden:

$ echo '@' | rg-13.0.0 '\@'
regex parse error:
\@
^^
error: unrecognized escape sequence
$ echo '@' | rg '\@'
@

I had done it this way to make it possible to add new escape sequences in a semver compatible release. But in reality, if I were to ever add new escape sequences, it use one of the ascii alpha-numeric characters, as Perl does. So I decided it was okay to forever and always give up the ability to make, e.g., `\@` mean something other than just matching a literal `@`.

`\<` and `\>` are forever and always the lone exceptions to this. It is perhaps a trap for beginners, but there are many traps in regexes, and this seemed worth it.

Note that `\b{start}` and `\b{end}` also exist and are aliases for `\<` and `\>`. The more niche `\b{start-half}` and `\b{end-half}` also exist, and those are what are used to implement the -w/--word-regexp flag. (Their semantics match GNU grep's -w/--word-regexp.) For example, `\b-2\b` will not match in `foo -2 bar` since `-` is not a word character and `\b` demands `\w` on one side and `\W` on the other. However, `rg -w -e -2` will match `-2` in `foo -2 bar`:

$ echo 'foo -2 bar' | rg -w -e '\b-2\b'
$ echo 'foo -2 bar' | rg -w -e -2
foo -2 bar
then the wood will compost and turn back into CO2. at least that is how I undersand the process.
Are you checking every token and cookie yourself to make sure they haven't been hijacked?
BYD in Japan? November figure for all BYD was 166. In contrast, Toyota sold about 100 cars short of 17k Yaris, in just Japan in that name and the month alone. Sub 35k is as solved as any cost of market entry problems are.
Hope this clears it up:
https://news.ycombinator.com/item?id=38820176
This has been an essential tool for me over the years as a working "data scientist".

Let's say you've been working on an "algorithm", which is a combination of cleverly-crafted SQL to fetch the right data, some ad-hoc data processing code in Python, getting predictions from a model, and some additional mathy stuff to translate the model prediction into something useful. You probably built it interactively in a REPL or notebook environment. You might have some ad-hoc assertions scattered across your scripts, but nothing resembling a test suite.

That's just how things go, and if you did it differently you'd probably never get your work done. But now you have a problem: you have what you believe is a mostly-working/mostly-correct implementation, which you built incrementally and interactively, but now needs to be put into production. Without any real tests, your script has immediately become "legacy code": https://understandlegacycode.com/blog/what-is-legacy-code-is.... If things went well, you had time to extract some common utility functions and write unit tests for them, but you probably don't have more than that.

So now what do you do? You want to refactor it into testable units, so you can build out a proper test suite. But you can't refactor code without tests, lest you risk breaking something. You did extensive manual checking and validation of your outputs, but you can't keep doing that over and over.

In this case, the best option that I've found is to do pretty much what Fowler is advocating for here. Extract a set of known inputs that don't take too long to run through the algorithm, and save their known-valid (or known-close-enough-to-valid) outputs. Then, piece by piece, start refactoring, re-running at each stage. If the outputs differ by more than floating-point roundoff error, you've either found a bug in your original implementation, or you introduced a bug in your refactor. Once you're sure that your refactor is OK, you can "lock in" the changes by adding new tests for the refactored sections. Repeat until satisfied, or out of time.
Source: https://old.reddit.com/r/termux/comments/18am78j/luks_encryp... (old.reddit.com/r/termux/comments/18am78j/luks_encryption_and_decryption_in_the/kc1ica6/)
It turns out you can't just go and unilaterally decide to kill people.

There is a good reason people want government institutions to
jealously guard this right.

The government is very fickle with giving out the death penalty.
It's the collateral that would be frozen. It's not your stablecoins.
Exactly this. You plan around what might be needed in the future. I've found some extra work now is usually a lot less work in the future.
I like the author's analogy and I'm pretty sure this country has regulations around selling food, but there isn't much of market consolidation. People open and own small restaurants and it's not only chains and franchises all around. People even start new banks and get licenses and the product is quite good. And there are things that are more regulated than opening a bank. I suspect that the CRA is not on a level of operating a bank and somewhat more lax than operating a restaurant.
You can't put it as "everything is exactly the same, but I just change the fundamental mechanism"
A key part of slavery is that you’re not allowed to leave, what is keeping people in NYC?
We went the other direction (to be fair, just building a simple static site). I’m a developer therefore I should make the marketing site! Problem is that with limited resources that took away time from building the product.

We’ve moved to various platforms over the years so that our designers with a touch of web knowledge can build our marketing site. They’re happy bc they don’t have to wait to make changes and devs are happy bc they don’t have to work on marketing sites.

The designers actually enjoy the constraints to a degree bc it simplifies their job as well.

But like I said, it’s just a simple static marketing site
WxPython & WxWidgets are worth a look. I personally like that it uses the platform's native API rather than emulating the GUI and the license seems ok.
As an SRE that occasionally encounters low-code things I'm also pretty skeptical..

* there is like no source control, or if there is the source controlled thing is an unreadable artifact which generally doesn't belong in source control.

* the workflows are poorly if at all documented.

* they still require a lot of custom code but that code isn't as reusable, tested or testable
* they often require a proprietary runtime, worse this may only run on windows

* they are difficult/impossible to instrument and so are difficult or impossible to monitor. Or if they do have monitoring it is going to work differently than the rest of your stack - likely using email based alerting which isn't ideal.

* the work is still 100% done by engineers either way, I've never seen a low code or DSL be picked up by non-engineers. (I am also skeptical towards DSLs)

The only tool that was semi-reasonable here was Looker which isn't exactly marketed as low code but at least in the version of the product I used did integrate with source control. Though generally the people writing lookml were still engineers.

I'm much more a fan of composable platforms that compress complexity but still make it possible to delve, customize and extend when necessary.
Isn't this solved by POE? For an office building which already has extensive electrical/networking/plumbing needs, pulling one dedicated wire for a robust networking connection seems worth it.
The rule blocking this is

thelocal.de##.article--sponsored
It usually is though.
Names are usually pretty arbitrary. Lots of languages have a "spaceship operator" but i would have no idea what it means if i didn't have it memorized.
Knowing Silicon Valley, the NSA and CIA are full of minorities who can’t get hired there because of the latent racism.
I think if they have ever seen your account password in any password dump/leak (ie. if you reused the password elsewhere), then they effectively prevent password login. You have to have another already-active session.

Makes sense really.
DiffDebugging is not a term I have ever heard of before, but I guess it's something I do on a regular basis. The code used to work, it doesn't now, WTF has changed?
Right, but how does that relate to my comment, or the parent's comment?
What do you think nurses do that having Filippino nurses would be a national security hole?
> We should not aim for endless productivity

There is no such thing as endless productivity. We should always aim for higher productivity, because that means getting more for less. What we should not do is to reward solely based on productivity.
Most SDEs have grown up in a severe labor deficit. It's so interesting seeing the idealism smack in to reality.

1. Those "employee-appreciations" were a cost-saving measure to retain talent. 20% time towards projects that benefit the employer vs getting paid 20% more, or free food at an incremental cost of $100/mo/employee instead of paying $2000/mo/employee for equivalent comp-based retention.

2. We are no longer in a severe labor demand deficit. Quality of life will converge on the American norm - treating employees like disposable cogs, under layers of brutal middle-management politics.

3. "Believe that people can change the world", or caring for and investing in employees... Can you point to any industry that was sustainably disrupted by a company following such a mindset? The only examples that come to my mind are niche companies that market based on such an ethos, like Patagonia. Of course there are stable European companies, and US union shops, but those aren't disruptive. WeWork had that ethos for a little while I guess.
Where I use low code is in essentially expert systems, where I need to encode the expertise of some SME. For instance, a lot of places have regulatory compliance burdens. The detailed rules for compliance changes by jurisdiction constantly. Most enterprises setup some sort of requirements to engineer pipeline that everyone’s bitterly unhappy with. It is never fully compliant, has tons of errors, the engineers resent their jobs, and the SMEs resent the engineers. Instead by instrumenting the system with a low code surface area with a policy management system overlaying it you get an excellent platform engineers like to develop, SMEs can author and manage their policies directly, and you capture a rigorous workflow which auditors and regulators really dig. This doesn’t make the engineer less important, in fact they’re much more important to ensure the policies are expressive enough and touch enough business data to ensure the policies are complete. They’re just not playing regulatory policy telephone games in code.
> This is Big Tech only: only them will have the amount of resources to fit the requirement of such act.

I haven't read the actual legalize in the final version. Which kind of responsibility is putting unbearable burden on the average web developer who slaps together few input fields and makes a nice CSS job?

Add: Auditing all the million dependencies in node_modules comes to mind, but maybe it's a good incentive to not.
This is what some of the new dedicated AI chips are designed to overcome. https://www.untether.ai/technology explicitly calls out the issue with Von Neumann architecture and has cells that combine compute and memory in one place. I'm pretty sure https://groq.com/ has a similar concept.

Some interesting stuff happens when you're memory bandwidth limited, particularly parallelism doesn't help, and it becomes faster, in an LLM, to use quantized 16-bit weights that get converted to float32 when used because the cpu can convert, multiply and add faster 16 bit values faster than memory can move 32 bit values to the cpu.
> The fact that a solo developer selling 100€/month of support is treated the same way than a billion dollar company demonstrates the complete insanity of this act.

But they're not treated the same way. Both by the law itself and the standards courts and regulatory agencies use throught Europe.
I think the gap is quickly narrowing on the need to fully comprehend most
computer programs for most use cases, ...

What makes you assume that current "AI" "comprehends"?

I wish it could, but it appears not to.

As an example, ask it to code up something from a "less popular domain" (e.g., Clifford algebra).

You might notice that it appears to not have enough data to make good guesses.
Some "AI" hype folks appear to move the goalpost then.

However, maybe the stock market and some companies benefit from all this sensationalist stuff.

I wish I had a HAL 9000 beside me, but I am sorry Dave, I cannot let you do that.
Most apps target Gmail because most users use Gmail.

Supporting other email providers would be nice to have.
It's open source so maybe someone else will contribute support for other emails before I get to it. It's not the first item on my roadmap. I'd like to perfect the current user experience.
That raises an interesting situation as I expect that one would be able to copyright the 'prompt' but not the generated image, and since the generated image does not include a representation of the prompt then someone else could generate the same image without violating the copyright since they are not reproducing/publishing the prompt. Prompts are then best protected as a trade secret.
Interesting, it supports an n-gram indexer. ripgrep has had this planned for a few years now [1] but hasn't implemented it yet. For large codebases I've been using csearch, but it has a lot of limitations.

Unfortunately... I just tried the indexer and it's extremely slow on my machine. It took 86 seconds to index a Linux kernel tree, while csearch's cindex tool took 8 seconds.

[1] https://github.com/BurntSushi/ripgrep/issues/1497
This is actually funny in that it reminds me of a Big Dumb Bank that I worked for post-GFC that was so screwed they were in endless cut mode. One year they basically ran out of money to severance people out by Q3. How the accounting magic of this works is beyond me, but they continued to employ these people instead of laying them off.

There were entire disbanded teams that resulted in roving packs of feral engineers showing up to the otherwise business casual office wearing sandals, baseball caps, and tees.. basically screwing around all day but showing up 10-3.

Some of them were offered up to existing teams "for free" for the rest of the year, but most of them were so far gone that it wasn't worth assigning them any tasks you actually needed done.

It's interesting that AMZN has gotten to this point so quickly from peak.
Online retailer Zulily is going into liquidation, shutting down
More jobs can always be invented/created in the name of safety. More regulators, more regulations, more psychological councilors, more child protection specialists, more DEI councilors, more lawyers for more lawsuits, more military divisions (to keep the country safe)... etc. Mainly supported with public funding.

Not saying those aren't real jobs (many certainly are), but I think the scope & number of those jobs can be expanded to fill the void left by more "productive" / "survival" jobs.