Eclyps

The whole "enter your banking credentials" thing is definitely a bit weird, but I understand why they do it.

A slightly different use-case, but does anyone know of a good service that replaces the need for nightly ACH batch processing that works with good old fashion routing number and account number (and maybe some other details OTHER than banking credentials)?

Thanks for the feedback. We actually don't do a great deal of pair-programming, but it made for a short title that got the point across. I agree that positioning it as the problem was a poor choice of words on my part.

I do disagree about the framing of my colleague, however. If I were to say that I have a friend that knows a lot about geography, I don't think that it would be implied that I see myself as the more powerful individual. My entire reason for posting was to better understand how I can take my own time and apply it to helping someone else grow. Without much more context, though, I can understand how it may have come off differently.

I am a serious layman when it comes to this type of stuff, but I swear I remember reading about similar wireless power years ago. I even remember seeing a video of a lightbulb being illuminated without being attached to anything. What makes it this year's game-changing tech? Is it the WiFi aspect?

LevelSet Solutions | ONSITE Royal Oak, Michigan (Metro Detroit)

We are looking for a couple full-time Ruby/Rails developers to help us build out some new products. We're a small company with a startup culture.

What you'll do:

- Work in a team environment to build new web-based products from the ground-up.

- Collaborate with colleagues in order to make smart decisions on how to implement functionality.

- Utilize modern languages and frameworks that fit well with what you are building.

- Make good use of your high levels of freedom and flexibility to experiment with ideas before implementation.

- Continually strive to improve yourself and your team through communication and collaboration.

What you'll need:

- 2+ years of professional development experience

- Experience with Ruby/Rails

- Strong understanding of web development concepts

- Experience with modern CSS/JS languages (Sass, Typescript, etc) is a plus

- Experience designing and building RESTful APIs is a plus - A strong desire to grow as a developer

Why you should:

- We offer a competitive salary and and share company successes with the team

- We have flexible work hours and a flexible vacation policy

- Our office is located in the heart of down town Royal Oak

- All of our development is done in-house; when you have a question about existing code or functionality, you can talk with the developer that wrote it.

- We care deeply about doing "the right thing" -- both for our clients and our employees.

- We place emphasis on learning and understanding, meaning there are always opportunities to learn new languages, methodologies, frameworks, etc, as well as share what you've learned with the team.

Please reach out to me if interested - I'm the Director of Technology. asanger[at]levelsetsolutions[dot]com

I often find myself feeling the same way about using gems in ruby. It's amazing how quickly I can get something extremely functional built out by adding a handful of gems, but after a few months I look back and realize how much extra (invisible) code I've added when I really just needed a tiny sliver of the functionality provided.

Very cool! I really hate getting a bunch of visio flow charts to describe processes - those aren't things that I can easily modify without having the proper application. Does anybody know of other tools that take some sort of simple language and converts it into a flow like this?

Great suggestion. I've read his classic posts, but I haven't gone beyond those. I'll take a deeper look. Thanks.

But honestly, I have none of these problems. If one of our clients tell us any of the above, we explain to them why that's not the case, and if they continue to press us, we show them the door.

We solved that problem early on - now we're just trying to figure out the best way build cohesive dev team when we can't apply standards across the board for all of our projects.

And I'm SO thankful for this. It really makes selling a client on the service much easier, since many of them seem to only care about fancy spash pages...

I agree, for the most part. Not every setup can be open sourced, and not everybody has the capacity to contribute frequently. I lead a small tech team of 4, and we are usually pretty busy. When we're using an open-source tool that we find a bug in or need additional functionality for, I do encourage the team to submit a pull request to the source so the world at large can benefit. At this stage in our company's growth, though, it's not realistic for us to dedicate large chunks of time to random open-source projects.

Hmm... I don't doubt that this happened to you, or that it does happen often, but as someone who was in charge of a fairly successful online community with tens of thousands of community members and upwards of a million posts, I'm happy to say that I never went back. I did the same as moot in this situation - I prepped the people who I wanted to take over and made the transition slowly until I was doing almost nothing myself. Then one day I made a post and I was gone.

I didn't revoke my own access, though I doubt that I still have it (this was about 8 years ago). Even if I did have access, I certainly wouldn't want to go back and start changing things. I cared deeply about my members and fully trusted my administrative team to do what they thought was best, and sometimes that meant putting aside my own beliefs and trying something different.

It all depends on the person that's retiring, I suppose, but I wanted to offer something to counter your experiences.

