Sometimes you gotta do things that others don’t value highly. A long career needs you to act with good judgment. Even - sometimes - when the optics are bad.
Me too! Though I never learned how to use functions (subroutines) until I picked up C from a book later on. I still have dozens of programs I wrote back in the day in qbasic, largely based off the examples in the help system.
There were a lot of books written back then on programming. My local book shops had a section dedicated to computer programming - including all the popular programming languages of the day like C, C++, Basic (and eventually Visual Basic), Java and so on. The books were technical and specific, but they were incredibly easy to find. And back in those days book shops were everywhere.
I learned C, Java, JavaScript and Obj-C from books over the years. Those books were honestly much better resources for a beginner programmer than most online resources are today.
I hear what you’re saying, but we don’t have a word for that different thing. OS means the kernel. But OS also means the entire distribution - all of macOS, all of iOS, all of windows, Ubuntu, Android, etc.
Until we have a standard word for the ui “shell” that comes out of the box with the OS distribution, people - including me - are gonna call (and think of it) as the OS. Or part of the os. Or something like that.
Exactly. The windows operating system isn’t just the nt kernel. It’s also all the UI that comes out of the box, that sits on top of that kernel. What is iOS? An operating system. What kind of software is springboard? It’s part of iOS. Part of the operating system.
An operating system is a lot more than just the kernel.
It’s not a rust thing. Custom markup is usually implemented in rust frameworks using macros. If mixing macros and logic becomes a problem, we can change how the macros are implemented.
Yes, I saw that's it's via macros, but my point is that it reminded me of some web development practices from a much earlier era, and why we moved towards doing templates and separating app logic from presentation
The trend has been to move back to this style in general (see most modern JS frameworks). The main point is less about combining code and view, but breaking up the page into many small components and pushing data loading down into where it is needed vs up front.
Doing that enables a bunch of performance tricks like starting to steam the page before data i loaded and concurrently render components.
If you have to split your page into many small components, a separate view file for each becomes tedious.
20% slower than the M5 is still a great result. I'm still using an M1 macbook pro, and it's more than fast enough for editing film, browsing the internet and writing code.
> I am confident a human and about 5 minutes with chrome debugger would yield better results
It really depends which human. I've worked with very few engineers who were good at this sort of optimisation work. A depressingly large percentage of people who make websites for a living don't really understand how http requests are really processed, or how to read and use the chrome profiler and benchmarking tools.
Claude isn't as good at optimisation work as someone who really knows what they're doing and goes deep on a problem. But I'm optimistic that it will help plug a capability gap in teams which don't have this sort of expertise on hand.
(That said, the chance that people actually learn this stuff is going to also go down if people get used to outsourcing this work to claude.)
The job of making a website is a large part something that should be given to people who have majors in art, English, and similar things. Well, there is some value in an engineer to build the whole site, but that's more of a framework task. The vast majority of the content is not an engineering thing to do. It is a job of people who are experts in language, art, journalism, those types of things that have very little to do with engineering.
In short, if most of the people working on your website could do those things you named, you have a problem that you have hired the wrong people for the job.
I think it's genius to use this element of computer security in narrative fiction. But I think they still had comms across the ship. The cylons could still clone the captain's voice and have random crew members perform arbitrary tasks by directing people to do so over the ship's radio.
Most of the in-ship comms were 'old school' (in our terms) analogue devices. They actually had to pick up speakers. Internal speakers were wired, not radio.
reply