It’s Understanding Before Coding | Tom McFarlin http://bit.ly/2xxgEAT #bacapa — Eric Gunawan (@erricgunawan) October 11, 2017 //platform.twitter.com/widgets.js Source: original article Posted by @erricgunawan via IFTTT
The Three Development Paradigms: Procedural, Object-Oriented, and Functional http://bit.ly/2yfNSVn #bacapa — Eric Gunawan (@erricgunawan) October 1, 2017 //platform.twitter.com/widgets.js Source: original article Posted by @erricgunawan via IFTTT
How to Write Better Code: The 3 Levels of Code Consistency http://bit.ly/2wmNCPL #bacapa — Eric Gunawan (@erricgunawan) September 29, 2017 //platform.twitter.com/widgets.js Source: original article Posted by @erricgunawan via IFTTT
Team-Based Pragmatism and Engineering | Tom McFarlin http://bit.ly/2wkr3eX #bacapa — Eric Gunawan (@erricgunawan) August 6, 2017 //platform.twitter.com/widgets.js Source: original article Posted by @erricgunawan via IFTTT
Mindset For Debugging (And Why We Need It) http://bit.ly/2r3Vxix #bacapa — Eric Gunawan (@erricgunawan) May 11, 2017 //platform.twitter.com/widgets.js Source: original article Posted by @erricgunawan via IFTTT
When it comes to commenting code, I’m verbose. I try to comment everything from the server-side code to the the JavaScript and even my stylesheets. Comments do help. Especially in the long run. Source: Maybe I’m Over Commenting Code (Are You?) | Tom McFarlin
Because of our familiarity with our tools, we think we’re ready to start writing code. But pseudocode goes a long way in organization and maintainability. Pseudocode still needed. Sometimes still doing it, writes on a notebook. Source: Drafting Pseudocode Before Building Anything
Build a bridge, or get in your boat and explore? Kyle Vermeulen asks Influx founder Michael De Wildt about the difference between hacking and engineering. – hack first, engineer later – new perspective. And good analogy of bridge 🌉 vs boat 🚤 Source: Hacking Vs Engineering: Not All “Bad Code” is Bad
Self-Imposed Pressure can not only take the fun out of programming, but can also result in shipping sloppy work – and I’m speaking from experience. Quality should be pursued. But Time sometimes can be the biggest enemy. Source: Self-Imposed Pressure in Programming | Tom McFarlin
BacApa 