I haven't used it, but read up on it after starting to use the Reform gem. It seems more geared toward forcing cleaner, more encapsulated code, which should make your rails app more maintainable in the long run. I don't think that there's any major functional changes that would impact performance.

I was not able to replicate this on Amazon's linux distro after the second patch was applied. After only the first patch, though, the server was still vulnerable.

It's updated now

Amazon's Linux distro for EC2 is still waiting for a patch.

EDIT: Finally got things updated. Bulletin can be found here: https://alas.aws.amazon.com/ALAS-2014-418.html

If yum isn't finding the update, try running "yum clean all" and then "yum update bash"

EBS has historically had a few issues, and the performance is fairly poor. I've personally never had any issues with them in the 4 years that I've used AWS.

I absolutely love visuals like this. There are things that I don't think I ever would have understood had I not seen an animated sequence of events like the ones on this site. I can forgive the heavy use of text within the images, since it makes the images easier to share without missing critical info (it IS just a wordpress site)

We ran into a couple issues (none of them significant)

1. When someone merges their branch into development for QA, it's going to be there (with or without issues) for anyone else who merges for QA after that. If the first merge has bigger issues than expected, it's a bit of a pain to roll it back and re-merge the later branch. Without the development branch as a base for our QA, we just QA things one feature/release branch at a time. This lets us easily send back branches that aren't ready for production and move on to a different branch that is before any merging takes place.

2. We weren't sure how to handle pull requests with the development branch always being there. We used to set development as our "default" branch in github, so any pull requests would be automatically merged into there. That got a bit confusing, though, as most of us were so used to merged pull requests representing a change that has already been reviewed and accepted as production-ready. And as for the merge to master, should we submit another pull request? It just seemed like an unnecessary extra step in a lot of situations.

But you are absolutely right. Different flows work for different teams and projects. I'm sure as our team evolves, so will our workflow.

The branching model that I use with my team projects used to be like this - master was always production code, development was always code ready for QA, and features would be branched off and development. It worked great for larger projects that had releases that were weeks apart, but a lot of our projects are very small and may have several minor changes go to production in a short amount of time.

We decided to kill our development branch and just create feature branches off of master. If multiple devs are working on the same project scheduled for the same release, we will create a release branch and they can branch features off of that.

An open pull request into master is how we initiate the QA process, and all remediations are discussed in there. When the pull request is merged and closed, we all get an email so we know to update our local code. It's been working really well so far for both our small and large projects.

Ouch. They crashed hard. Can't access the website either. Simply no response.

American here. I usually try to get out of the country once per year, usually for a good 14 days (10 business days). Sometimes more, sometimes less. Last year was actually the first year in many that I didn't make it out of the country, but it was more due to my own failure to plan a decent getaway and a lack of funds.

Other than my one big trip, I usually only take a Friday off here or there. Maybe only 2 or 3 of those per year.

I've always had wonderful service from TD. Haven't needed anything in the past year or so, but they always had competitive pricing and handled the my only RMA pretty painlessly...

The big difference here is that purchasing a porno magazine requires interacting with a clerk who will then verify your age and send you on your way. A better comparison would be banning the sale of all porno magazines unless the buyer registers for a porno card for his/her family (which would then provide unlimited access regardless of age).

I tend to agree that unfiltered access to all sorts of things can have an unhealthy impact on the minds of kids, but this is still the wrong way to handle it.

I would guess from Michael B. Taylor, a professor at the University of California, San Diego.

I've been using a similar setup with Pomander and the Pomander-Wordpress plugin. It's got a similar setup, but is 100% PHP-based, so I don't need to have ruby on all my servers. Been using it in production on about 15 servers for well over a year, and I'm pretty happy with it.

http://ripeworks.com/pomander/wordpress.html

Just want to chime in and say that I've used this while building multiple sites in the past, and I really dig it. At the time it was my first dive into anything rack-like, so I didn't have much to compare it to, but now that I'm in Ruby-land, I can say that it's a job well done.

Why is this on HN?

I've been harassed by recruiters who would email me on my personal email address, my work email address, my cell phone, and my boss's office phone. Virtually all of it during work hours. I guess they got my cell phone number from the signature of the email that I sent politely telling them to please stop contacting me because I am not interested in any positions, regardless of the pay. I eventually had to personally spend the time researching the company and carpet bombing their management with a legal threat upon receiving further communication from them. It shouldn't have to come to that...

Different strokes for different folks, but the gameplay always seems exciting to me because it's always human teams vs human teams. The number of hero combinations and play style variance keep things interesting, IMO.

This... doesn't seem to be something that I would expect to find front-page of HN. Did I miss something about Kroger and technology?