If you’re using logs for debugging check this out:
http://blog.libinpan.com/2009/07/less-is-better-than-tail/
Cheap travels with WordPress as the foundation
https://www.indiehackers.com/businesses/scotts-cheap-flights
A todo list, React, Redux and the WordPress JSON REST API
I always wanted to create a very simple WordPress based Todo App. After putting it off for a very long time I finally had the time to look into it.
The Idea
The idea was a simple todo list that takes over your WP home page and relies on a standard to do post type for persistence. The interface should be driven by React using redux for state management. The result should be WordPress plugin that simply works without any configuration. The app works over the WordPress JSON REST API and must have a very simple UI framework.
The Parts
1.Defining the data we need to store:
- user – name and login details. For this, I cheated and simply use the WP login interface.
- Todo item – with the ability to save details on a todo. For this, I use simply used a new post type. The title being the todo, the content being further information and post meta to store the state( completed/not completed )
2. Define the todo post type which we’ll use to store todo items. Each todo item relates to a post. You will notice that it’s not anything fancy but includes a few rest API configuration to make it easy for us to call posts at a later stage.
3. Setting up the JS system. I used Webpack to manage all frontend modules. I used yarn for package management and also Bable to allow me to use ES6 syntax.
4. For the UI framework, I used spectre as it is very light: https://picturepan2.github.io/spectre/
5. For user authentication, I used the user login and then relied on the WP cookie to allow the user to create todos over the REST API.
You can find the source code to play with here, it’s a wp plugin so you can install it:
https://github.com/dwainm/wpdone
I attempted this project mainly because wanted learn about all the new frontend tools. I mostly work in PHP and doing this was very refreshing. I’m inspired to do more of these. Even if no one ever needs it, I built it coz I wanted to.
Faster VIM syntax checking with A.L.E
Is syntactic still slowing down your workflow, try A.L.E. It’s a drop in replacement for syntastic ( make sure your language is supported ):
https://github.com/w0rp/ale
It works with instantly with vim-airline.
This is the only line I’ve added to my vimrc is”
[code]
let g:ale_open_list = 1
[/code]
Vim CtrlP productivity tip
If you’re using VIM with CtrlP, here’s a tip to quickly jump to line numbers in a file:
https://coderwall.com/p/cyh7xg/ctrlp-line-number
Signature plugin for visual marks in Vim
To install this plugin with Vim Plug place the following in your .vimrc:
Plug ‘kshenoy/vim-signature’
So I tried an editor called VIM
But Why?
I’ve tried many editors, but with each of them, I found a few things I didn’t like. I always knew about VIM and I knew how to exit vim ( link for the pun ), but never thought it serious enough to work in until I saw how magically other people were using it. That’s when I started thinking about trying it out. I’ve been using it for little over a month now and this week marks the end fo the first week of using it at work.
First steps
I started googling around for the best guides on where to start. This led me to the book called Practical Vim. This is the only book a beginner needs. It covers all the most important things you need to know. It also gives you a great foundation from which to grow your very own .vimrc.
The IDE rabbit hole
On making the switch I realised that I’m seriously going to miss PhpStorm if I don’t figure out how to use VIM effectively.
Enter plugins, the magical stuff you drop in to give VIM super powers. Then enter plugin managers. The first one I tried was one called Pathogen. It worked like a charm, but then I realised I needed to add git submodules for each new plugin. The thing with vim is that you want to version control all the things so you can easily take your environment with you when switching machines. So I’ve got a plugin manager and I have that under version control, but adding so many submodules was not working out especially after the 5th plugin. I eventually switch to something that only keeps a few strings in your config called Plug.
Side note, if you want the best way to keep your dotfiles on GH see this: https://news.ycombinator.com/iterThem?id=11070797
Now that you have all the vim niceness you’ll soon realise you need a better way to manage the terminal. You need tabs, panes or some sort of split window system. There are many, many options. I looked at a few and decided on Tmux, the main reason for doing so is that it is terminal based and works on many platforms. I’m totally happy with this.
Mastery
I hear that people use this editor for years and still learn new things. I’ve seen from using it for a month that you’re alway tweaking your workflow. There’s always something new that you can add or change in your .vimrc. The best thing about VIM is that no two people use it in the same way. It should become an extension of your thoughts so that the editor gets out of your way. I’m not there yet, but I can see how my muscle memory is forming day by day.
Portability
I can now freely move between machines and take my editor with me. I has dot files: https://github.com/dwainm/dotfiles
My Struggles
In PhpStorm, Cmd + L gives you this magic wand that fixes code indentation a common coding standard issues. I miss it so much. I need to figure out how to do this in VIM.
Another struggle I have now is that I’m constantly pressing the wrong keys. This will probably get better with time. I found that I can use the numbers keys at the top fo the keyboard because I don’t know where keys 4-7 is in the dark. I’ll have to learn this.
Lastly I the struggle is just to adjust to a new workflow. One where I’m constantly tweaking things to better my productivity. I believe this will pay off over time and I’m excited about my new vim adventure.