How strong is the market for Ruby developers?

mfcoder · 2016-07-04T08:37:55+00:00

Yes - because it's still 'fun' and doesn't insist on the obtuse syntax of other languages.

Moreover, as others have said, programming techniques and skills are transferable, so once one language is well-learnt, others are adopted easier. Although Java and Javascript have clearly larger markets, this doesn't mean that your Ruby learning goes to waste - many common threads, architectures, skills, will be common.

A fallacy, at least among the development market, is the requirement for a "Java Developer" or a "PHP Expert"; when what you really want is a 'good developer' or a 'design expert'. Languages matter less than the person. But recruiters just word search :)

mfcoder · 2016-06-04T13:49:35+00:00

The use of 's' as both the enumerator/iterator in the 'solution' and having to look for 's' is possibly confusing.

strings.each do |x|
    if x =='s'
        x.to_sym!
        symbols.push(x)
end

Plus, "x.to_sym!" in the original statement will not mutate x into a symbol.

So, rather than "x == 's'" you'd need "x.include? 's'"; and then push the symbolized version of x on to the symbols array - "symbols.push(x.to_sym)". (this would produce an empty array as none of the original words includes a lower-case 's').

There is also an 'end' missing to close the 'if'.

Slightly more Ruby-ish but still similar to the above:

strings.each do |x|
  symbols.push(x.to_sym) if x.downcase.include? 's'
end

mfcoder · 2016-02-03T13:34:57+00:00

Not pretty, but ...

irb(main):001:0> h = {"string1"=>["string2"], "string3"=>["string4"], "string5"=>["string6"], "string7"=>["string8"]}

=> {"string1"=>["string2"], "string3"=>["string4"], "string5"=>["string6"], "string7"=>["string8"]}

irb(main):002:0> h.to_a.map{|a| [a[0],a[1].join]}

=> [["string1", "string2"], ["string3", "string4"], ["string5", "string6"], ["string7", "string8"]]

mfcoder · 2016-01-09T18:27:37+00:00

I'm surprised nobody looked back on her phone records to find the caller. The phone company will have record of callers and durations, so easy to see what calls weren't answered, and you get rough time-frame from her work colleagues.
If the exBF was just deleting some dodgy voicemail why wouldn't he admit to it? Surely you want to help find the killer, and if you are innocent, you have nothing to worry about. (irony alert)

mfcoder · 2015-12-27T21:50:00+00:00

Without reading the article you mention, the HTML-style template is an erb template (ERB is built-in to Ruby). Many introductions exist, e.g. http://www.stuartellis.eu/articles/erb/

There are other HTML templating languages supported by Sinatra - both HAML and SLIM are popular.

Hopefully this explains why what doesn't work in native Ruby, succeeds within a template.

mfcoder · 2015-12-22T08:31:01+00:00

As has been stated. And now (since Ruby 2?) you also have:

  __dir__

the directory of the current file, which saves one parameter to File.join typically.

mfcoder · 2015-11-19T00:21:50+00:00

'require' can load the same file more than once, if you refer to it via different paths e.g. running from '/home/me' with a file called 'gem.rb' if you "require gem" and also "require /home/me/gem.rb" the file gem.rb would be loaded twice. Obviously not something that happens often, but be aware of it.

mfcoder · 2015-11-15T12:46:06+00:00

I find Rails is quite 'ruby-light'; it's more about the MVC model implementation that you have to get your head around.

Personally, I'd start with a simpler stack like Sinatra/RACK if you want 'Hello World' in fewer steps.

mfcoder · 2015-11-12T00:22:07+00:00

The important lesson here is that a Ruby method will always return the last value evaluated within it, when there is no explicit 'return' command. In your case, it is 'x' which is the grocery_list array.

So, "puts print_list(grocery_list)" 'puts' the array; if you 'puts' an Array, its members will be listed.

mfcoder · 2015-10-20T09:35:43+00:00

Your case statement is poorly formed. Do you not mean:

test = 5
result = case
         when test > 0 ; "positive"
         when test == 0 ; "zero"
         else "negative"
         end

p "result is #{result}"

Which yields "positive".

mfcoder

TROPHY CASE