👋 Hiya! I'm Bran, and on this channel I'm creating content for software engineers. I'm a big fan of TDD, Pair Programming and Continuous Integration. I'll also talk about behavioural/soft skills and a lot of other topics which are not language/framework/programming-specific topics.
🎥 Weekly videos on Thursday.
🏢 Disclaimer: The opinions expressed on this channel are my own, and not necessarily those of my employer.
I have recently gotten into the habit of being more verbose in my C# projects and I find that when designing I write my high level code in almost plain English including variable/function/class names. And Then I go back up to the top and hit Alt+Enter then Enter on each line to "generate whatever code" and the implement that code. It forces you to write the whole project before testing, but it only codes what you need, rather than designing each part one at a time and doing full unit tests all the way up. (This is just the first pass, i usually go back and refactor a ton)
The very use of the term "code" as a synonym for the more accurate term "source description" sadly suggests a fundamental limitation in what follows.... There is no intentional or unintentional attempt to ENCRYPT or even subsequently decrypt anything whatsoever in any correct conventional sense of the term code!!!
Pair programming philosopher. You are probably very human-oriented, but software engineering is not human-oriented profession, but project-oriented. Education in the project is important, but strong leadership is needed to broadcast the knowledge and project assumptions across team members. Pair programming is a wasting of time and no results consuming a lot of energy and distracting from a real work.
The statement that code ownership is a bad idea and that everyone on the team should share the code seems like a good idea at first but there is a learning curve involved with jumping between the different pieces. We experienced this when we coded a system that spanned database code, front end code and mainframe code. Every few months we needed to refresh on MVS/TSO/JCL/DB2 ...of course if the code base is small this works well. I think pairing works best on initial design approach before coding starts. And then it would be more of a team discussion.
I'm a bit confused about why there is loose coupling between A and B in the example at 2:33. I thought there was no coupling between A and B since they are not dependent on each other. By the way, great video!
What you're neglecting is that a reader is almost certainly reading for the purpose of being able to write. That means that convenience of the writer is of nearly equal priority. Not disputing any of the recommendations just that the motivation is definitely for support of writer as well as reader.
Your productivity software reviews are great! By the way, Immersive Translate is a must-have for anyone needing translation help. It’s free and versatile.
Great Video, I have seen several times that using bad Language resulting in big problems, in a recent case I noticed that developers were using contractid and consumerid very loosely, then when the project was ready to be released a use case came up from someone who had multiple contracts (a private and a business one), however everywhere in the database the relation between consumer and contract was 1-1 instead of 1-n, in the end it costed us 2 additional sprints to fix this, and it could have been easily avoided if we agreed on more clear language. Another one, which you see a lot is that there is no clarity about language/country, at the start usually not a big issue, but when a project evolves it often becomes clear that a wrong structure is costly to fix.
So for the iife exemple, if the function is called and not saved in a variable how do you acces it's content doesn't it just get popped away after it's called ? I don't know if my question is clear.
Really great video. I am running my first post-Mortem meeting tomorrow and this has relieved some anxiety for sure. Wish me luck! Thank you for the quality content
Vulnerability is for the brave. Very nice introduction, already hooked up. I'm trying out mobp for the first time next week. Can't wait for it to happen 🎉
Great stuff Bran, as a Product Owner I always insist on empathy with the user, also from the development team (and vice versa) this really helps. I tried building a glossary for the product team and client, never thought it could be implemented into the code.
