Thinking about software engineering
nintil.com
Thinking about software engineering
1–10 of 21 posts
Re: Thinking about software engineering
#2Hopefully the article is enjoyable to those that haven't read his blog, I stumbled upon it because I'm a fan on nintil in general, but I think it's interesting even if you aren't familiar with his other writings.
Re: Thinking about software engineering
#3Hopefully the article is enjoyable to those that haven't read his blog, I stumbled upon it because I'm a fan on nintil in general, but I think it's interesting even if you aren't familiar with his other writings.
I second this , this blog is gold.
Re: Thinking about software engineering
#4What would be the best programming language matching his criteria(flexible, concise, static types, DSLs)?
Re: Thinking about software engineering
#5What would be the best programming language matching his criteria(flexible, concise, static types, DSLs)?
OCaml seems like it hits all of those well.
Re: Thinking about software engineering
#6What would be the best programming language matching his criteria(flexible, concise, static types, DSLs)?
If those are the only criteria, my take would be Haskell.
Re: Thinking about software engineering
#7Hopefully the article is enjoyable to those that haven't read his blog, I stumbled upon it because I'm a fan on nintil in general, but I think it's interesting even if you aren't familiar with his other writings.
Thank's for sharing! I hadn't heard of him until now. Love the suggestions for how to have better meetings especially.
Re: Thinking about software engineering
#8What would be the best programming language matching his criteria(flexible, concise, static types, DSLs)?
most typed functional languages seem to fit: ocaml, f#, purescript, haskell
Re: Thinking about software engineering
#9Thing is execution of Software Engineering is highly opinionated. People with diverse cultures have different needs & skills. It is very difficult to write one doc that doesn’t raise questions or meetings. I guess we can minimize them by holistically understanding the use of the doc we’re creating.
Re: Thinking about software engineering
#10> Lack of ownership is the root of all evil
This is something I battle at every job. Every meeting should include as a documented outcome: who owns this gap we just identified?