prudentpomelo

Wow, this is wildly refreshing. Definitely more interesting and fun than any crud bullshit I do every day.

The stream was lagging almost as much as Tyson's fighting.

I use scholar.google.com and search for topics I am interested in. If you have access to IEEE or ACM publications then even better. Or I download books as pdfs and read those instead of scrolling hacker news ;)

I am taking a crack (again) at creating vim bindings in Javascript for HTML textarea inputs.

Please don't make me write uppercase keywords. They make my eyes bleed and hurt my hands. Why not let the syntax highlighter do the heavy lifting for you? Dress your keywords with mauve or a nice butterscotch. Don't shout at the database. Write queries as if you are texting your best friend—all lowercase. Your friend understands and so does the database.

  select      e.first_name,
              e.last_name,
              s.amount
  from        employee as e
  inner join  salary as s
              on e.id = s.employee_id;

CTEs would be such a blessing. I am stuck using mysql 5.6. So many queries would just get simpler.

Kinesis Advantage360 Keyboard. Solved so many RSI symptoms in one shot.

Take therefore no thought for the morrow: for the morrow shall take thought for the things of itself. Sufficient unto the day is the evil thereof.

- Matthew 6:34, KJV

Downloaded it this morning on my work machine and it worked like a dream. Multiline mode and vim bindings were the chefs kiss that brought it all together.

I touch type between 60-70 wpm. When I practice using source code it drops to 30. However, the most important thing I have done for my editing speed is learning vim. Vim is a cheat code in programming. The learning curve is steep. Once I got the basics down it helped eliminate most of the fatigue I would feel when editing text with the mouse.

It's honestly relieving to read all these stories because I feel like I am in the middle of this right now. Our legacy product is a mishmash of perl and php that was probably started in the early 2000s. Which I wouldn't feel bad about supporting if it wasn't for the new system that has been bolted on top of it. The previous team that started the migration is all gone and now we are halfway between two two systems that we have to support. On top of that my manager is afraid to say no to our eccentric CEO so we are flooded with new feature requests but can never get anything done because we spend so much time chasing down problems in the old system. Is there any sane way out of this? I just feel like I am white-knuckling it through every day.

This is the exact boat I am in. I always say the best thing about our codebase is the worst thing: junior developers can do whatever they want.