bubblebeard

This is what happens when you give a new tool to people without educating them on how to use it properly. Problem with AI is that it’s so new to us all it’s difficult to find an authority on the subject.

In my experience it’s useless for fixing bugs or identifying flaws (mostly). That’s still our job, ensuring the code is generated as we intended it to be.

AI tools are most effective when you already know what you want to write, or if you need help finding alternatives to a poor solution you’ve implemented.

I’ve used MacBooks since 2008, still do since the company I work for refused to supply PC laptops running anything but Windows.

They can be great if you have a large wallet and simply want a computer that will integrate easily with your iPhone or any other Apple products. I use an iPhone myself because I’ve had bad experiences with Android devices, but every few years I try a new Android phone anyway.

Apple does not care about their end users. The hardware they retail is overprivced and the M chips are over hyped, especially with ARM PC:s now available.

Their OS was great back in 2000-2010 but has since become more and more unstable, while Linux has moved in the opposite direction. Today I would argue Linux is at least as easy to manage.

Some apps integrate better with OS X, and the magnetic charger cable is a plus. Then again, using external monitors is difficult, and if anything breaks in your nice Apple laptop it will be difficult to mend and cost and arm and a leg. All in all, I would stay away from them.

Personally, I would not yet use AI for something like this. The technology just isn’t trustworthy enough yet to get this level of control in my opinion. This is the way we’re heading of course. Better to laugh at the inevitable disasters this will cause rather than cry about it I suppose.

For developers, kerping local copies are crucial for several reasons, as is the benefits git provides (amongst other similar versioning systems) outside of simply sharing files.

Proton

Nintendo contiounsly retail older titles. Snes mini, their e-shops, re-releases. Most games originally released for the PS1 are not owned directly by Sony and many of them retail on Steam.

Ah of course, that makes sense then. What about dynamic DOM content though? Like content produced by PHP or similar. Is that filtered somehow or does this analysis expect static content?

Interesting, this is a problem I have never considered. Regarding DOM changes though, wouldn’t it make more sense to monitor files for unexpected changes instead?

Yes, but you placing your neck under that boot is a free choice. I admit, sometimes a little tricky to avoid, but a free choice still. As far as I know, there is always an option but please correct me if I am wrong.

With that said I think technology overall has become increasingly worse over the years in some ways. God, do I miss a TV without an OS.

This is something I’ve practiced myself quite a lot in recent years, and in my experience it’s so much harder while at your desk. Doing something else while letting your brain work really helps. For me, that’s usually going for a walk, taking a run in the woods, or doing some repeditive household chore.

LLM:s and CA:s are most likely here to stay. The question is how we use them correctly. I’ve tried using an LLM to help me learn new programming languages, suggest alternative solutions to some mess I’ve created, and explain things I do not understand. For all of these things, it’s been very helpful. You can’t rely on it, you have to use common sense and cross reference things you do not at least have some prior knowledge of. Just saying, it’s way easier than attempting the same using traditional search engines.

One thing it will not do is replace developers. I do not see that happening. But, in the future, our work may be a little less about syntax and more about actual problem solving. Not sure how I feel about that yet though.

I too have been thinking a lot about these same things. Great article, didn’t know about the SEO benefits. We should always strive to suppress needless overhead, if nothing else it decreases the potential attack surface.

I can relate. I’ve been using CA:s/LLM:s for various projects for the past year. It started to take the enjoyment out of it for me too. It’s a tool like any other though, just gotta figure out how to use it correctly. For me at least, I only use CA:s now to write code I already know how it should work. So I just use it to write code I’ve already written in my head, if that makes sense. And you should always review code produced by an AI very carefully.

In my limited experience, it’s better to create a full plan for what you want first, then ask your agent to build pieces of it at a time. Larger plans tend to fail because of the complexity. I will ask it in some small detail to work on part a), while I create instructions for part b). I then review the result of a), before letting it continue with b), and so on. In my experience this has worked well, but you should always review the results very carefully of course.

I think this is a good reflection of education overall. It’s easier to learn through practical application than grinding through textbooks.

Haha that was fun :D

