Technology
News community around technology, social media platforms, information technology and governmental policy surrounding it.
What doesn't fit here?
The core of the story has to be technology focused.
- If article mentions "AI" in a sentence and then talks about business economics that doesn't make it tech news.
- Gaming is too many layers removed from technology. There are many dedicated communities that are a better fit for it.
- Transporation is too many layers removed from technology. EVs while use many cool technologies have many dedicated communities that are a better fit for it.
- Entertainment is too many layers removed from technology. While sometimes it can fit here, business or cultural aspects of it are a better fit for dedicated communities.
- Cybersecurity. While it heavily focuses on technology, most of the time it's too technical for most people who are not already invested in it. Should be posted in a dedicated communities unless it has broader connection to other tech areas.
Post guidelines
Title format
Post title should mirror the news source title. If you don't like the title of article, look for an alternative source instead of editorializing it.
URL format
Post URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.
[Opinion] prefix
Opinion (op-ed) articles must use [Opinion] prefix before the title. Opinion articles refer to articles that their publisher doesn't explictly endorse.
Country prefix
Country prefix can be added to the title with a separator (|, :, etc.) if the news is from a local publisher who doesn't clearly mention the country.
Rules
1. English only
Title and associated content has to be in English.
2. Use original link
Post URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.
3. Respectful communication
All communication has to be respectful of differing opinions, viewpoints, and experiences.
4. Inclusivity
Everyone is welcome here regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
5. Ad hominem attacks
Any kind of personal attacks are expressly forbidden. If you can't argue your position without attacking a person's character, you already lost the argument.
6. Off-topic tangents
Stay on topic. Keep it relevant.
7. Instance rules may apply
If something is not covered by community rules, but are against lemmy.zip instance rules, they will be enforced.
Companion communities
!globalnews@lemmy.zip
!interestingshare@lemmy.zip
Icon attribution | Banner attribution
If someone is interested in moderating this community, message @brikox@lemmy.zip.
view the rest of the comments
Yes there is. No one wants to listen to us. I've had 3 levels of people above me ask me how I've incorporated AI into my workflow. I don't get any pushback because my effectiveness is well known, yet the top down edict that everyone else use these shitty tools continues unabated.
Where I work, my skip-levels have started debating on whether they want to consider if an engineer uses AI as a factor for reviews, pay raises and incentives, and are tracking who uses it by way of licenses.
It's a bit ridiculous IMO because they're essentially saying "we don't care if slop makes it into the code base, so long as you are using AI, you will remain gainfully employed."
I've seen a lot of stupid shit over my career but this AI zealotry just takes the cake.
Everyone is so convinced these tools will make software get made faster, but I'm not even convinced that it gives even a modest benefit. For me personally they definitely don't, and it seems to lead junior devs horribly astray as often as it helps speed them up.
It feels like I'm not even looking at the same reality as everyone else at this point.
I wish I had one like you at where I work, just to keep sane for a bit longer. Everyone else is just way too into this shit even though for most it seems like a gigantic time sink.
I mean "ought to be useful," sure that would be nice. They ain't, but perhaps "ought to be."
It's useful for things I'd otherwise Google. It makes a great ORM, when you know exactly what you want to do with a lot of mundane code. And it's so much better than adding a framework for an ORM.
I don't like ORMs, but I'd rather use a battle tested ORM than some vibe coded data layer.
You know, you can just look at it. It's pretty simple, easy to look at, pretty repetitive code where it's generally pretty easy to spot if something's wrong.
Vibe coding is more hitting "accept all" and not looking at it at all (or not knowing how to look at it).
Or, I could just write it myself, instead of ending up like these guys https://sketch.dev/blog/our-first-outage-from-llm-written-code