> "Learn C The Hard Way" is probably the closest but it's very opinionated and has its critics.
I have similar feeling too. When I looked around, I had this feeling that majority of experienced C developers may not have experienced higher level language or work in app-level and went back to C to adjust their previous experience.
Either the developers decided to abandon C in favour of high-level languages or the developers didn't like what they tasted the high-level languages enough to learn the better practice to bring it back to C. The latter group tend to go back to where they came from and stick with C.
This could be the reason why "Learn C the Hard Way" and another commenter up there posted a link as to why "Build Your Own Lisp" considered harmful/bad. On the other hand, these two materials could fit for what I'm looking for.
I glanced over "Modern C" and while I can pick up a few things better than my previous learning C experience, my experience match to your statement that most of the books are covering minutia details of the language :(.
Thank you for clarifying and confirming what I felt so far.
Recently I decided to resurrect a very old Macbook White (2008) by install FreeBSD in it.
All of my workstation (laptop/desktop) have dropbox installed and yet dropbox is not available for FreeBSD.
This is where rclone come to the rescue. There might be other software that can take the role of dropbox client but rclone gives me the flexibility of switching to other provider if I decided to do so in the future.
Oh Mircosfot's strategy is the weirdest: OCS, Lync, Skype, Skype for Business, Teams, Yammer... People are just lost.
Nayego is trying to hard build a HipChat-like client+server that is open source and based on XMPP.
https://nayego.net/ you can subscribe if you want to see a preview.
Whichever approach is fine, the end result is that less effort is made to directly support PGSQL in the long run, and you'd get to support any database back-end as a result. I only mention ORM's cause some have decent tooling (EntityFramework (Core), Diesel.rs, etc) which can be useful for generating schemas out of object models. Also in some cases ORMs are using DB abstraction libraries like for example Entity Framework is built on top of ADO .NET.
But "immutable" way of doing things have been encouraged, suggested, marked-in-stone as best-practices in most languages since 2005... am I missing something?
People have been saying that:
- Global Object is bad
- Stateless is better than Stateful
- Singleton becomes an anti-pattern
- Methods/Functions without side-effect (avoid mutation)
Nobody really mentioned to do things the Functional programming way per-se but the characteristics are there.
Immutable programming with proper immutable data structures (i.e. persistent) is very different than immutable programming in a language with lots of constructs for mutation.
You can throw "const" on things but that isn't really the same kind of immutable programming that exists in Clojure.
Because immutable programming is not just about data not changing, it's about the transformations you can do on that data without concern for the costs that would arise if you did those same transformations in a language without immutable data structures.
BI/Analytics is a tricky area with many sub-areas.
I'm relatively new to this field and I found the value of the solution is how it can connect various business workflows instead of just focused on building dashboards.
For example: typical BI tools only focused on Visualizations (most mentioned here only support that and a bit of "Insight"). This alone is not enough because business activities around BI would require forecasting/predictive and planning (and potentially Risk Assessment).
I have similar feeling too. When I looked around, I had this feeling that majority of experienced C developers may not have experienced higher level language or work in app-level and went back to C to adjust their previous experience.
Either the developers decided to abandon C in favour of high-level languages or the developers didn't like what they tasted the high-level languages enough to learn the better practice to bring it back to C. The latter group tend to go back to where they came from and stick with C.
This could be the reason why "Learn C the Hard Way" and another commenter up there posted a link as to why "Build Your Own Lisp" considered harmful/bad. On the other hand, these two materials could fit for what I'm looking for.
I glanced over "Modern C" and while I can pick up a few things better than my previous learning C experience, my experience match to your statement that most of the books are covering minutia details of the language :(.
Thank you for clarifying and confirming what I felt so far.