79
I just learned about Pkl, so take this with a grain of salt. JSON Schema and Pkl seem to have some overlap. But JSON schema is not specifically designed for handling configuration and Pkl supports other formats like YAML.
This is great. I think "instance post/comment links" would be a great addition to Lemmy core in general, but don't know how easy it would be to implement. What I have in mind is: when someone provides a link to a post/comment in another instance, it would be converted to a link the person is logged in from. I think it would be OK to leave the link as is but add an icon next to it that goes to the correct URL for that instance.
Yeah, I don't know if it's a bug or a feature. I got a similar problem before with one of my posts. I think a workaround would be to post it as a link and paste the image in the Body.
What you did with the message queu in Javascript is impressive. And I'm sure there are other efforts that solved "impossible" problems in creative ways. Creativity is important in a lot of professions and I can admit that it is probably more important in programming than, say, accounting (I hear "creative accounting" is not a good thing). However, I don't think creativity is vital in what we do. It's useful, sure. But, for example, it's not as important as critical thinking. I think the real problem is that we are a relatively new engineering discipline that is still under rapid change. The paradox is, if we look at the programming paradigms, we don't actually see many new things. We reheat the stuff from 60s/70s all the time (functional programming is a good example). But the socio-technical aspects of what we do (and how we do it) is under constant change (waterfall, agile, autonomy, etc.). And, this is probably what makes software unique. We have a very short feedback loop (as opposed to building a bridge). And I would say, that should also have its place in education.
This talk by Dave Farley sums up my thoughts about "software engineering" quite well: Taking Back “Software Engineering” – Craftsmanship is Insufficient (Piped link).
Most of the time 100% code coverage is just a waste of time.
Recently, I have seen web apps that requires an email address, then does the validation by sending an email to that address and only then allows the user to proceed with registration. That's probably the only sure way of validating an email. Users may still use disposable email addresses or short-lived aliases. But I think that's acceptable.
I agree that this is a solution looking for a problem. I still think the way he explores the limits of the language is food for thought. And the fact that this is at all possible makes C# a fun language to work with.
Video description:
In Object-Oriented Programming, objects are instances of classes and they encapsulate behavior and state - that is what every textbook on OOP is teaching. However, there's a subtle limitation in OOP when it comes to dealing with changes in the state of these objects. We often try to mitigate that limitation by applying the State design pattern, but that adds extra complexity and potential confusion to downstream components, especially when using Object-Relational Mappers (ORMs).
In this video, you will learn to recognize the fundamental limitation of Object-Oriented Programming and how Functional Programming (FP) offers an inverse perspective. Through immutability and transformations of values, FP tends to make state transitions explicit and predictable, leading to a more straightforward way of handling the issues that would otherwise be too large a burden for a corresponding object-oriented model. This requires a shift in thinking and can introduce its own challenges and learning curves. It is a fascinating topic, shedding light on the fundamental underpinnings of OOP and FP, and their practical implications in software development.
And it all depends on the problem at hand. Any of those solutions can be acceptable as long as you have a well thought out model.
You can just build a time machine and commit it before the other one. Problem solved.
By the time I checked the link, the second ad was from Netflix and I didn't see the word "open" in the job description. Is everything Netflix does open source? If not, how is it communicated that the job posting relates to working in open source? I didn't check all of them, but the list doesn't necessarily seem to deliver what it promises?
Here is my understanding of author's position: Stay away from companies like Redis and ElasticSearch. They are building software with a proprietary mindset (the fact that they have tight control over product strategy and development demonstrates this) only to realize that they are being devoured by bigger fish. It's a business model problem, not an open source problem.