By default AngularJS and Blade conflict with the way variables are called. Both use a double curly bracket {{ var }} syntax. There are a few workarounds such as changing Angular’s or Blade’s delimiters but an easier method is available.
Inside blade prefix Angular echo variables with the at “@“ symbol. Here is an example:
This will prevent blade from parsing it but will be correct when sent to the browser.
Nice and simple!
In my post yesterday about Ulysses III I posted a screenshot of my customized theme. Since then I’ve had a few requests for me to release the theme and I’m happy to oblige, you can now find the following two themes in their styles exchange.
Here they are in all their glory.
Most of my focus was on the dark styles but the beauty of Ulysses is that customizing them is super easy.
To get your theme to look just like mine I used the following Ulysses settings:
I hope you enjoy these and if you have any questions just ask in the comments below.
I’m fascinated by writing apps. So much in fact that I believe I have purchased every one that has ever been made. I’ve even tried using development apps like Sublime and PhpEdit but nothing ever felt just right. I can’t explain it but it was always some little issue that drove me crazy.
This all changed when I found an app called Ulysses III. At the core it’s a nice markdown writing app much like some of the others on the market. But that is where the similarities end. It is minimal yet extremely powerful.
What I enjoy most is the sidebar and the library of all your files, sheets as they call them. I’ve seen a few apps do this but something about having everything together in one app makes me feel good.
All files are backed up to iCloud and are available on the Mac and iOS via their free companion app Daedalus Touch. I do most of my writing on the Mac but having the iOS app is great for jotting down quick notes while on the go.
Where the app shines is in those little features that are out of the way unless you need them. They have mastered making a simple app.
A simple app isn’t simple by virtue of having fewer options, a simple app is simple because of usability. — Ben Brooks
From the folder level you can set goals, see statistics, and add custom/smart folders. These same things can be done on a sheet level, as well as custom tags.
The writing environment is also nice. It supports markdown with some added features such as comments, notes, and annotations. You can really do some series writing in it. In fact you can even split a sheet which would come in handy when writing your next novel.
The export is another great thing. You can export as markdown to your clipboard, send to marked app, export a PDF, email, or iBooks. They even have a styles exchange where you can install different themes for both exporting and the writing environment. Here is my current customized theme:
Along with all these it even has a quick open (command + o) which is similar to Sublimes command + p or PhpStorm’s recent files. Fully searchable.
Ulysses III is an IDE for all your writing.
———
So far I’ve only used it for blogging but I am planning on releasing the next volume of the Artisan Files e-book with it. I feel like with the export templates and the feature set it has, I can generate a nice looking e-book. Not only that but save me the headache of using iBooks. I never could fully figure that app out. 🙂
The only downside is the export doesn’t appear to support mobi files. I am hoping an app like Calibre can help here. Only time will tell.
I’m very pleased with this app and on my list it’s a must have.
As a developer one of the best ways of giving back, beyond releasing code, is by writing about your experiences. Think about all the people you follow on social media. Chances are you follow the ones that are sharing knowledge and inspire you.
I love this part of the industry but a lot of times I see developers make common copywriting mistakes in their blog posts.
What good is a tutorial or article if it’s glanced over or never found?
In this post I’m going to outline some of the tips I’ve picked up and mistakes I’ve made in the past.
Your technical blog post needs structure. Two common methods are:
The first method is what a lot of technical articles use. It has a tendency to come out pretty dry and boring.
I like the second method better as it makes it easier for you to set up a story. The basics is to start your article by focusing on the pain or problem, then a dream of what you want to accomplish, and finally the actual fix or solution.
As a developer this is much of our entire day, so moving it into a story form is easy and should come naturally.
Have you spent hours crafting a blog post, editing it, making sure its perfect, only to have it be a big flop? I have, numerous times and one of the common problems is the title. In fact much has been written about crafting the perfect title and it could be argued it’s the most important part of your article.
For us developers the best titles are those that other developers will be searching for. For example on my site “Switching to PhpStorm” and “Setting up Gulp, Bower, Bootstrap Sass, & FontAwesome” are my most popular posts. The only reason is because they appear in search engines.
Those two posts I threw together fairly quick and the ones I’ve spent the most time on hardly get any traffic.
I touched on the introduction previously but it needs it’s own section. The introduction is the second most important part. This is where you inform readers on what to expect and set everything up.
I come across lots of articles where this is missing or just generic filler. It doesn’t draw me in and at that point I just scan the headings for sections that sound interesting.
Including headings and scannable break points is another important feature. On the web readers quickly scan articles so you need a break to draw them into each section. Some examples are of course headings, blockquotes, lists, and images.
It’s also important to write clearly and keep your style consistent. In technical writing that means keeping your naming the same. A common example is writing the word JavaScript. Don’t mix between using js and JavaScript. Stick with one.
Another tip is to run your text through an app like hemingway. For web writing keep everything at a grade nine reading level or lower. Using small words helps readers where English isn’t their primary language, and makes your content more consumable.
In copywriting the closing is typically your call to action. Most developers aren’t selling anything so this is a great spot to ask for comments, connect via social media, or recap the article.
I hope these tips on the structure, title, and content help you the next time you are writing a technical article. Now go and write about that problem you solved today. I’m sure it would be a benefit to others.
I had been waiting all day for this talk and at 2:50 p.m. I rushed into a room filled with six long tables. I took a seat on the front row so I wouldn’t miss anything.
Waiting to greet me was an index card, a pen, and a sticker. All branded with the speakers avatar. It was an impressive first impression!
I have followed Yitzchok Willroth, @coderabbi, over the past year on social media. We’ve had enough interactions that I consider him a friend, although never meeting in person. Anytime one of my friends are about to give a presentation I am nervous for them. I want more than anything for their talk to go well.
As I looked up to a small black and grey stage, I seen Yitz standing behind the podium. He was performing pre-talk preperations and getting his computer hooked up and microphone wired in.
He was dressed in a white button up shirt, black dress pants, and he looked a little nervous. As he wiped the sweat from his forehead, I knew the presentation was about to begin.
To be honest I wasn’t exactly sure what the next 45 minutes was going to be like. The title of the talk was “Talmudic Maxims to Maximize Your Growth as a Software Developer” which are foreign words to my vocabulary.
Less than two minutes into the talk, my anxiousness was quickly put aside. It was the best talk of the conference and it had everything a speaker needs. A story line, stage presence, and he kept the attendees listening intently to all the guidance.
The talk was not only for software development but for life itself. I believe the big takeaway is going to be different for each person, so I will not cover the presentation content. I am hoping this talk becomes the keynote at the next conference you attend. It was that good.
I feel like I got to see a rookie throw a touchdown on the first play of the first game. He gets it.
Just because you’re dealing with a scholarly discipline that’s usually reported in a style of dry pedantry is no reason why you shouldn’t write in good fresh English. William Zinsser
Continue reading “Make your tutorials pop by avoiding dry pedantry”
I got my start in tech almost two decades ago. Back then the landscape was much different, but I feel in love, and made it my career choice.
I found a friend, started selling software and doing custom development. Back then no one used the fancy term bootstrapper and I was just a partner in a small business, like thousands of others.
Flash forward a lot of years and I found myself getting a full time job. Something I hadn’t done in such a long time that it was a shock. I went from setting my own hours, working a few minutes away, and wearing many hats. To having to drive an hour each day, a set schedule, limited vacation, someone else making decisions, and having to focus on just code.
On one hand it was easier. Being an owner, all these questions stayed in the back of my mind, and at all hours:
If you notice almost everything in my list was around money. Being a bootstrapper without a large net worth is stressful. A few bad months without proper savings can hurt you in a bad way. I had a hard time with the income being unstable from month to month. This stress compounded when I had kids.
Going to a full time job took away most of that. I could depend on a paycheck, had insurance coverage, and taxes would be handled like the rest of the population.
That doesn’t mean it wasn’t without issues. Mostly driving into an office. I took a job in the next city over, on a good day about 30 minutes one way, but that hour a day really adds up.
My kids go to bed between 7 and 8 which meant I would only get to see them for an hour or two and I didn’t like that at all. Especially in the toddler stage when they are doing all the good stuff for the first time.
I was able to eliminate the drive by getting a job working remote. Which also included the side benefit of being home for lunch and to be a big part of my kids lives.
Working from home is not without challenges. For me it’s mostly training the kids that during work hours they are to not be to loud and keep interruptions to a minimum. I would say that works 90% of the time but I do make an exception after school. Having them hold in their excitement until after work is impossible.
The other thing I’ve heard about working from home is isolation. This hasn’t affected me and I assume it’s because of my personality. I prefer not to talk and chatting with friends via online messaging is just as well with me. You could say this is my introversion showing it’s true colors.
All in all I’m happy with my experiences on both sides. One benefit is now as an employee I have a pretty good understanding of the business side, and how when you work for a bootstrapper you are an integral part of the company.
