1. rails runtime startup time, and the insistence that things like zeus/spork/etc mean that this isn't really a problem. Glib "advice" from the peanut gallery re abstracting / splitting up your rails application to correct this, with minimal concrete examples / guidance on how to do this for a long-running app with many cross-dependencies
2. Aurynn Shaw (not sure if she's on this list?) raised this better: Rails seems slightly wedded to "every database is the same". Can make it harder to do DB-specific things without extra gems/muckery. 3. As in 1, there isn't a "Rails Way" to split up huge apps after the fact. Engines are _mentioned_, but outside of talks I haven't found a decent writeup. On a positive note, here's things I like: 1. For better or worse, I feel that Ruby and Rails have reached a point of stability at 2.x & 4.x. Rails is, and remains, the best choice for delivering a certain type of web application. Luckily enough, lots of companies in Australia want people to build that sort of web application. 2. Bundler. Oh, my god. If you've ever done lots of development in Perl or Python you'll know why I <3 bundler so much. Everything good about npm was inspired by similar functionality in bundler. Bundler makes all the problems with distributing the correct versions of libraries with your app to production / development systems go away. I can't understate this: I worked in a environment for three years where a simple addition of a new helper library or a bugfix DB driver upgrade would require a change management ticket, a two month turnaround, and 75% of the time Operations would simply say "No, we're too busy." 3. Ruby ON RAILS. Flexibility is nice, getting things done and knowing that there's a pool of developers and libraries out there that are using the same code/practices that you are makes lots of things much easier. 4. Github. (or BitBucket, but that's just a ^C ^V of Github). Every time I'm forced to use bazaar or google code or Jira or Confluence or twiki or Request Tracker I cry a little. GH just does it so much better. On Wed, Feb 26, 2014 at 1:01 PM, Gregory McIntyre <[email protected]>wrote: > == ACK WHITE MALE PRIVILEGE == > > Are you a senior Rails dev? What are the THREE things you find MOST > frustrating about your day-to-day job in the last few months? > > I'm happy to start: > > 1) No issue tracker I have ever used meets my requirements wish list, thus > I sad. How do others solve some of the problems we have, perhaps with > alternative approaches. How does your team establish other business > function's expectations of due dates or progress? > > 2) How do you effectively go about changing a code base from ubiquitous > poor quality code to extreme ubiquitous awsum++ quality code? There are > issues far broader than "refactor it" - like business justification, > timing, mixed skill teams, etc. Rescue jobs are daunting and you risk > abject failure. Currently IMHO the place to start is to retrofit fast and > complete tests, which is time consuming and undervalued by the business but > I see no better way. Is there a better way? > > 3) Non-deterministic tests are the devil. I've been nailing them down one > by one and some days it feels like it's all I do. There are a range of > causes but often it's browser-automation related. Do others encounter these > too? Are there practical tips to avoid wanting to slash your wrists? > > -Greg > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/rails-oceania. > For more options, visit https://groups.google.com/groups/opt_out. > -- Michael Pearson -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rails-oceania. For more options, visit https://groups.google.com/groups/opt_out.
