> They’re building a pocket-sized, screenless device with built-in cameras and microphones — “contextually aware,” designed to replace your phone.
Too many people speak of ads, not enough people speak about the normalization of the global surveillance machine, with Big Brother waiting around the corner.
Instead, MY FELLOW HUMANS are programmed to accept and want their own little "Big Brother's little brother" in their pocket, because it makes them feel safe and happy.
It's really a cultural disease to accept this. From my other comment:
> I see this in people why have used antagonistic software for decades and have become zombified and shellshocked; the idea that software could be on your side is to alien to them. They['ve come to] hate software and technology and just want to get some work done. They tolerate the abuse because they can't fight Google alone; it's pointless to resist.
CodeQL seems to raise too many false-positives in my experience. And it seems there is no easy way to run it locally, so it's a vendor lock-in situation.
A big selling point for me. Needless reworking of familiar interfaces plagues
MS Windows ecosystem and I'm glad LibreOffice is displaying healthy conservatism
by not fixing what isn't broken.
Yes I can totally imagine that in a few years, most people will only need a smartphone and a dock station. At home, they will plug their phone (iOS, Android, whatever) to their dock station and it will behave as a Desktop. And it will be good enough for everything they do.
IANAL but the law in Germany is basically the same in this case, accessing data that's meant to be protected and not intended for you is is illegal. It depends somewhat on the interpretation of what "specifically protected" ("besonders gesichert") means. https://www.gesetze-im-internet.de/stgb/__202a.html
I'd love to see some stats on this: people leaving to start something new (be it Apple or any other acquiring company) might be over-represent because there is not much news about people staying in their job
I worked in a team of four between 2017 and 2020 this way. I really enjoyed it. After that I joined a company that worked with PRs. Felt like such a waste of time.
When the same name is used a thousand times in a codebase, shorter names start to make sense. See aviation manuals or business documentation, how abbreviation-dense they are.
The UK banned disposable vapes, the suppliers now add a charging port and the ability to put in refills. The refills cost as much or more than the vapes so now people throw away the "reusable" vapes as if they were disposable.
we have a "release" branch and a "develop" branch. The release is trunked on the last released version and (in theory) only gets fixes. If we need to fix a more older version, we create a temporary branch on that version to fix it, and we cherry pick the fixes (or merge to) to release branch and then to develop branch.
The triple mortal loop, comes that we have two versions of the product. One with the old no responsive frontend and other with a modern responsive frontend. And we need to release and develop the two versions for sometime, before the direction decides to kill the old no responsive version. So we end with 4 branches: release, release_rwd, develop and develop_rwd. If we fix something in release, we need to do a diamond merge : release to release_rwd, release to develop, release_rwd to develop_rwd and develop to develop_rwd
Because I find LLM-generated content very annoying to read. It's sloggish, bloated, and the speaker always has this cringe way of trying to connect to the audience.
I don't believe the story itself is made up by an LLM but I'd argue that if you have an LLM write your story then it's no problem for you to have it add a TL;DR at the top so we can skip the slop.
> I'm of the opinion that having AI be a constant presence in your life and relying on it to assist you with every minor detail or major decision is dystopian in the extreme
Could that be because you're putting some extra substance in what you call an "AI"? Giving it some properties that it doesn't necessarily have?
Because when I'm thinking about "AI" all I'm giving to it is "a machine doing math at scale that allows us to have meaningful relation with human concepts as expressed in a natural language". I don't put anything extra in it, which allows me to say "AI can do good things while avoiding bad things". Surely, a machine can be made to crunch numbers and put words together in a way that helps me rather than harms me.
> It's not going to happen.
I can wholeheartedly agree as far as "it is extremely unlikely to happen", but to say "it is not going to happen", after last five years of "that wasn't on my bingo list"? How? How do we know there won't be some more weird twists of history? Call me naive but I rather want to imagine something nice would happen for a change. And it's not beyond fathomable that something crashes and the resulting waves, would possibly bring us towards a somewhat better world.
Touching grass is important, and it helps a lot, but as soon as you're back - nothing goes anywhere in the meanwhile. The society with all the mess doesn't disappear while we stop looking. So seeking an optimistic possibility is also important, even if it may seem utterly unrealistic. I guess one just have to have something to believe in?
A lot of responses below talking about what a 'certified' or 'chartered' engineer should be able to do.
I thought it would be noteworthy to talk about another industry, accountancy. This is how it works in the UK, but it is similar in other countries. They are called 'Chartered Accountants' here, because their institute has a Royal Charter saying they are the good guys.
To become a Chartered Accountant has no prerequisites. You 'just' have to complete the qualification of the institute you want to join. There are stages to the exams that prior qualifications may gain you exemptions from. You also have to log practical experience proving you are working as an accountant with adequate supervision. It takes about 2-3 years to get the qualification for someone well supported by their employer and with sufficient free time. Interestingly many Accountants are not graduates, and instead took technician level qualifications first, often the Association of Accounting Technicians (AAT). The accounting graduates I have interviewed wasted 3 years of their lives...
There are several institutes that specialise in different areas. Some specialise in audit. One specialises in Management Accounting (being an accountant at a company really). The Management accountants one specifically prohibits you from doing audit without taking another conversion course. All the institutes have CPD requirements (and check) and all prohibit you from working in areas that you are not competent, but provide routes to competency.
There are standards to follow, Generally Accepted Accounting Practice GAAP, UK Financial Reporting Standards FRS and the International equivalent IFRS. These cover how Financial Statements are prepared. There are superate standards setting bodies for these. There are also a set of standards that cover how an audit must be done. Then there is tax law. You are expected to know them for any area you are working in. All of these are legally binding on various types of corporation. See how that switches things around? Accountants are now there to help the company navigate the legal codes. The directors sign the accounts and are liable for misstatements, that encourages them to have a director who is an accountant...an audit committee etc.
How does that translate to software?
There are lots of standards, NIST, GDPR, PCI, some of which are legally or contractually binding. But how do I as a business owner know that a software engineer is competent to follow them. Maybe I am a diving company that wants a website. How do I know this person or company is competent to build it? It requires software engineers with specific qualifications that say they can do it, and software engineers willing to say, 'I'm sorry I am not able to work in this field, unless I first study it'.
The EU directive doesn't even compel them to have those kinds of removable batteries in the EU, because being removable with commercially available tools is considered compliant [0]. The topic has been too obfuscated with hype pieces. Still, it would be nice to not have to break glass and melt glue to open up phones.
> That guy that seems totally legit and just wants your sister to install his fun little game/app that he wrote is actually trying to get her to install an app that's going to track your location and read all your messages and copy all your photos.
Personally, I quite like being able to use the CUA keyboard shortcuts to access menu items. I like consistency over decades but I appreciate that there are other ways of looking at this.
I don't think that's fully accurate (full-disclosure: I've done the technical review for this article).
First, as for "serialization" vs "deserialization", it can be argued that the word "serialization" can be used in two ways. One is on the "low level" to denote the specific action of taking the data and serializing it. The other one is "high level", where it's just a bag where you throw in anything related (serialization, deserialization, protocols, etc) - same as it's done on Wikipedia: https://en.wikipedia.org/wiki/Serialization (note how the article is not called "Serialization and deserialization" for exactly these reasons). So yes, you can argue that the author could have written "deserialization", but you can also argue that the author used the "high level" interpretation of the word and therefore used it correctly.
As for insertion not happening and balancing stuff - my memory might be failing me, but I do remember it actually happening during serialization. I think there even was a "delete" option when constructing the "serialized buffer", but it had interesting limitations.
Anyway, not sure how deep did you go into how it works (beyond what's in the article), but it's a pretty cool and clever piece of work (and yes, it does have its limitations, but also I can see this having its applications - e.g. when sending data from a more powerful machine to a tiny embedded one).
It's still used for job hunting and recruiting unfortunately. I got a real message from a real recruiter for a 5k+ employee software company on it just last week. My friends and colleagues dealing with layoffs have had to update their profiles. :(
Too many people speak of ads, not enough people speak about the normalization of the global surveillance machine, with Big Brother waiting around the corner.
Instead, MY FELLOW HUMANS are programmed to accept and want their own little "Big Brother's little brother" in their pocket, because it makes them feel safe and happy.