leeluolee's comments

There are two common coding methods used in technical interviews and assessments: algorithmic coding (e.g., Leetcode) and file system-based project coding. The latter is generally considered better because it is better suited for real-world work. In the current age of assisted programming tools (e.g., ChatGP and Github Copilot), there is less need for handwriting algorithms such as inverted binary trees. However, algorithmic coding is advantageous for its time-efficiency, making it ideal for time-critical interviews.

Based on this, our team has tried a simplified TDD coding approach in technical interviews, and it has proven successful and it strikes a balance between time-saving and job-oriented . We plan to release this method to the public, as we believe that TDD is not only a testing process but also a design process. Even if the candidate is unable to complete the coding challenge within the given time, the process of designing unit tests can demonstrate their coding skills. Additionally, the interviewer can quickly adjust the requirements by modifying the test cases.

Although the demo is currently simple, our goal is clear: to explore coding methods that balance time-saving and work-oriented principles in code evaluation, particularly in a time when programming tools are rapidly evolving.

What do you think about it?

just some trick, in fact, It also use builtin `fs.readFile` to write file

Demo on codepen http://codepen.io/leeluolee/pen/KwJbov?editors=101 .

This Demo doesn't use any css property for 3d transform, It is all clip-path.

Incredible！！　

thx for kind reply.

My girl-friend also lived in Kunming, and I love the Pu'er tea, so 'puer' comes out. :)

The last two years, puer is nearly a personal tool for myself(and some clever colleague ). so the project may looks poor. if people also like it, I will do my best to make it better (document, gulp & grunt support, public api, etc) :)

So sad to learn it.

I think I should learn French Seriously

@kolev great question.

1. First，I need to say: puer is created before browser-sync (more than one year).

2. puer provide some features that browser-sync that not supported(debugger, mock request, qrCode generate etc.)

but puer is not support the user-action Synchronization that browser-sync supported.

puer is aim to providing a simple foundation for common frontend workflow .

From a user perspective. providing the bower or component support will be better, and maybe you should place the dependency(jquery) in bower.json or component.json. but not directly in git folder.

thanks for kind suggestions. regularjs and reactjs pursue a shared objective: a solution to creating view in modern front-end development, beside it, they have nothing in common. Unlike react's virtual-dom, Regularjs is based on living template(string-based parser combine with dom-based compiler make it living) to describe component's structure. it is really flexible and inituate, you can have full control on template logic, and meanwhile the view is living like angularjs.

but they all based on dirty-check: react operate on generated virtual-dom , regularjs operate on data-view binding .

Aurajs is very awesome, but it is more like a architecture than a library. Probably it is not very suitable to have contrast between them.

To be honest,128G is obviously not enough, dont make mistake like me.

http://fortawesome.github.io/ is still 404. make it be the Homepage will be better

make your site a little beautiful will help you get more suggestion on your datepair.js.