{"componentChunkName":"component---src-templates-blog-post-js","path":"/install-prism-plugin","result":{"data":{"markdownRemark":{"html":"

Install Prism Plugin

\n

Prism is a lightweight, extensible syntax highlighter. Gatsby JS comes with a well integrated plugin. Follow the instruction then you can render code snippets in a nice looking way.

\n

Here is an example. The follwing markdown

\n
```javascript\n// In your gatsby-config.js\nplugins: [\n  {\n    resolve: `gatsby-transformer-remark`,\n    options: {\n      plugins: [\n        `gatsby-remark-prismjs`,\n      ]\n    }\n  }\n]
\n

will become

\n
// In your gatsby-config.js\nplugins: [\n  {\n    resolve: `gatsby-transformer-remark`,\n    options: {\n      plugins: [\n        `gatsby-remark-prismjs`,\n      ]\n    }\n  }\n]
\n

And we can try some typescript code as well.

\n
export interface Person {\n    name: string,\n    age: number\n}\n\nlet john = {\n    name: \"John\",\n    age: 39\n} as Person;
","frontmatter":{"date":"August 23, 2018","path":"/install-prism-plugin","tags":["gatsbyjs","prismjs"],"title":"Install Prism Plugin"}}},"pageContext":{"prev":{"excerpt":"Quarkus And Spring I spent few days learning different Micro-service frameworks. The first framework I choose is actually , but once I start investigating , I realized one thing that seems important to me. It looks like , but it's another . Once you…","html":"

Quarkus And Spring

\n

I spent few days learning different Micro-service frameworks. The first framework I choose is actually Micronaut, but once I start investigating Micronaut, I realized one thing that seems important to me. It looks like Spring, but it's another Spring. Once you locked in the eco-system. it's hard to get out. So I start looking for something that is more standard so I choose Quarkus, backed by RedHat that implements Eclipse MicroProfile, that should make it relatively easy to port to other platform that also support MicroProfile.

\n

The more I use, the more I like it, even it is still a new framework.

\n

Things I like Quarkus so far

\n\n

Things I thing it can improve

\n","id":"9ea1209c-d7e8-549b-91b5-311f639340a9","timeToRead":1,"frontmatter":{"date":"2020-03-02T04:18:56.083Z","path":"/quarkus-and-spring","tags":["quarkus","spring","microservice","mircoprofile"],"title":"Quarkus And Spring"}},"next":{"excerpt":"Feature Toggle And Regression It is OK to violate DRY principls to copy the code when working on a new feature that is high couple to old behaviour. As a professional software engineer, I kind of strickly obey the DRY principals, and don't want to…","html":"

Feature Toggle And Regression

\n

It is OK to violate DRY principls to copy the code when working on a new feature that is high couple to old behaviour.

\n

As a professional software engineer, I kind of strickly obey the DRY principals, and don't want to introduce any regression. But this could end up you can not easily to write a clean code and refactor. You need to branch your code in the exisitng code base.

\n

Copy the exisitng code will ease your regresion nightmare. Once toggle is removed, the old code will disappear, so you are not violating DRY prinsipal any more. But you need to make sure the toggle will be removed and old behaviour will not needed. Otherwise, you could put yourself in a situation that DRY try to address, maintain multiple codes that basically indentical.

","id":"542576fb-98c8-5d3b-ae45-751baaf7b524","timeToRead":1,"frontmatter":{"date":"2018-08-09T21:12:26.441Z","path":"/feature-toggle-and-regression","tags":["dry","feature-toogle","regression"],"title":"Feature Toggle And Regression"}}}}}