coreyoconnor

They don't follow basic design principles. If i have to tell the ai every detail of basic design then... Well... I do not consider that very intelligent for a software dev.

I do use AI extensively and get it to spit out vaguely acceptable designs. But I'm doing the design. Even when i have another agent trying to simplify or such the design details are still me.

I don't think people understand how this runs in contrast to the claims of intelligence.

Nice! Thank you.

That does defeat the claim that AI is intelligent IMO. I should not need to dance with instructions in order for the LLM to behave intelligently.

Which of these has effective accessibility support?

I suspect if such a filter was applied there would be very few. Probably just the bindings to gtk, qt or appkit.

Everytime i read one of these vibe coded projects i wonder: Is AI capable of building well structured programs? Designs with strong separation of concerns. Clean code. Short, well defined functions.

This is not how I'd design much of this. Does that matter? AI and whatever training data used seems to differ.

I'd love to try these new phones. My current phone (Google Fold) is terrible. However

1. google pixels are the best android devices AFAICT. Not a high bar, but that's that.

2. due to the prevalence of spam and scam calls: Not having an AI call filtering is a no-go. google pixel's have a really nice call screen.

Course we could have a competent government that would do something about scams (besides encouraging and supporting them). Then small business could actually compete. But the best we get is a rapist and scam artist.

I left amazon, in part, because of this realization: Much of management was exactly doing that. That was back in the BERT days and even then writing was on the wall.

How do you educate people on stream processing? For pipeline like systems stream processing is essential IMO - backpressure/circuit breakers/etc are critical for resilient systems. Yet I have a hard time building an engineering team that can utilize stream processing; Instead of just falling back on synchronous procedures that are easier to understand (But nearly always slower and more error prone)

I appreciate the spirit. Not treason, but definitely anti-making-shit-better.

I use Jira a lot and... there are keyboard shortcuts. There are keyboard shortcuts for Confluence.

I did not know about the jira shortcuts until recently. Not really a huge deal for me. Seems like linear's are definitely better but shrug. Keyboard shortcuts are not the source of my issues (ha!) with issue trackers.

Confluence shortcuts tho. I'm pretty sure I'm the only one in my company that knows them haha. Which says something about confluence for sure.

You're welcome! I think akka has been making great strides in polishing the rough edges. (Along with the rest of the Scala ecosystem TBH). Unfortunately that doesn't seem to generate the hype I'd argue akka deserves shrug

I've had good success with akka at multiple companies. At Protenus the core ETL is based on akka streams. Which has worked great. No notable issues. Tho we don't run in clustered mode.

At glngn we didn't use akka streams (outside of akka http) but did use event sourced, persistent entities powered by akka typed in clustered mode. Deployed to k8s. Which definitely took effort to set up nicely and enable smooth deployments. Our clusters were not huge so many problems did not show up (split brain).

I haven't used other systems that provided an equivalent to akka typed persistent entities. I can't compare akka in that sense. However the event sourced persistent entities model is really, really effective. Definitely a different paradigm: some stuff is trivial that would otherwise be a trial.

I suspect many of the benefits could be achieved by using something like Kafka feeding non clustered nodes. But never tried.

"[Arrived] in a $1-million leather bodysuit with an anatomically-correct gold breastplate and a 15-carat-diamond nipple. 'You were just surrounded by the most interesting and intelligent people that you could find anywhere in the world,'"

Interesting juxtaposition haha.

The reason is the concern that users will confuse issues with the project with issues with how the project is distributed in Nixpkgs. He doesn't want to have to support nixpkgs.

There are likely multiple root causes. The whole space of issue management around libraries and applications using those libraries is a horrible and abusive mess. In my experience, between an application using a library and a library users will target whichever is easiest; not most applicable. Plus, most opensource user support is a fucking chore (you'd need to pay me for these days) that's unsustainable.

Another cause is likely the cost of nixpkgs contributions themselves. Personally, I no longer contribute to nixpkgs because even for tiny changes the process is ridiculously expensive. That's not including the cost of getting up to speed with nix/nixpkgs and the, often, highly opinionated packaging.

nixpkgs needs to be broken up into multiple independently distributable packages.

For fun I've been analyzing the contracts posted to r/CryptoMoonShots. Out of 20 posts 16 of them used the same contract; modulo names. This contract blocks everyone from removing funds but the owner.

How? Is it some complex chunk of code that requires a delicate hack?

No, not at all. There is literally a function with code, more or less, like: "If owner then OK here's all the funds". Anybody can check this in the contract. Yet people are dumping funds into these contracts. Even tho these contracts tend to only attract a few thousand dollars each. Well, costs next to nothing to create and spam.

A more detailed analysis of a similar contract to the one I've seen: https://cryptot3ddybear.gitlab.io/blog/posts/scam-explained-...

After a lot of scrolling through marketing hyperbole... What is it?

No cynacism meant. My mistake. "motivations" was incorrect. I was trying to ask about how the business of AWS manifests such a thing. Which I think you've described. Thanks!

While the above case is (arguably) crime. In general crime is unrelated to this issue.

As for licensing: totally agreed. I would like to see more projects with protective licensing.

Too many projects are basically donations to Amazon.

"please don't" doesn't pay the bills. You want those people to avoid transferring the reigns for cash? Find some sustainable way to pay them. No amount of feel good platitudes will do that.

I wonder about the complexity and AWS motivations.

What does AWS gain by improving IAM? There are barely any competitors, so they won't be losing people for that. They offer their own AWS professional services happy to charge you for making it "understandable". Their service agreements largely absolve them of client mistakes. Which usually result in larger bills from AWS.

"hence not in CLI applications" is that specific aspect accurate? I'm no longer mac user but thought mdfind (https://ss64.com/osx/mdfind.html) was the command line version of what smart folders use. Not the same as a filesystem but usable for many CLI apps.

Looks like this one has edges that are easy to grip. Samsung phones should take note ;)

Is there a press release that doesn't use a ridiculously overused scroll visualization?

(scala dev here)

Scala has a history of embedded domain specific languages that are difficult to understand. (Rather like Perl now that I think about it.) This is not universal in scala EDSLs but definitely exists. So it's a fair concern in general. IMO Chisel is a nice EDSL so, in this context, the concern is unwarranted.

Run OpenShift and invite friends to use it for hosting.

Did not know this. Is that due to browser issues or a specification issue?

No worries for Amazon SDEs! The amazon software developer "outside contributions" agreement basically states that you are not allowed to do anything without approval anyways. /s

Seriously tho. When I was employed by them their agreements were by far most draconian compared to any other company I've worked for. Ridiculous.

Most companies I've worked did have a route to enable you to contribute to projects outside of work and still retain the rights. Tho the easiest route is to establish something within a domain you want to work and then state that on a "inventions and copyrights" pre-employment agreement. This will outright eliminate you from certain jobs but... That's the US for ya.

SEEKING WORK

Location: Seattle, WA

Remote: Yes

On-Site: Yes, no relocation

Technologies: Scala, Ruby on Rails, Ansible, Jenkins, Nix, NixOS, DynamoDB, Postgres

LinkedIn: https://www.linkedin.com/in/corey-o-connor-389ab23/

GitHub: https://gitlab.com/coreyoconnor/

For fun I do this: I ask them how much it'll cost upfront. (they can rarely even give bounds). Ask about refund policy (?!?!?!). Tho must be done nicely as the person handling the questions is no way responsible for the absurdity.

I know these won't actually succeed in adding a bit of capitalism but it does succeed in highlighting the absurdity.

Ideally yes. However, that's assuming a lot of privilege that the average consumer wouldn't have at all in this case.