sarlalian

There’s a fork https://github.com/LadybugDB/ladybug that you can use.

Because all software has bugs, because the system underlying that software changes and you need to keep up, because for some people it’s just missing that one feature or doesn’t work quite right in that one edge case. I’d bet that there are issues in the backlog with people’s complaining that their issue isn’t being addressed quick enough.

Is AI the problem, or that it had a regression? Is the regression actually caused by AI?

How are the maintainers supposed to know that the users don’t trust VS Code if no one voices their concerns like a rabid mob? Seriously why should the maintainer care what users think about how they produce code?

Bugs happen, regressions happen regardless of whether it’s human or AI written. The only valid criticism is that he’s moving too fast for quality code review by others. That said, I bet if you search through the issues you’ll find multiple places where users have complained about their bug staying open for too long without being addressed.

Part of it is cultural due to the origins of our country. We are mostly a country of immigrants. On the base of the Statue of Liberty is a poem “The New Colossus” which says:

Not like the brazen giant of Greek fame, With conquering limbs astride from land to land; Here at our sea-washed, sunset gates shall stand A mighty woman with a torch, whose flame Is the imprisoned lightning, and her name Mother of Exiles. From her beacon-hand Glows world-wide welcome; her mild eyes command The air-bridged harbor that twin cities frame.

"Keep, ancient lands, your storied pomp!" cries she With silent lips. "Give me your tired, your poor, Your huddled masses yearning to breathe free, The wretched refuse of your teeming shore. Send these, the homeless, tempest-tost to me, I lift my lamp beside the golden door!"

There are reasons beyond the cultural history or being a country of immigrants. Much of the innovation of the US over it’s history is due to immigrants. From modern physics, the telephone, the Internet, mRNA vaccines, etc. 46% of Fortune 500 companies were founded by Immigrants or their children. 44% of billion dollar tech startups are immigrants.

Without immigration, the US would have negative population growth, which is economically probably a disaster. We’d have to achieve impossible levels of productivity to support the larger aging populations. Additionally the job losses you mention are mostly in Technology, Finance and Government… sectors that aren’t exactly dominated by immigrant labor.

Being protectionist doesn’t typically work out from a cost and labor perspective. We already have shortages in farming, construction and health care labor, which are often populated by immigrants. So overall, we’d have more unfilled positions, which would result in higher prices, etc. Native born Americans just don’t seem to want those jobs.

I can really only describe my personal experience adequately vs the X hype, though there are enough influential/experienced devs out there who aren't part of the LLM industry who are saying they are having great success that I have to think that, that amount of smoke must mean fire.

Some background, I'm a "working manager" in that I have some IC responsibilities as well as my management duties, and I'm pretty good at written communication of requirements and expectations. I've also spent a number of years, reading more code than I write, and have a pretty high tolerance for code review at this point. Finally, I'm comfortable with the shift from my value being what I create, to what I help others create.

TLDR: Agentic coding is working very well for me, and allows me to automate things I would have never spent the time on before, and to build things that the team doesn't really have time to build.

Personally, I started testing the waters seriously with agentic coding last June, and it took probably 1-2 months of explicitly only using it with the goal of figuring out how to use it well. Over that time, I went from a high success rate on simple tasks, but mid-to-low success rate on complex tasks to generally a high success rate overall. That said, my process evolved a LOT. I went from simple prompts that lacked context, to large prompts that had a ton of context where I was trying to one-shot the results, to simple prompts, with a lot of questions and answers to build a prompt to build a plan to execute on.

My current process is basically, state a goal or a current problem, and ask for questions to clarify requirements and the goal. Work through those questions and answers which often makes me examine my assumptions, and tweak my overall goal. Eventually have enough clarity to have the agent generate a prompt to build a plan.

Clear out context and feed in that prompt, and have it ask additional questions if I have a strong feeling about direction and what I would personally build, if there's still some uncertainty that usually means I don't understand the space well enough to get a good plan, so I have it build instead with the intention of learning through building and throwing it away once I have more clarity.

Once we have a plan, have the agent break it down into prioritized user stories with individual tasks, tests, and implementation details. Read through those user stories to get a good idea of how I think I would build it so I have a good mental model for my expectations.

Clear out context and have the agent read in the user stories and start implementing. Early on in the implementation, I'll read 100% of the code generated to understand the foundation it's building. I'll often learn a few things, tweak the user stories and implementation plans, delete the generated code and try again. Once I have a solid foundation, I stop reading all the code, and start skimming the boilerplate code and focus only on the business rules / high complexity code.

I focus heavily on strong barriers between modules, and keeping things as stupidly simple as I can get away with. This helps the models produce good results because it requires less context.

