101–110 of 137 posts
Why does this need GitHub auth? This asks for unlimited private access to ones repo. This is a hard NO from me.
It can open GitHub PRs from the interface and there's tons more info we want to pull in like the result of CI checks
Earlier quoted context omitted.
Thanks, really appreciate the heads up. I put devs who do this on a personal black list for life. I think also that this would be better as an mcp tool / resource. Let the model operate and query it as needed.
It's the email/username harvesting that you mean right? Or do people also have something against anonymised product analytics?
They're not anonymous, they're just pseudo-anonymous. It's incredibly easy to collect pieces of data A thru Z that, on their own, are anonymous but, all together, are not. It's also incredibly easy to collect data that you think is generic but is actually not.
Do you query the screen size? I have bad news for you. But, all of this is besides the point: when that data is exfiltrated to a third-party service, you have no idea how it's being used. You have a piece of paper, if you're lucky, telling you the privacy policy, which is usually "you have no privacy dumbass".
Even if data appears completely anonymous to humans, it can be ingested by machine learning algorithms that can spot patterns and de-anonymize the data.
I mean, we have companies who's entire business model is "how do we string together bits of data and tie it to real-world identity?": namely Google. Turns out it's remarkably easy when you have your hands in a lot of different pots. Collect a little anonymous data here, a little there, and boom: now you know that Billy Joe who lives on First Street loves to go to Walmart at 1 AM and buy Ben and Jerry's ice cream in a moment of weakness.
Earlier quoted context omitted.
I read that too and these are the kind of statements which really tells you what happens when a profession embraces mediocrity and accepts something as crass as "Vibe-coding" which is somehow going to change "software engineering" even when adding so-called "AI agents" - which makes it worse. All this cargo-culting is done without realizing that more code means more security issues, technical debt, more time for huma…
and I came into the industry when software was not engineering. Still think this is mostly true (you can call yourself an engineer when you insure your product)
I'm glad I work for a regulated industry where we still have some kind of responsibility and pride for what we do. I could never work for the kind of irresponsible anarchy that AI is creating.
I would imagine matching tickets/conversations from Linear mcp to use as an overlay of context
We need something like a kitchen brigade in software - one who writes the vibe code tickets (Chef de Vibe), one who reviews the vibe code (Sous-Vibe), one who oversees the agents and restarts them if they get hung up (Agent de Station). We could theoretically smash thousand tickets a day with this principle
If you're doing code reviews, writing new tickets, evaluating progress and guiding the overall structure of a project, do you loose something important or is it genuinely a satisfying way of working which you could imagine sustaining for the long-term?
Add it to this lists, i think it helps:
https://github.com/tokyo-dal/awesome-ai-coding-tools
https://github.com/devtoolsd/awesome-devtools
and any awesome lists related to ai development
Is this really the case?
Earlier quoted context omitted.
Thanks, really appreciate the heads up. I put devs who do this on a personal black list for life. I think also that this would be better as an mcp tool / resource. Let the model operate and query it as needed.
It's the email/username harvesting that you mean right? Or do people also have something against anonymised product analytics?
> human engineers now spend the majority of their time planning, reviewing, and orchestrating tasks This feel like much too broad a statement to be true.
i feel so strongly that this will rapidly become true over the next 6 months. if you don't believe me check out Sean Grove's talk from mid June - https://www.youtube.com/watch?v=8rABwKRsec4