My readings in 2015 week 26

  1. If you never hear about JavaScript source map or you want to know how to apply in details, read this post “Enhance your JavaScript debugging life with cross-browser Source Maps” from CodeProject.
  2. Run executable from Resources in C# from CodeProject, it comes to my mind that is this technique be applied for hacking?
  3. How to post list/array to MVC controller.  You can find another way to do this without JSON.
  4. Get ideas about Web Assembly.
  5. I am not sure, did I share this before; uses remoteIE to test your page in Internet Explorer on iOS, Mac OS X, and Android.
  6. Not just Google provide mobile checker, W3C did the same thing for you. Go here.
  7. I like this tool, symdiff to figure out what CSS class is not used in html markup and stylesheet.
  8. More explanations about Exception filters in C#6.0.
  9. If you are working with legacy system that logic mainly sitting in Stored Procedures in SQL server, you may be interested to read this post “Template for Managing Microsoft T-SQL Nested Transactions“.

What’s next big change coming to our life: machine replaces human?

I read a post “Humans Are Tech’s Next Big Thing—And That Could Be Risky” from, companies started to hire people to identify the best contents to their customers.  The first thing comes to my mind is machine learning; are those companies using humans to train their AI algorithms; eventually will machine be able to self-learning and do their job as human?  Right now, more companies started to use big data and machine learning algorithms to do things that previously done by humans.  What happens if 10 years later, lots of work can be done by robot with AI enabled?  Do we need to start thinking about how to ensure something that machine try to control humans in “Terminator” or “Matrix” movie should never happen?

More debate: Full stack developers?

I read a post this morning “Full stack developers: Do they really exist?” from pluralsight.  I shared my thought about full stack developers last October.  After reading this, I would like to share some of my new ideas.

People started to talk about full stack developer position/role.  I would like to ask how do you define a developer is a full-stack developer?  If you told me that, as long as they are touching codes run in both front-end and back-end; I would agree that we should have full stack developer position.  Why? As I worked in Agile environment, we are in a small team and delivers a “just enough and testable” small functionality/feature to our customers in a fast peace environment.  Therefore it is good to have full stack developers to work out the total solution.

However I think we need to be very careful and set up a reasonable expectation on this role.  My expectation are:

  1. They are confident to make code changes in different layers.
  2. They may be expert in one of the layer.
  3. They always approach the expert of the layer if they find something they are not sure or need to get advice.
  4. They love learning. (why? because there are so many things changing everyday in both front-end and back-end, so you need to learn a lot every day to catch up as much as you can).
  5. They love to share. (As new things come out so fast and everyone has limited time; they should share what they learn to the team and make the whole team grow together).

Based on what I mentioned above, I am happy to tell everyone that I am a full-stack developer and do my role very well.

What is your thoughts? Just to share.

My readings in 2015 week 25

  1. 7 essential JavaScript functions you should know; I only know “once” function and used it before.  It is good to know “debounce” function.
  2. Copy & Paste & The Web from CSS Tricks.
  3. CSS level 4 selectors.
  4. ES6 in depth: Arrow function.
  5. ES6 in depth: Symbols.  See what Symbols is used for and how.
  6. Explicit vs Implicit interface in C#;  before reading this post, I know when to use explicit interface and try to avoid; but not really understand why.  Now I know the reason.
  7. Historical Debugging, Profiling, New Diagnostic Tools in Visual Studio 2015 from Scott Hanselman.  However I think we need to have Ultimate edition to fully accessible to this feature.
  8. What is Code? from Paul Ford. This is a long reading, I read some pieces of it and it is a good sharing to other developers and what culture and attitude should a developer be.
  9. YAGNI and KISS revisited.  I think they are very useful and should always ask yourself “are you following them?”
  10. Dynamic.js; a JavaScript library to create physical-based animations.
  11. Another post talked about CSS Layers and different methodologies.
  12. Do you know what does this CSS selector “foo:lang(de)” do?  You can get answer from this post.
  13. cta.js; a light weight library to animate your “action-to-effect” paths.
  14. I like simple solution, this is an example that just use pure HTML and CSS to provide a nice footnote accessible functionality.
  15. Simple techniques for semantics and mantainable JavaScript Apps. I like the technique to use data attribute for JavaScript binding selector instead of using class and Id.

My readings in 2015 week 24

  1. Common 10 good web form design tips.
  2. Strongly typed AppSettings in ASP.Net 5.
  3. 5 reasons why you need a JavaScript style guide. I think style/convention guide is important for a dev team no matter what language you are using, once the team size is getting bigger.
  4. Protect ASP.Net applications against CSRF attacks.  Security is always a tough thing to implement and you always need to take balance between performance and it.
  5. How to use table-valued parameter in stored procedures.
  6. Animation is so cool!! check out these loading animation samples.
  7. Understanding how to use CSS content property.  Good to know the details and it will sometimes help to make your work easily, e.g. adding dividers in a sub menu.
  8. Please stop and spend few minutes to watch the video in this post “Engineers develop a computer that operates on water droplets“; it is so amazing!!! Technology is growing so fast, and I can’t imagine what is going to happen to our life in even coming 5 years.
  9. ngork, a tool that can help to open your local site to public. Read this post “how to use ngork to test a local site” to learn more about that.
  10. This post “Need for speed 2” is a good resource to improve your site performance.  Go take a look.
  11. Didn’t read it through, just want to share “Top 12 tools for creating animations with HTML5“.
  12. The fancy syntax: ES6 destructuring.
  13. React.js learning
    1. Get started with React.js tutorial
    2. React.js diff algorithm
    3. Learning React.js: Getting started and concepts
  14. Predict the output challenge for C# puzzles.

My readings in 2015 week 22

  1. Once again, BEMCSS introduction and a simple example.
  2. SEOSiteCheckup helps you to improve SEO implementation for your site.
  3. What you should know about collapsing margins, the example is very interesting that make div not collapsed by just adding a 1px padding.
  4. Animation is everywhere now; space.js helps to give your content transitions.
  5. Performant CSS Animations: It is great to learn how animations renders in the browser, what browser frame waterfall is.
  6. Do you interest web animations? if so, you may need to try Famous, a high-performance javascript library for animations.
  7. This CodePen Slack Logo give me a big surprise, it just uses some divs and CSS; and I think I need to dig in and understand this example.