jonobird1

Worth it.

Guess sassy humour doesn't go far here.

No, because cats < dogs.

I work in a code base that's 5 million lines of code. It happens.

That aside, it's very useful for launching features. I have used this practice at Expedia and works well.

This is also works well for launching a feature as it's a simple on/off switch - simply git ignore the features.php file to have a different one in each environment.

That's one option.

However the issue with that is if you have multiple environments (e.g. three test environments, staging and production) and you want to have the code in a state of continuous deployment, then you use your branch for your feature, merge it in with this feature switch and when it gets to staging and you realise there's a bug, you can simply switch the feature off without it causing an issue rather than having to remove code from a merge.

Do you have a proposed solution to test understanding rather than memory?

I think possibly regular problems. E.g. with learning code, you put each question into a solution by learning the way to do it, and then implement a solution.

I could not agree more. I do however think fundamentals are important, our focus is just wrong.

The fundamentals and mentality need to change. However a wise man once taught me that it is human nature is to cheat and find easy ways out - which is why KPI's never work if they are implemented for more than six months or so. So it is necessary to keep goals fresh and change things every so often.

But more to the original point and a specific solution, more things should be taught of how to be an adult, morals, values, goals, communication, persuasion, how to do your tax etc.

I agree with that. Seems like fairly common sense. Process for a developer is to be immersed into their code and to constantly improve it so when there's no time to do that and high pressure, then it's obviously going to be lower end result quality.

Water is wet.

I'm sorry, I couldn't resist:

  var result = $('#target').text(); 
  
  $('#' + result).css({'background' : 'black', 'color' : 'white'}).text('me');

I am obviously making an educated guess based on experience here, however I believe that answer to why the stress is high is what causes reduced code quality rather than the stress itself.

For example, if you're under the pump and have unrealistic deadlines, you are more likely going to write less quality code. Not because you're trying to cut corners, but because when you have the time, you go over your code an improve it about five times before submitting it and have a freer mind to do that.

What are your thoughts?

Ha - for a minute, I had to check it wasn't April 1.

Correlation or Coincidence? I get how they got to this conclusion, but I think latter.

I came to the comments to see if I was the only one.

Cool app. I built something similar and got a bunch of traction but never did much with it: http://snippetrepo.com

I'm just getting a "400 Bad Request" for the home page (from Brisbane, Australia)

I agree with you completely. I was waiting for someone to reply with this. HTML emails convert better than almost any other marketing channel. You just can't beat it, as much as people complain about it.

Definitely. Targeted tells you if it's ended up in spam and probable reasons why it did.

With outgoing generated email, we are only a testing client at the moment until we get enough requests to do sending too.

It's the style of writing we wanted to take for our FAQ as these were the questions being asked.

At this point in time, there isn't an alternative to screenshots unless you emulate/reproduce the mailing engine for each client, but then, you can't be 100% sure what you're seeing is accurate.

An example of a new feature that we have added is sending directly from your email marketing software. Say you've set up your HTML email in MailChimp ready to send, click 'Send a test' and paste in your unique Targeted.io email address, and it'll appear in your dashboard within seconds.

I'd also like to hear this. pub/sub libraries already work pretty great so how do you differ from this?

Good document and read. Got a question about using separate CDNs for image serving. The initial HTTP connection to the host takes a while, especially with a long latency for some countries if there's no close server to the user so by splitting it up into separate image hosting servers, that may actually cause longer... love to hear thoughts on this as that's always been my thoughts?

1) Not yet 2) Not yet 3) No 4) 80% within first few minutes - same as Litmus 5) Actual screenshots, no css hacks.

At the moment, we're trying to focus on making something people love. Once we're happy, then we will release it as a white-label service.

https://targeted.io - Email testing, made by two developers. 200% growth per month. Not large in commercial standards but still large amount of users for a two man team.

I agree! As a front end dev, this has frustrated me and clients for yeaaaaars. Can't believe they're finally like 'oh, I guess we better fix it'... but it's not even turned on by default for another two versions :/

It really depends on your audience. As a general rule, you should try to make your site allowable for javascript-disabled-noobs to still be able to go through the primary functions of your site.

With that said, out of our 1m visitors a week, we have less than 0.1% with it disabled. So it's a tradeoff - how long will it take you to code the extra to allow those 0.1%, and does this require extra code and junk up.

We don't support any browsers once it gets to below 1% - aka IE7 so I don't generally go out of my way to make sure everything works for non-javascript users.

It used to be more important back in the day with the old school mobile browsers etc with the good ol' WAP (as Jonnie says)

A good point there. I've noticed over the past few years a few SaaS companies offering both monthly and yearly. I think the pre-pay could be a good idea if the LTV doesn't reach 1 year with most people so by having that pre-pay of a year, you might actually increase your LTV and thus more profit. But doing it this way exclusively over month-to-month might drop your customer signup rate.

Interesting topic and I'd love to see data around this.

This'll probably be an unpopular comment but I feel the need to point out that this is good (in the ways that made this post popular) and bad.

Bad because for the dot com company I work for, we use cookies to make sure we don't show users 'helper' tooltips more than once per 30 days and cookies is one of the better ways of doing this. It also helps us anonymously track a user location to show better search results, user currency etc.

There are many bad ways a website can use cookies, but by using a plugin like this, it'll ultimately just ruin your own user experience.

You can. It says you can still use your normal garage opener. My question is since it syncs with your server, can you open my garage? Someone can open my garage if they gain my password, my phone, or my wifi network. Is this correct?

Great question and a big one I am faced with at the moment. My thoughts for that is on each snippet, a user can provide a better way of doing this and this will either be showed back to the original user to decide if this way is better, or to have multiple options somehow.

There is no official way to ensure code validity just as there isn't with StackOverflow. But we do have a voting system and invite only community so by having this, developers can upvote and downvote based on quality and this weeds out low quality snippets and invalid/bad code.

I don't see how Uber is responsible. Correct me if I'm wrong but you wouldn't sue Android if you were texting while driving, or Google Maps if you were changing your location and had a crash.

So why would Uber be responsible if their driver was using their app? Especially if Uber says to their drivers not to use it while driving.

Interested to hear thoughts here.