c++ programming

Once upon a time, the CEO of my company asked me why I did so much software engineering for my work.  My response was that software engineers were unlikely to produce what I needed in the short time frames that I had at my disposal without me spending a huge amount of time training them.

I've been exploring the possibility of frontend development for engineering simulations in Javascript.  Following on from the previous post on generating VTK XML particle data output files from our simulation, her's a new post on reading in those files in Javascript.  See my article at http://www.parresianz.com/javascript/typescript/vue/vuex/xml/reading-vtk-particles/.

-- Biswajit

Either, depending on your taste and use-case.  I prefer XML for aesthetic reasons, but that format can get verbose.  Check out my new post on how to read JSON files in your C++ code at http://www.parresianz.com/c++/json/json-input/.

-- Biswajit

Mechanics research codes are typically written by graduate students who aim to get their work done as quickly as possible. These codes are not meant to last beyond the publication of a few related papers. These files have the advantage that they can be read in quickly using an input file stream and the code for doing that can be written in minutes. 

Continuing yesterday's thread on new C++ productivity tools, here's another one on using clang-tidy to modernize your code automatically to C++11/14. Life becomes markedly easier after the code has been updated.  Check out my post at http://www.parresianz.com/c++/clang-tidy/ to see how I've integrated clang-tidy into my toolchain.

-- Biswajit

Some of you may be involved in computational work where your students develop C++ codes.  If the code is formatted well it's easier to read and understand.  With the creation of clang-format, the job of formatting (and not just indentation) can now be automated to a great extent.  For a few pointers on how-to, check out my post at http://www.parresianz.com/c++/clang-format/.

-- Biswajit