Different models prompt differently. While the Opus/Sonnet family of models drive me nuts with their "personality", I'm generally better at getting good results out of them. The GPT series of models, I like the personality more, but kinda suck at getting good results out of them at this point. It takes some time to develop good intuition about how to prompt different models well. Some require more steering as to which files/directories to look in, others are great at discovering context on their own.

If the agent is going down a wrong path, it's usually better to clear context and reset than to try and steer your way out of screwed up context.

Get comfortable throwing away code, you'll get better results if you don't think of the generated code as precious.

The current job market will probably suck for the next 2-4 years honestly. Over time, people will leave the industry and find other career’s and the market won’t be as heavily impacted as it is now.

If possible, go to local meetups for whatever type of role you are in/interested in. The current environment while very different from the 2000’s dot com bubble bust, has certain similarities, and at that time, the only way to really find work was through relationships. I know at that time I ended up switching from being a software engineer to desktop support for about 6 months just to stay employed, especially since it was the only job available in my friend group.

This will be a U.S. centered response, because that’s where I live and work. We’ve tried hiring for local and remote roles. It’s a terrible experience all around, both on the hiring and being hired side of the equation.

The company I work for is a medium sized business, in residential and commercial construction. For example, a recent react native mobile dev position my company posted had about 300 applications in the first hour, with about 500 total in the first week on indeed. Of those applications, 90% didn’t have most of any of the requirements for the position. The job description says that we don’t sponsor H1B visa’s (because it’s stupidly expensive now). Of the 10% that somewhat met the minimum qualifications, all but 1 required sponsorship. This was listed as a hybrid role, only 20 people applied from the region where the office is.

We already know from previous roles that a huge percentage of people with resume’s that say they have the required skills, actually won’t come close to making it through the interview process.

While as a company we like AI/ML tools, and encourage our staff to learn them, and use them where appropriate, we want to invest in everyone’s skills with new tools. We try not to use AI where a human connection is important (hiring, sales, etc). We’ve had to resort to AI for dealing with the massive influx of low quality job applications and it sucks.

Basically anyone who goes above and beyond at this point automatically get’s at least an interview.

I do understand why so many people are just applying to every job that shows up, it makes sense. But it really does make the prospect of finding those few great people very difficult.

We aren’t a ruby/rails shop otherwise I’d reach out to OP.

They are on the record about why they switched to a chromium based browser. It’s been a while, but if I’m remembering correctly, at the time Google was making changes to YouTube to make it actively slower, and use more power on IE. Microsoft realized that while they could compete as a browser, they couldn’t compete and fight google trying to do underhanded things to sabotage their browser.

I get that regardless there were warning signs, but it honestly seems like slack either miscommunicated or flat out lied to them about the ability to address pricing. While in retrospect they should have started preparing to migrate away, it's human nature to assume good intentions and hope that things will work out well.

There's a couple of interpretations here.

1. The sales rep really thought they would be able to retain good pricing for them and it fell through, and at the last minute hackclub was blindsided by their inability to retain the pricing.

2. The sales rep thought that hackclub was likely to jump ship if they had time to plan based on the new pricing, and lied to them about the possibility of retaining pricing. And thought that by doing so they could force at least one year of higher cost.

3. Hack Club is misrepresenting their communications with Slack to drum up public approval.

My guess is that option 1 is the most likely, and the optimism of the sales rep ended up being a net negative, and human nature being what it is, Hack Club thought things would work out, and everyone is already busy so why borrow trouble.

As for complaining online, sadly it seems that bad press is the only lever that most people have as a forcing factor for companies these days. I honestly only had a Twitter account for a long time, just so I could complain about companies in public to get them to do the right thing, so unfortunately complaining online does actually help.

It wasn’t slack, but I’ve had multiple vendors that I was in regular touch with, surprise me with pricing changes in the week(s) leading up to a contract renewal. Never quite this short notice, but definitely as little as 8 business days before the renewal was due.

Both times I’ve paid the new price for 1 year and cancelled. Both times our sales rep was surprised the next year when we didn’t renew.

You can self host for free. You lose some features, but overall it’s still pretty good.

When I run out of need and interest.

Some topics I end up needing to know a lot about despite lack of interest (looking at you UEFI), and so I learn until I can solve all the problems I’m having. Others I quickly pass up my needs and then continue with interest for a while (networking, routing, etc).

This assumes facts not in evidence. While the posted quote is sanitized, the assumption that the poster did the sanitization vs. copying from a sanitized source isn't necessarily supported.

Also, something starts off as a nothingburger side project, so you make some decisions based on that. Then it develops a bit, and turns into something you care about and are able to turn into a business. What people want and expect changes over time, and a license on a codebase that is basically developed by one person, isn't a marriage.

