> "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.
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.
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).
Have we ever looked the discussion from a different perspective?
This is fact: Atlassian tend to leave the acquired product alone.
This is question: These products that Atlassian left alone, why are they not growing according to (_yours_ assumed) potential? Have we ever asked that perhaps the people behind Hipchat maxed out their potential? Or perhaps the drive is not there anymore?
What I'm asking is this: Did Atlassian do something destructive after they acquire the company? or perhaps the acquired company just simply can't live up to their potential (for any reasons except Atlassian pushing their management to the acquired company).
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.