vim-rails is enabled only if config/environment.rb is present in the Rails working directory. At work, we have an engine based working directory that does not contain this file (as there’s an embedded application within the engine.) To enable vim-rails, I need to do: echo "load ::File.expand_path('../../embedded-app/config/environment.rb',__FILE__)" >> config/environment.rb mkdir -p .git/info echo "config/environment.rb" >> .git/info/exclude Within the repo to enable vim-rails support.
Spiro Sideris writes: To write understandable code, always ask the question of who your audience is. What level of experience do they have? What are the prerequisites they should know before reading this function? There are even differences in the semantics between programming languages, so knowing the best practices, and the language coding style, will ensure you are writing readable code for developers in that language. Writing Code Like a Mathematical Proof
Rule 1. You can’t tell where a program is going to spend its time. Bottlenecks occur in surprising places, so don’t try to second guess and put in a speed hack until you’ve proven that’s where the bottleneck is. Rule 2. Measure. Don’t tune for speed until you’ve measured, and even then don’t unless one part of the code overwhelms the rest. Rule 3. Fancy algorithms are slow when n is small, and n is usually small.
From my perspective, Mozilla has put together the best recommendations for
both server and client configurations. For now, I’m concentrating on the
client configuration (within
~/.ssh/config and my SSH keys.)
Back in August I rebuilt the site using Jekyll and Minimal Mistakes for the theme. This worked great for a few months, but even a small site was taking too long to generate (10-15 seconds!) While 15 seconds per build isn’t much, it was just enough friction to make updating not fun. That’s when I remembered that Julia Evan’s had posted her experience switching to Hugo. A zero second build time was very attractive!
As a remote worker in a rural community, I’ve found it difficult to find other technology workers in the area. After speaking with Brett, we decided to start the Norfolk Techies Slack group. If you’re a technology worker in the Norfolk County area please contact Brett or myself for an invitation link.
Sam Schillace writes: I was talking with the engineering team at Box about what I’ve learned along this journey, and what came out of that conversation were my personal engineering principals. These aren’t rules or engineering guidelines. They’re simply the principles that I pay attention to when I write and operate code. These include: Be paranoid. Don’t lie to the computer. Keep it simple. First rule of optimizing: don’t.
Jim Bird writes: Using run-time flags like this isn’t a new idea, certainly not invented at Flickr or Facebook. Using flags and conditional statements to offer different experiences to different users or to turn on code incrementally is something that many people have been practicing for a long time. And doing this in mainline code to avoid branching is in many ways a step back to the way that people built software 20+ years ago when we didn’t have reliable and easy to use code management systems.
Never say: “Do as I say, don’t do as I do” Create An Environment Of Play Manage What They Consume Interrupt Negative Self-Talk Actively Remind them to be Grateful Make Rigid Routine Days Mandatory Encouraging Curiosity and Asking Questions Encourage Independence From Diaper Years Never Teach Them Ugly Ideas About Money Let Them Have A J.O.B. Answer Their Questions With A Question Pour On The Hugs and Kisses 12 Ways To Instill Your Kid With An Entrepreneurial Mindset