monomon

Nice. I am working on some improvements to parenscript, this might come in handy.

Not exactly the question you were asking, but there are also SDKs for closed source software. You can get a library, or just an interface definition you adapt to. It can be frustrating when you cannot peek a layer deeper into the system, and takes head banging, but it's a thing. Often, if you are a significant enough client, you can get consulting or guidance from the devs at the other end.

Nowadays a lot more business software is open source (at least partially), because it increases adoption. People found that when you remove the stops, others will flock and build stuff around.

I wanted to make something similar for my mom's garden, but yours look way better than what I had in mind. Thanks.

Another reason to use libraries is communication. Would you prefer to receive a GitCommitResult in your code, or have to parse the stdout of the subprocess? If you need complex communication with the other program, then it needs to provide rpc or some other form of inter-process communication. A library avoids this issue.

Great answer. I am also a fresh "lead" and am struggling with some aspects, but as you said, clarifying the direction and working together are the most important ones. Pairing also allows you to explain things in more depth, which aids understanding.

We don't do complex planning, usually have a few meetings and we start prototyping. So that's been a non-issue luckily as a lead. Detailed estimation can be really exhausting and takes a toll on the team.

Another cool thing I realized - you avoid the chance of some framework updating under you and breaking everything. It's a bit like pdf, it gets fixed and generally untouched.

A generator can help if you have a bunch of data that you need to convert to some html structure. I know what you are saying though, as little complexity as we can get away with, innit :)

For this reason I'm building my own generator in Common Lisp, leveraging cl-who and parenscript. All components are descibed in one place and render as web components, which allows me to attach dynamic behaviors easily.

This works great for business-card style sites, deployed to netlify.

It does look pretty damn cool. One thing that bothers me is it is in the npm ecoystem :)

Concepts like Reactive programming are widely used in web/UI contexts. The problem of connecting a UI to an underlying data set is not trivial. Several frameworks deal with this.

As was already said, concerns like Accessibility are studied academically. They have more to do with user experience than the technology, so not sure if they match your question.

Same. Writing code is FUN! However that's not the only goal there is. It's a part of the puzzle. Perhaps it takes some maturity to reach that point.

I also played with my kids on lan, and they love it. Had to discipline them a bit to water the plants 😀