It is not intended primarily as a learning tool or as “training wheels”. It is primarily designed for doing research on philosophy or a similarly theoretical discipline at an advanced or professional level, so it is equally suitable for grad students and professors (and anyone “in between”—like me) to use. It can be used for teaching, writing papers, writing a dissertation, writing a book, taking notes from seminars or talks, organizing your thoughts, etc. It might also be used by advanced college undergrads, for example taking an upper-division philosophy class, to take notes and study for exams (or of course writing papers). It becomes more useful, and can accommodate an ever-growing body of knowledge and understanding, the longer you use it. The more information you have added to the database, the greater the benefits it will provide in helping you organize it and understand how things are related at various levels. It is a tool for your total knowledge organization, not just for managing individual projects. My intention in designing it was to be able to retain all my notes and ideas in a well-organized fashion during and long after my dissertation, while I am getting tenure and trying to “publish, not perish”.

To see if you are writing good code, you can question yourself. how long it will take to fully transfer this project to another person? If the answer is uff, I don’t know… a few months… your code is like a magic scroll. most people can run it, but no body understand how it works. Strangely, I’ve seen several places where the IT department consist in dark wizards that craft scrolls to magically do things. The less people that understand your scroll, the more powerfully it is. Just like if life were a video game.

So make sure to write your documentation, but do not explain your spells.

This is so clear that you don’t even need comments to explain it.

Another type of comments are the ones trying to explain a spell.

Do not explain your spells, rewrite them.

Abstract the whole queryCommandState / execCommand system into a store (or some wrapper that also holds a store) that has state like isBold and canMakeBold and a makeBold() function.

The consumer component will barely change from our last example. The only difference is the way we'll get a reference to our store (since now the store is exported from the JS module):

In order to use this, we need to use a little more advanced readable store. Here's your example updated for this:

// our temperature is now a store with initial value 0 const temperature = writable(0); // now we don't need to change this function, the change will be propaged // by the store itself const getTemperature = () => { return temperature; }

Here's how we would rewrite our callback example with a store instead:

Refactor ruthlessly. Rewrite bravely.

(Nearly all of the code from D3 3.x has been rewritten.)

If I can find some time, maybe I can help pitch in somehow.

That should work, but it's a non-trivial change.

Right now major changes require a deep and broad understanding of the codebase and how things get done.

Keep in mind that third party code with references to other files also processed by the asset Pipeline (images, stylesheets, etc.), will need to be rewritten to use helpers like asset_path.

If we renamed things more often, then it probably wouldn’t be so hard to name them in the first place.

Got a bit sidetracked into refactoring the Element visitor code, so haven't actually started on the event handler stuff per se, but that'll come soon. Element stuff is starting to feel a bit more logical and easier to follow.

It is important to notice that if you are planning on making your application a PWA, you don’t have to rewrite all the logic.

So they rewrite it in pursuit of four objectives:ClaritySuccinctnessIntrigueLogicThe enemy of those objectives is being precious about what you’ve said and how you've said it.

But maybe this PR should still be merged until he finds time for that?

You are not sure which path to take between the big re-write or continuous improvements(using refactoring)

One thing is certain when it comes to navigation trends, users and designers seem to be fed up with completely hidden styles and demand options that work in similar formats on desktops and mobile devices. This might be one of the reasons a vertical pattern is trending.

This is a next iteration of mobx-react coming from introducing React hooks which simplifies a lot of internal workings of this package.

When did you last use it? Material-UI is a completely different beast to the original version, it's LEAGUES better. It's IMO one of the best written UI frameworks out there.

since you mentioned you had a bad experience with it last time. I had the same experience, but the new one is completely different from the original the quality is night and day.

With the emergence of MOOCs, game-based learning, OER, and other networked learning opportunities, researchers are ac

SOTL necessarily builds on many past traditions in higher education, including classroom and program assessment, K-12 action research, the reflective practice movement, peer review of teaching, traditional educational research, and faculty development efforts to enhance teaching and learning. Terms closely related to the scholarship of teaching and learning are good teaching (that which promotes student learning and desired outcomes and is recognized by student satisfaction, peer review, etc.) and scholarly teaching (in which teaching is regarded as an area of study and the teaching and learning knowledge base is regarded as an additional discipline in which to develop expertise).