I mean, there’s a chance it’s exactly what he said, “I didn't give it much thought at the time, but knew that I wanted the code to be available for people to learn from, and to make it easily auditable so users could validate claims I have made about the privacy and security of the platform.” … it doesn’t have to be some to be some sort of nefarious OSS altruism, it really could be, “maybe people would want to see how this works”… that ends up leading to … oh crap a bunch of people who have never contributed, and will never contribute, are hosting versions of what I created and taking money that I really would like to have to feed my family.

His point was that we are quickly entering the land of “Source Available” not really being a shield if someone’s willing to spend some time in claude code.

If you look at the commit graph, it’s definitely not a community project.

Whether it’s an explicit design flaw that allows the gun to fire with no interaction with the trigger at all, or one where the gun is prone to fire unintended when circumstances are less that ideal, and an interaction that shouldn’t cause it to fire does. Who cares. It’s perfectly reasonable for law enforcement and the military to want a higher level of safety than what is apparently possible with this handgun.

It really doesn’t matter at this point whether someone is able to document it or not. There is a lot of anecdotal evidence of uncommanded discharge (yes the plural of anecdote is not data), and the reputational damage to the gun and the brand has already happened. If I were in the market for another handgun at this point, I would personally skip the Sig, because even at a %0.001 chance that this is a legit problem, my risk tolerance around firearms is pretty low, so I’ll just spend more and get a Glock where I’m certain it’s safe.

If you look at all the places where Kent has had drama, the common element is him and environments that have pretty rigid workflows. The common thread seems to be him not respecting workflows and processes that those places have, that inconvenience his goals. So, he ignores the workflows and processes of those places, and creates a constant state of friction and papercuts for those who he needs to accomplish his goals. They eventually get fed up, and either say no, not working with you anymore, or no, you’re not welcome to contribute here anymore.

He’s not super offensive, but he will tell a Debian package maintainer that their process sucks, and the should change it and they are being stupid by following that process. Overall, he seems a bit entitled, and unwilling to compromise with others. It’s not just Kent though, the areas that seem to be the most problematic for him, are when it’s an unstoppable force (Kent), and an immovable wall (Linux / Debian).

Working in the Linux kernel is well known for its frustrations and the personal conflict that it creates, to the point that there are almost no linux kernel devs/maintainers that aren’t paid to do the work. You can see a similar set of events happen with Rust4Linux people, Asahi linux project and their R4L drivers, etc.

Or if you use your fingers to move the display… a fairly common action with a laptop.

Boy are they going to make that instagram feed fire.

1. Sarcasm, even sarcasm you think is obvious, rarely is. Even less so when in text and not spoken. 2. Not everyone on this site is a native English speaker, so won’t necessarily detect sarcasm and idiom super well. 3. Yup, blame the reader because they didn’t get what you were laying down…

Maybe, women don’t have a responsibility to me to make things work. I just don’t see a world where women stop working, and go back to where they couldn’t own property or get a credit card or bank account without having a man. Women have discovered that it’s possible to find men that have jobs, take care of themselves, and participate in household chores and child rearing, and frankly the expectations in general are reasonable.

The fact that so many men have the response to that of, fine… we’ll take away your reproductive freedom, and next we’re coming for divorce. We want you trapped.

Society changes, people have to adapt, and right now society is failing men, and they aren’t adapting on their own. I’m not sure what the answer is, but Andrew Tate for sure isn’t it.

There’s a significant amount of discussion and research about the problems both young men and women face. It’s definitely not 100% a men are to blame for everything, situation out there. There’s plenty of discussion about how women treat each other, about how some of the staunchest supporters of laws against women’s health care and autonomy are women, and about the crazy expectations for men that some (mostly young), women have.

Each topic hits only certain types of distribution, so if you’re reading and social media sources, are all pretty similar, or you aren’t trying to make sure you click / positively influence the feed to what you want it to be, you might be missing a huge swath of information.

I can 100% agree with this. I’m a pretty liberal person (my father says a little left of Lenin), but I did grow up in the south shooting guns with family, and am still interested in firearms and related information. It’s so hard to get youtube and other things to actually believe that I’m liberal because “guns”.

Tmux absolutely can move panes between windows, including into their own new window. And can move windows between sessions.

That’s underselling the community around it. Most subsystems have dedicated maintainers at this point, and it’s improving at a reasonable rate. It’s just new and new tools don’t have the full set of features of older tools.

I’m assuming based on your dismissal of people using a new terminal emulator instead of one which has been around for decades, that you don’t want any time or effort invested in new tools.

Or they have experience as open source maintainers, and don’t really answer questions that you can find out for yourself if you look at the github repo.