My feelings are all over place about AI. I think the technology is amazing (in the right hands). In terms of it's capabilities.
If we are talking about application, ethical concerns then I think it fucking sucks.
The way I see it. This is the inevitable end goal of social media. The way social media grants instant gratification is the same way LLM's do just on a much larger scale. To me both of these things are connected.
We've been exploited by tech companies using fast feedback and this to me is another level of that.
Which browser / version / os? And was it any particular bowl that crashed it?
It works fine for me on Chrome, Safari and Firefox. However, some models have produced crazy resource intensive ramens before. I audit them now before pushing to make sure they're not too resource intensive
Whilst the first training sets would have used Stack overflow and open source projects.
I have my suspicions that the AI companies have been using reverse engineering to gain more training data.
Ethics don't really concern these companies so...
When you have essentially infinite compute and are constantly looking for more training data. To me the next logical step is to start reversing compiled programs.
It could also explain why these AI models are so good at it too...
Interesting that a Rust re-write pre optimisation was 30% slower than the C++ equivalent.
I wonder if they optimised the C++ it would actually have more speed benefits than the Rust alternative. Only they can't claim it's a Rust rewrite like every other company at the moment.
You could consider getting an older flagship phone perhaps 2022-2023 and have a strong portable device with a decent amount of compute power and not to mention ram. I'm starting to believe that these devices are under utilised and we will see some interesting applications using either with AI or without.
I particuarly think the economics of this are interesting, if you take the one plus 11 you can get one for around £200-250. The CPU is very capable and the alternatives are a PI 5 or N100. You get 16b of ram, a screen, gps, bluetooth a camera... the list goes on.
These devices could really shine as edge computing devices and I believe they are overlooked.
The problem with modern smartphones is that they run on battery, even when plugged into external power. You cannot use it without the batteries without some more hardware hacks. As the batteries aren't designed to be always in a fully charged state, if you decide to use the phone with the battery (with 24x7 power supply) then you also have to carefully monitor the batteries too. Batteries tend to heat up when charged / discharged, old batteries can also bulge or, worst case, even explode. Another thing you need to consider is cooling - Smartphones are designed with the idea that their CPUs won't run at 100% for a very long duration. A smartphones CPU, Camera, battery etc. tends to get hot on prolonged use. So if you are, for example, planning to use it as a mini webserver or media server or as a 24x7 streaming cam, you need ensure it remains adequately cool. And ofcourse, the best smartphones for these kind of projects is one capable of running Linux.
Some OnePlus devices have a "bypass charging" system. My OP8 Pro is running since 2y now as a Kubernetes node, and nothing bad has happened to its battery (yet).
I'm honestly curious to see if bypass charging is on, but it's been a while since I touched the device itself and it has been fine do far. YMMV
>>The problem with modern smartphones is that they run on battery, even when plugged into external power.
That's not universally true - a lot of android phones have a "bypass charging" mode where you run directly from the power supply, and indeed you can run them with the battery removed.
I think sometimes playing games on the phone while plugged in would actually drain battery because the CPU just used too much power (obviously a while back when charging was lower power).
Not sure if those phones would work without a battery and throttle the CPU, or if they would crash.
A lot more mobile devices will require removable batteries after 2027 due to EU regs.
There are exceptions, so not all phones will, but more will. I hope there'll be more time/effort put into hacking removable battery phones to accept hardwiring a PSU onto the battery terminals over the next 5 years.
I've been toying with the idea of learning zig and weirdly enough I was looking at this guys book. I don't have any experience with low level languages. The closest I've gotten is Go.
I was debating between C and Zig, but I still don't really know what I want to choose. Feels like C is probably the right choice given the languages age and it could technically be more useful (not that I'd be looking for a job doing C work).
C is still supreme for working on the majority for a Linux/BSD system stack. It also imparts skill that transcend to most other spaces where you may eventually need an FFI to interact with a library anyway or understand how it actually runs on a system.
It depends for what you want it. If you're going to do an API, well, Golang is more practical here in my opinion. For TUI apps, I would dare to say Rust was more pleasant than Golang. My experience with Zig was limited, I would not say is not a good fit.
I would say from a pedagogical perspective, learning C is hugely useful for understanding how programming works at a much lower level.
This has the benefit of you learning about manual memory management and how to deal with all the issues that come with such a rules free language like C that will basically let you do anything. This understanding means lot of the constraints and features that safer languages like Zig and Rust add start to make a lot more sense. For example, going from Python to Rust, the borrow checker will probably seem rather arbitrary, but going from C to Rust, you will find the borrow checker is just automating a lot of checks you were already doing yourself.
For that matter, assembly is useful as well. Not that you have to become an expert in it, but do enough that you understand it from a practical standpoint. It doesn't even have to be on x86, use an emulator of something simple like a 6809 or 6502. I never had trouble understanding pointers in C once I had some experience writing assembly code.
I think you should know C if you want to do low level stuff. It will help understand why zig (or rust) is built the way it is and what is useful about it, too.
On one hand, I like the idea of being 100% responsible for reviewing my own code because it allows me to get changes in quicker.
The way we've been working is that we own a feature end-to-end rather than just a slice of it. So I understand my work, and other people understand theirs. In that context, not having code reviews makes some sense.
This was a change forced by management, I am but a peon
But part of me already misses what code reviews used to bring: learning opportunities. I can no longer rely on someone more senior than me to give me feedback, challenge my decisions, or help develop a shared understanding of the codebase.
> I can say to Claude "hey, bring me up to speed on this thing they've been building - how does it work, where is it at, and what still needs to be done?"
I think there's an opportunity to solve this differently. If you could see your teammates' conversations with their agents, you could actually follow the decisions they made and understand why. Although I appreciate that's a bit "big brother".
> What I'm recommending instead is to still build a very strong foundation in engineering fundamentals, because that's where I think we as humans offer the most value right now.
Whilst I partly agree with this, how do you actually do it in practice?
How can you possibly know what good looks like without writing good code yourself and experiencing the consequences of bad code?
I've been thinking of this as a privileged point of view, particularly from engineers who've spent more of their careers working pre-AI than post-AI.
You've had the benefit of years of experience developing the judgment needed to distinguish good engineering from bad engineering. You can now use AI effectively precisely because you've built that foundation.
But how are newer engineers supposed to develop that same judgment, especially if their workplace operates like yours?
But it's valuable to experiment with these instincts.
If we are talking about application, ethical concerns then I think it fucking sucks.
The way I see it. This is the inevitable end goal of social media. The way social media grants instant gratification is the same way LLM's do just on a much larger scale. To me both of these things are connected.
We've been exploited by tech companies using fast feedback and this to me is another level of that.
reply