[danielmarkbruce]

Most of the really stupid stuff written is written in good faith. It's not an excuse. There are many good books written about the financial system, accounting, etc. Rather than writing just another (incorrect) blog post, why not point to the good sources of information?

[LeanOnSheena]

I didn't say it was an excuse. There is value in articles that correctly synthesize fundamental concepts in ways that bring in new learners who are curious and open to learning. There are things the author gets right, even if they are a bit facile.

[danielmarkbruce]

You might be right. It's also possible you are wrong though. Some things have a lot of moving pieces and if one piece is off the entire thing is wrong - so you have to commit to getting a grounding that is quite thorough to have any understanding at all. I'd argue accounting is one such subject, finance is one, the legal system is one, software engineering is debatable, math isn't one.

[LeanOnSheena]

I am a CPA by training originally, but have spent most of my time in operational finance roles for PE-backed technology companies. While my work is all finance and accounting related, I mostly work with SQL and Python day to day creating internal applications for things like ARR etc.

I agree completely on your "thorough grounding" comment. I spend a lot of time explaining to finance people how tools like python, SQL, AWS stuff can be leveraged in simple ways for analytical purposes, and I spend a lot of time explaining to technology people what all the finance and accounting stuff is really about. In both cases my experience is it always comes back to explaining fundamental ideas or concepts over and over, but applying them to different situations and contexts (I do so much more confidently when explaining accounting and finance stuff since I have deeper education & experience there).

A lot of times these fundamental ideas and concepts can be explained very simply and intuitively using toy examples. the problem is it can take years and years to build up enough experience to really separate the signal from the noise and see clearly what is truly fundamental (yes that's where formal education is helpful but it can be hard to really grok absent experience imo... In the same way learning a programming language can be easier if you just try to build something).

A deep understanding of fundamental concepts is what allows you to pick apart very complex and novel problems into it's component parts. A deep understanding of fundamental concepts is one of the things that separates professionals from non-professionals in my opinion.

[bostik]

That sounds like it would make one hell of a tech talk. I have a gut feeling many readers (especially lurkers) of this very thread would gladly watch the recording.

Common and/or various ways the two groups misunderstand each other, and how you help them to anchor to the underlying base concepts? Yes please. For example, we know that interest accrues over time, but we still use shorthand for the annual interest as a step function because it makes intuitively more sense.

[danielmarkbruce]

There isn't a short cut. You just have to understand both topics.

[mylastattempt]

Going in without understanding the underlying basic concepts is, just... well let's just say I completely agree with your comment!

[em500]

Rather than leaving some oblique references to "many good books", why not provide the actual references?

[ngcc_hk]

Because not everyone can read the source. Hence might be better to say let us have better summary or take, not just post to the source guy.