asp_hornet

One of the theories floated is if an advanced civilisation made it to us, they would most likely be so advanced they would see us no differently as we would view ants and not even consider us if they needed any resources from our planet.

Another thought is the fact that no advanced civilisation has ever made it to earth is proof that any intelligent species is destined to destroy itself before it can evolve far enough to travel the stars.

Both outcomes are pretty bleak

If people invested as much time improving their abilities as they did gaming the system, they might find the problem solves itself.

It truly is indistinguishable at this point. Its all posturing and optics.

This thread reads like a whole bunch of sour grapes. Hopefully this challenges other companies to do better

Remember, M4 is iPad only for now not macbook. No light on those

Yeah, like all those short sighted bitcoin naysayers.

Sometimes overhyped tech is just over hyped tech.

Are we pretending large language models are artificial general intelligence so we can role play?

Overlooked answer? Aren't you are literally describing a mobile phone. You know, before they were smart phones with distractions. The nice thing about this solution is its less likely to be forgotten because its on the wrist.

Maybe they misunderstood the site and thought hacker news was related to the hacker ethic of building stuff.

i feel this is a sentiment shared by every generation. “Now with printing presses, kids have access to tombs of knowledge”

Conversely, you used to look at a line of OS code and knew how that translated to registers within a processor. Now i barely know which kubernetes cluster the code is currently deployed in

An awesome project and great write up. This is what i come to HN to see.

Especially given all the negative sentiment in the developer community towards Devin. You would think they would want to distance themselves as much as possible

Oh wow. That’s crazy overkill

Why cant the mac use it?

Am I understanding the story correctly? a year plus, no doubt horribly expensive engagement with an external vendor was replaced with a few weeks skunk works project buy an internal team member who executed it by lying up the chain of command and there were no repercussions.

> path of least resistance

Great take. It feels like the path of least resistance peppered with obscene amounts of resume driven development.

Complexity in all the wrong places.

Isnt that an extension of the same problem though? You probe it to take the statistically most accepted alternative perspectives that exists in its data. Its not intelligent in the sense that it comprehends what you or it are saying, it just follows the weights.

Well said. Its nothing to do with the language or tooling, just this weird ingrained dogma.

> On the other hand, you can easily have a programming career in .net alone. Its not going away the next 30 years.

Not to mention if a service offers an official client or SDK, C# is almost always on that list. That is awesome.

> Professionally I've only ever worked in c# code bases.

Pretty much answered their own question in sentence one.

In my opinion OP is delusional. I worked in .net for 13 years and was stoked to leave. The layers of indirection, obtuse abstraction and over application of design patterns in “idiomatic c#” is preposterous.

I agree with you 100%

I love everything about this. The shareware, the price, the source code. It reminds me of how software was in the 90s.

It already doesnt. The problem is the operator

Modern software is so cumbersome and bug prone that people just presume bugs instead of the software doing its job.

> He made sure that he boarded before the the passenger who had the boarding pass information that he stole; when the other passenger tried to board, the system suggested that this passenger had already boarded, though the gate agent assumed it was a glitch, so allowed that person to board

This exists because most modern rewrites of COBOL systems have been rewritten several times over despite the rewrites never finishing all the functionality of the original.

Modern day software engineers need to eat a huge slice of humble pie.

Modern cloud “5 nines” isnt a promise of availability but a promise to get some store credit each month when it inevitably fails (adjusted down for usage because you dont use all that capacity you pay for so we just credit for the percentage you do).

The trick is to make sure when you promise 5 9s to your customer that you build in the same bullshit clauses so you dont get left holding the bag.

Its gross

Everyone who clones a node project will call npm install before the call npm run. Having a seperate install command doesnt make it more secure, it just makes 1 more thing for newbies to learn and another thing to go wrong when you pull master and someone added a package and you called run without installing again.

Oh, thats true about it being unexported. I hadn’t considered that.

No, you’ve achieved an illusion of that as now your spending hours wasted on discovering where a developer forgot to call NewUsername and instead called Username{“broken”}. I cant see the value in this abstraction in Go.

I’m not sure I understand. In your example you’ve grouped related data in a struct and validating that it matches your system’s invariants, that feels good to me.

The original example was more “wrap a simple type in an object so it’s always validated when set” which looks beautiful when you don’t have the needed getters in the example nor show all the Get call sites opposed to the 1 or 2 New call sites. All in the name of “we don’t want to set the username without validation” but without private constructors Username{“invalid”} can be invoked, the validation circumvented and I’m not convinced the overhead we paid was worth it.

> need a getter

Yeah, thats what I figured. Im not sure if I want the tradeoff of calling .GetValue in multiple places just to save calling validate in maybe 2 or 3 places.

Not to mention I cant easily marshal/unmarshal into it and next week valid username is a username that doesnt already exist in the database.

Maybe this approach appeals to people and Im hesitant to say “that’s not how Go is supposed to be written” but for me this feels like “clever over clear”.