Thanks!

While all languages have their own strengths I would recommend Rust. I’ve dabbled in multiple languages over the last few years to broaden my horizons and Rust is for many reasons my favorite.

Biggest reason is probably the way the language invites tests to be written, almost making them unavoidable.

Nobou has created some of the best music I’ve heard. Favorite track though is still ”Under the Rotting Pizza” from the FF7 slums. I listen to his music almost daily, great composer.

This looks pretty nice, seems you’ve put alot of work into this. A suggestion, if you haven’t already the following things could really help for software development tesms:

* Ability to connect issues with branches on github/bitbucket etc. (so you easily see, and quickly navigate to, related code submissions). We mostly use JIRA and this is a crucial feature for our project management.

* Ability to set a category/group for your tasks, and in these categories specify additional fields (just simple text/drop-down/radio button fields). Projects often have individual needs, and cluttered forms is a nightmare.

* Time tracking on issues.

* Parent issues which tracks the collective time spent on child tasks, to get an overview of time spent on pieces of a project.

If you can make a simple enough interface I think this product may be viable, even if the market is a bit saturated. JIRA for instance has a horrible interface, even making minor changes is a dreadful experience. Almost cost me a keyboard and screen last time I had to modify what fields should be available for a particular project.

This is well written and reflects my own ideals quite well. Especially the part about all code being a liability.

We should always take a few moments to reflect before we write anything at all. Everything unnecessary we add is just another point of failure or potential security hole.

I agree with you, I didn’t say that quite right. In my mind this is actually pretty much what I meant, though I completely see how it can be misinterpreted. Line counts, like most other design rules should really be more like guidelines. Thank you for helping me clarify myself mate!

I constantly try to improve how I write my code. The last couple of years I’ve been involved in a couple of projects that’s required rebuilding a few times over because the project managers kept changing directions and was always in a hurry.

For one project I eventually managed to convince them to let our team write a more general purpose library to conserve time in the future. And this has paid itself of several times over.

When we write code it’s important we do consider how it may be utilised in the future. Since we cannot make exact predictions it’s better to make methods as small as possible instead to reduce the amount of time spent on refactoring (since this is unavoidable). This also helps us to create solid, more future proof, tests for our business logic.

You don’t need to follow a strict set of design rules, but general guidelines is a good idea. Like trying to follow SRP, avoiding more than x nubmer of lines for your method bodies and trying to avoid nestled code.

It’s refreshing to see a young person with such sound reflections about social media.

This post made me reminisce about learning web development when I was 11. Finding resources online was tricky, especially since I didn’t always have access to the Internet. I got books from my parents, and not very good ones either, but I loved them all the same.

I miss those days, when everything was more of an adventure.

Cool! I will keep an eye on this and consider it!

Also, I noticed the website seems to not render completely properly on my phone, just something I noticed.

Congrats on the lauch!

I’ve been thinking about learning more languages over the years and your approach intrigues me. From the website it appears to be text based learning only though, is that accurate or does the app support vocal conversations as well?

This past year I’ve been trying to listen to my gut feeling more often and found that more of my endeavours are successfull, and very often when I disregard it, whatever I set out to accomplish will fail or have unforseen consequences. Funny, since there is no apparent logic to it.

Agreed. Whenever I want to play anything on my PC there is always some problem I have to deal with.

Holy crap, this guy made the future

Having been in a similar position myself, I understand how hard it can be to let go of either the one or the other. I would suggest you cut down on your hours at work (your steady job), and spend this gained freedom on something which relaxes you and which does not involve a computer or TV. For example walks, bathing, reading fiction, or some other hobby. Since your side projects generate an income this shouldn’t hurt you too much financially, and as your business grow you can cut back more hours from your day job in time.

For me, I had to take a different approach and dropped something I really cared about. But two years on I can say it was the right decision. Putting too much strain on yourself will only end badly, so I’m happy to hear you are attempting to take steps to prevent that.

Best of luck!

Think it’s great to put that on your resume. If I was to apply for a new job I’d like to believe they would be more interested in the things I’ve built and designed then my grades or past positions.