Personally I have not experienced it, but I have heard of people scanning for LGPL library usage in iOS apps, then essentially extorting the developers for their source code.
I can't find the specific article now, but I am extremely careful to avoid anything GPL or LGPL.
How is that extortion? If you use a library/project with a licence you need to abide by its terms. If you don't want to do that, then either write it yourself or find an alternative. People asking for the source code is not extortion, they're fully within their rights to do so.
"""
Just anecdotally, but this aligns with my observations on the trend/growth of successful useful open source projects that go with permissive BSD-like license. ~20 years ago there were way less of those than now.
And as a SW developer doing client side/apps as well, using GPL/LGPL is a total pain and basically cost prohibitive, unless I work on my personal small project where I don’t care about having to/risking to open source the rest of the code and getting sued/cloned…
Real life example from ~2010 - we ended up including an LGPL library in our mobile app code, and published/upstreamed all the modifications we did to that code (mostly ARM optimizations). Once the app became popular, our competitors came to us demanding the source code of our app - just because iOS didn’t support dynamic libraries (so we had to statically link it), and giving them the object code to relink it wasn’t enough for them (which would satisfy the spirit of LGPL), because they really wanted to see how we hacked around iOS camera input APIs…
"""
Arguably the competitors didn't have a case as the object code was provided, so I would stand by calling this extortion. Maybe the legal burdens were too high, so the company complied.
We created an Abstract controller that handles all of the typical behavior for a resource, auth, filtering, pagination, tenancy, import/export, serialization etc.
Then we expanded rails generators to cover ALL typical behavior. And the markdown file calls the generators.
It was a bit complicated to model polymorphic behavior but we got it working thanks to Ruby/Rails.
But the basic premise that made this work is: Use only restful actions; don’t turn it into RPC.
Recognize that most RPC/graphql functions are state changes that could have been a patch request. So instead of /clients/activate its /clients with a status attribute for “activate” or “archive”. Then most nested routes aren’t needed, use accepts nested attributes for and return child ids in the show action. There’s more to it that this but by strictly following conventions and modeling the data for rest, the api ends up
Super simple.
Our standard controller only whitelists strong params. All other behavior is automatic.
I disagree on this, there are plenty of problems in accounting that an LLM can help with.
I’ve built some software[0] that analyses general ledgers and uses LLMs to call out any compliance issues by looking at transaction and account descriptions.
Is it perfect, nope. But it’s a hell of a lot better than sifting through thousands of transactions manually which accountants do and get wrong all the time.
> But it’s a hell of a lot better than sifting through thousands of transactions manually which accountants do and get wrong all the time.
I still wonder why humans getting things wrong is a problem, but LLMs getting more things more wrong more often than humans never is. At the very least you'll need a human accountant around to verify the LLM. Or I guess you could just practice "vibe accountancy" and hope things work out but that seems like a worse idea than a trained human professional. But I'm probably just a Luddite.
Also, I am admittedly not an accountant, but I don't think they manually sift through every transaction to verify compliance issues in every single case. That probably isn't how that works.
I weigh the economic value against the lives I believe is going to ruin and the damage I believe is going to do to society and the future of the human race and I do not find value there. I find ruin
There might be a way for us to adopt AI as a tool without bringing ruin to many people, but I don't believe that is the goal of anyone building AI.
As it stands, I don't believe there is anything ethical about AI in it's current form. So from that perspective, I vehemently deny there is any value in it
At one point in history, people like you were asking why anyone could be anti-slavery. After all, it was impossible to deny the economic value of slaves.
Some specific examples (like the one you mentioned, _adjacent_ to accounting per se) don't disprove the main point that 100% accuracy is fundamentally impossible with LLMs, while critical for all key accounting aspects.
My preference is 3 days in the office, I find anything less than that and I struggle mentally. My home starts to feel like a prison and I lose connection with people.
I really value human connection and I just don’t get the same thing online.
I relate to that and I think the real reason some people struggle to believe that is because not everyone has a great work environment at work. I have one, I actually look forward to coming to the office sometimes.
I was pondering this, because my team is very small, so I don't get to interact with all that many people at the office (the people I interact with will 90% of the time be elsewhere anyway).
But apart from that it seems like the worst of both worlds? You still have to commute there, you can't reasonably expect to have peace and quiet since it's mostly open space (or if it's a closed office, how's that better than staying home?), and you don't even get to see your colleagues.
In my case, what I hate with the office is the commute and the random noise people make (phone calls, chats, whatever). I rather like my colleagues, so it's not like I want to avoid those people specifically.
Not the previous commenter, but co-working spaces are few and far between in most of the world, plus they can be expensive if the employee is the one paying.
As for the coworkers not knowing your boss thing, I agree, although in a more positive framing – it can be helpful to have a work social group that isn't in your reporting chain. You can get this at many medium sized and up companies.
Or better yet, a therapist. Work is literally THE worst place to make human connections because it is a business first and foremost (yes, go ahead and post how it’s not true – it won’t change a thing).
> Work is literally THE worst place to make human connections
I don't necessarily disagree, but I make a slightly different argument, in that, humans will make human connections, whether they like it or not, and the most typical human experience is to make stronger and stronger connections with people you see regularly. Furthermore, depending on the company, there's the desire to be a part of something bigger, there's social conditioning setting in to prove yourself among your peers, there's the desire to not appear like you're lazy.
Where I think you'll agree is that your company will 100% exploit these human aspects of you to get a better margin on the value of your labor vs the compensation they pay you.
Let me clarify my point: in the absence of life outside of work, work is the worst place to make connections. If you treat work as “just” a complementary source of connections, then it is fine. But if it’s your only source, then you need to get of this situation asap.
We have an intern that is finishing a four year computer science degree that has no clue what git is, never used a log and all he presents is AI garbage.
I find it profoundly depressing to try and teach someone who has no interest in the craft.
Capitalization would not change the content at all, but would make it easier to read. People reading English have expectations are capitalization. Breaking those expectations makes the text more difficult to read and feel less effortless.
They still respect writing rules, in fact - except for the capitalizations.
If they wrote, say, phonetically instead, the text would become utterly unreadable, even though the raw thoughts in one's head aren't expressed in written English.
https://acronyms-suck.com
reply