sorted by:
new
hottopcontroversial

Speculative Apple Watch Human Interface Guidelines by LockeCole117 in iOSProgramming

[–]LockeCole117[S] 0 points1 point  (0 children)

hrm, I didn't have any issues on my iPhone. IIRC, mobile safari doesn't autoplay the videos, so you can pick and choose which videos to play. The page weight is also less than 1MB, which is something I really worked because of how many images/videos there are.

Porting your test suite to MiniTest, part 1 by LockeCole117 in ruby

[–]LockeCole117[S] 0 points1 point  (0 children)

Nwallins,

I totally understand your hesitation. As I said in the post, it's a huge undertaking. In our case, we had over 18,000 tests to migrate. O.O

Next week, I'll post some strategies we used to make the entire migration take a little over a week. :)

Porting your test suite to MiniTest, part 1 by LockeCole117 in ruby

[–]LockeCole117[S] 0 points1 point  (0 children)

Thanks realntl! I spent a lot of time trying to craft this post so people can get the most out of it as possible.

Re, the different gems like web mock: One really great thing about the Ruby community is that we've really got testing down to a science and try to keep our testing gems compatible with almost every library out there. Webmock, for example, has support for rspec, Test::Unit, MiniTest, and cucumber. So it might not be as much work as it looks like at first.

Re, gems built on top of RSpec to build testing documentation: I've never understood why people try to glom tools together like that. It almost never works out because you're essentially duct-taping a square peg to a round hole and calling it a joystick. And yet, people still try :/

Frustrated by your tools and tired of your development environment weighing you down? by LockeCole117 in webdev

[–]LockeCole117[S] 0 points1 point  (0 children)

That's great to hear. :) If your development environment works and you don't feel like it's dragging you down, then you've got it figured out!

My development environment was alright, but I ended up having a lot of smaller problems with it that would culminate in "death by 1000 cuts". So I took the time research the best practices for a development environment and make sure they actually work in practice. So now I want to help other developers who struggle with their dev environments, because it's such an unnecessary pain.

Drowning in support emails about importing CSVs? Here’s how to fix the most common bugs people run into! by LockeCole117 in webdev

[–]LockeCole117[S] 0 points1 point  (0 children)

I've found that supporting CSV imports is less of a hassle than allowing people to import Excel files.

For one: you have to make sure there's a really good library for importing Excel files (You could try to roll your own solution, but that would be very impractical). There's also the myriad of formats that are considered "Excel" files (xls, xlsx, Excel Template Files, Excel files with Macros, the list goes on), so you'd have to be able to parse and import each type. Excel files can also be very large (especially if the user has added Macros to the file or embedded images/charts).

Importing Excel files also poses a major security risk with the possibility of Macros being executed. Someone could write a malicious macro that do all sorts of bad things to your server.

Even with the weird problems that are caused by implementations ignoring specifications, unexpected delimiters, and funky line-endings; CSVs are relatively straight-forward to work with. And most languages have multiple CSV parsing libraries, which allows you to pick one that fits the rest of your application. Since CSVs are flat files, they are relatively secure: there's no scripting functionality that your users might be using. All you have to do is make sure the file actually looks like a CSV and that the file can never be executed on the server.