this post was submitted on 11 Jun 2023
2 points (100.0% liked)

Programming

59 readers
1 users here now

This magazine is dedicated to discussions on programming languages, software development, and coding. Whether you are a beginner programmer or an experienced developer, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as coding languages, software engineering, web development, and more. From the latest trends and frameworks to tips and tricks for debugging, this category covers a wide range of topics related to programming.

founded 2 years ago
2
Domain Knowledge or a lack thereof (2013) (jacquesmattheij.com)
submitted 1 year ago by lukem@kbin.social to c/programming@kbin.social
3 comments fedilink hide all child comments
 

I believe that a lack of domain knowledge is the root cause of a lot of very bad software that gets developed and I think that it is up to computer programmers and their managers to deal with this. Acquiring domain knowledge is an essential component in the development of software that really works well for its users.

top 3 comments
sorted by: hot top controversial new old
[–] Solaire@kbin.social 0 points 1 year ago (2 children)

as a self taught software engineer just starting my career; what do you mean by domain? I'm familiar with the term as i have spent years on learning web development as the "domain name" like in a url. But i get the sense that you may be speaking on something else? I will agree though; my boss should learn more about the web and how it works instead of relying on these frameworks to handle everything...

[–] clobble_wobble@kbin.social 2 points 1 year ago

"Domain" in this case refers to the space you're building software in. Not the website name. For simplicity its kinda like business logic. For example if youre working at DoorDash your domain would involve the rules around orders, restaurants, etc.

The term was popularized by Eric Evans' book Domain Driven Design.

[–] little_pinecone@kbin.social 1 points 1 year ago

Basically what @clobble_wobble said. For a fast introduction I recommend Domain-Driven Design Quickly (available for free). If you are interested in gathering requirements in a way that can also strengthen your understanding of the business domain, you may want to check the Event Storming technique.