I've been meaning to make new dev projects for a while. But finding the time to sit down to just code is difficult for me these days. However I wanted to make a watch face for my new watch and I just said screw it.

Through a mix of using the Pebble SDK documentation, and referencing a few AI chatbots, mainly GPT-OSS I'm running in Alpaca, I was able to make it, make it run, and since it's in C, I was able to have no memory leaks (according to the logs).

I've uploaded the source code to Codeberg if you want to look at it, I've yet do document it, so hopefully it's not too hard to understand and not a spaghetti mess.

https://codeberg.org/the16bitgamer/poketech-dx

** Notes on my experience using AI to aid in coding **

When I was taught to coding, Google-fu was the goto way if/when the documentation fails you. However with both how old, and incomplete the Pebble SDK docs are, Google-fu wasn't helping since the info it would pull was about a decade or older and mostly out of date or hard to decipher information on Stack Overflow. I would almost say using an AI along with the actual documentation and tutorials was a necessity for me to even finish this project.

The AI wasn't perfect, endlessly gas lighting me, telling me to do over the top things for functions I already implemented, and putting me down rabbit holes going no-where. But compared to what I could get from Google, and it's ability to try and break down what the code is doing, it was a lot more helpful than I thought it would be.

In Brief:

• Two motions regarding "artificial intelligence" and Large Language Models (LLMs) were voted on among Codeberg e. V. members and passed.
• We are promising to not use any of your data to train LLM and explain what the planned Terms of Use change mean for 'vibe-coded' projects.
• We believe that LLMs endanger the free/libre software ecosystem as a whole.

The blog/news post then goes extensively into where Codeberg understands itself to be in the development landscape, and their voting results. They present their interpretation of the current software development and hardware landscape under the influence of LLMs, and the consequences they take. And how it changes not only development in general, but FOSS collaboration and projects specifically.

To us, it seems ridiculous to see projects with a single developer and virtually no users consuming as much or even more resources than some of the largest community projects on Codeberg, which operate frugal with CI/CD and storage resources. We do not believe it is reasonable for Codeberg to invest our precious donation money into hosting of large ghost projects.

cross-posted from: https://programming.dev/post/54023908

Hi!

I've never read any of Uncle Bob's books. But I have taken interest in "Clean Architecture" as it seems like a good solution to make mid to large sized projects simple to understand and maintain.

I think MVC gets too much coupling and fails at larger projects, same with n-tier. But I'm not sure about anything right now (software design is a very complicated problem after all).

So I was wondering if you friends who have used Clean Architecture in production can share your knowledge and experience with me about this design?

Is it actually good and worth investing in?

Footnote:

I'm especially weighing this architecture because Uncle Bob's writings are really hit and miss. I don't see him as a master or guru so I take everything he says with a grain of salt.

DSCI is simple yet super flexible pipeline engine to write CI code on regular programming languages, integrates with Forgejo using web hooks. Intended for small teams hosting Forgejo on single VM VPS and willing to create pipelines on regular programming languages

How many lines of code does an average Linux kernel developer produce per year?

Based on estimates of the value of the Linux kernel (around 2200 Million Euros in 2011), the size of the kernel (in 2011, version 2.6 was current, with a bit less than 20 million lines of code), and average salary of kernel developers (for Germany, one could estimate 60,000 - 80,000 EUR/year for a mid to senior embedded developer, you can go to kununu.de and look for salary statistics for larger companies like Siemens as a reference), one can estimate the lines of new code that a full-time kernel developer produces - less than 1000 lines per year:

 value=2200000000
 cost_man_year = 60000
 lines_of_code= 20000000

 person_years = value / cost_man_year
lines_per_person_per_year = lines_of_code / person_years

I get to 545 lines per person-year that way.

The interesting question is: You can obviously type that in in half an hour. What do these software developers actually do all day? ;->

Edit: Some people might get it wrong and overlook the 😉 emoticon: I absolutely don't think you should or can measure the productivity or competence of a software developer by counting the lines he or she produces! Myself, I just fixed a bug after searching one whole week for it by uncommenting a single line ... in a two year old unfinished port of a software written 15 years ago to implement and port a niche industrial protocol created 18 years ago.

There's this weird github repository

https://github.com/OOOO00000000OOOO/OOOO00000000OOOO

I noticed there was someone attempting to proxy to this repository on my site, causing it to show up in the logs. It was detected as spam but this repo doesn't look like it's built by some normal spammy company. The owner has gone through great lengths to try to stay anonymous. And I can't make out what the repo is or what it's for. Does anyone know or have any ideas?

Thanks

Why is learning C so much more generally useful than learning React? What I mean by the last point is that learning C tends to develop skills that are useful in a lot of other parts of software and tech work: if you know how to write decent C, you'll have a much easier time of understanding PostgreSQL internals, for example, while if you've learned React, it's anyone's guess as to whether or not that'll actually improve your HTML skills, for example.

I launched my first product on Product Hunt recently, and while it definitely wasn't the launch I'd imagined, it taught me a lot.

Like most first-time founders, I thought the hardest part would be finishing the product.

It wasn't.

The hardest part was getting people to discover it.

Looking back, here are my biggest takeaways:

Building a good product isn't enough. If nobody knows it exists, they can't use it. A launch lasts one day, but an audience takes months (or years) to build. I underestimated how important it is to consistently share what you're building before launch day. Comments were more valuable than upvotes. The feedback I received highlighted things I hadn't noticed while building. Marketing is a skill. I used to think marketing meant "posting a link." Now I realize it's about telling a story that makes people care. The launch wasn't the finish line. It was just another milestone.

I didn't hit the rankings I was hoping for, but I don't regret launching.

It gave me feedback, exposed weaknesses in my product and marketing, and reminded me that building a startup is a marathon, not a single event.

For those of you who've launched on Product Hunt (or any similar platform), what was the biggest lesson you learned from your first launch?