everytime i see projects like this, i think that a rss implementation it wolud be so cool. Although iknow that there is not that much rss lover out there haha
The essential work of #programmingnotesfollow is building the theory of the problem + solution. Theory then enables creation of working code. In the end, the code is necessary, but it is not sufficient. Theory is indispensable. (cf. Peter Naur, 1985)
@thechelsukprofilefollowCurrently in remission from ME/CFS after 3+ years. Occasional software engineering leader, app developer, blogger, zwifter, and just being online.wrote:
@fastidious๐profilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerswrote:
Maybe implementing a subset of Markdown would be a good thing. I am thinking about bold, italics, inline code, and code block, mostly. Oh, and links.
I agree that minimalism is hard. Thatโs why the subset was explicitly recommended small. Yet, I believe it is extremely useful to have.
@fastidious๐profilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerscontinued:
I've tested MD and honestly I don't like it. Bold/italics add unnecessary noise/clutter and the font is already monospace, suited for code, so inline code & code fences are not needed. If 3rd party clients want to implement them it's fine but I'm sensitive to visual noise.
I agree with this. The core you're building is around a deliberate minimalist philosophy. I was happy to build an opinionated client for my own use-case, but it should imo stay on the fringes for those seeking it.
I assume this is not original at all at this point - but (extreme) DRY is not a good practice. My experience is that a bit of copying yourself and your colleagues in the code base often make maintenance of the code base easier.
@honey_ohs๐ฅทprofilefollowSoftware engineer. [Reluctant] Salesforce dev. Salesforceโs biggest hater.
stephenlf.devstephenlf.devImportant Thingsreplied to@asmund๐ฅทprofilefollowFather, getting older every day, technologist, enterprise architect @ work, like to explore tech. Like to keep it simple and work in the shell, write in vim, prefer Debian if I have the choice. Plays saxophone and clarinet. Enjoy motorcycle riding, photography, hiking. Christian.:
Many have adopted the term WET (write everything twice)
Uncompromising adherence to DRY.
First copy-paste? Fine by me. Second? I'll still let it slide. Third? OK, now let's think about finding a suitable refactor.
Getters and setters for everything. Certainly, if you want an object to be doing more than just getting and setting a value right now, get them in there!
Planning to add functionality later without breaking code? Stop it! That should break code! If I'm consuming a library and have been using this setter method for 2 years, I don't want it to suddenly introduce brand new validation, caching, or logging behavior!
Are getters and setters on everything even considered a good practice? To me it screams junior developer who hasnโt yet fully understood encapsulation and abstraction โ if youโre just exposing getters and setters as the interface then what is the class/module/etc providing beyond what a standard variable doesโฆ?
In the first attempt, Opus 4.7 successfully completed it and proved it. However, the solution is to enumerate all possible space and .filter out anything that doesn't qualify my definition, which is obviously not ideal (if cheating is too harsh).
I can't think of a good way to also prevent that kind of solutions and ended up prompting "please don't enumerate and filter". Opus 4.7 then reimplemented and proved the backtracking algorithm.