The idea is, I have been a software engineer for the past three decades. I REALLY love my profession (even though now, it’s pretty much sitting in meetings all day), but I love it.
I have a few projects I always wanted to do, because I just want to do them because they are useful to me. I have architected and coded hundreds of giant projects. At this point, building anything with the big web frameworks just seems exhausting. I have decided to bring each of these pet projects to fruition and then document how and why i made each decision. Every project will be using smalltalk as the data store. If the project is a website, I will use seaside as the web framework. Otherwise, I’ll use the teapot as an API interface. The series of articles I will write will be aimed at people in my position. People who are familiar with software development, and would like to read about it at a higher than tutorial level. In the end, I’ll end up with: - an application of some sort that scratches my own itch - a pile of articles outlining how i designed the tool set for the application. and in reality, it’s gonna be thinly veiled Smalltalk evangelism. But i think it might be worthwhile to talk about this stuff in a pubilc platform. > On Jan 18, 2024, at 10:34 AM, Yanni Chiu <yannix...@gmail.com> wrote: > > Can you sketch out the complexity aspects of your five projects? Is this all > for learning, or are they “production” applications? Do you want to gain > experience with different ways to persist data, or are you just thinking that > you have to use different ways due to project complexity? It might be ---- peace, sergio photographer, journalist, visionary Public Key: https://pgp.key-server.io/pks/lookup?op=get&search=0x69B08F58923AB3A2 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV @sergio_101@mastodon.social https://sergio101.com http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101
