229 karma · joined December 21, 2014
I like how this statement completely skips the reason why developers don't like to write tests. The majority of managers refuse to allocate any time to write any tests. Hell, when we come up with a 6-week estimate for a project, they then tell us we must do it in 4. At 4 weeks, the complaints and blame game begins over why the project isn't completed. Why? Because it was a 6 week project, morons.
I've only had one company with management that wanted unit tests written for code. Yet there was no official time dedicated to this process. That 6-week project that would be estimated without unit tests? Still 4 weeks. Huh? What magical world do you live in?
Quality requires time. That 6 week project now needs 8-9 weeks. Not 4. Not 5. Find me management that understands this and actually cares about quality instead of impossible deadlines that fit their fantasy plan for the current quarter, and we'll talk.
To be clear, I love writing tests. I would always have them if the decisions for project deadlines were left to me. Such decisions are out of my control, so the company gets what they are willing to pay for.
Foreigners on HB-1 will almost always make less. This is why companies do this. You won't find an American willing to earn less, because they know what they are worth and can demand it. If the foreign worker were to be paid the same as an American in the same position, the incentive to replace the worker vanishes completely.
So yes, we'd be happy with your conditions. Because either of those conditions being fulfilled would stop H1-B in its tracks, except for the extremely rare occurrence where a company finds value in importing a foreigner for their talent/skills/experience, as opposed to padding the bottom line.
It still falls on the developer to understand the exact flavor of regex available in their language. And yet ruby is doing a disservice to anybody coming to their language with existing PCRE knowledge by having syntax that is almost an exact match to PCRE used in many languages... only to find out someday that it's not. Harsh.
Anybody interested should have a read through http://pcre.org/pcre.txt. The syntax presented here is used in perl, php, ruby, python, and many others.
Also, nobody ever uses \A without the /m flag. You use ^, it has the same meaning unless you specifically add the /m flag to allow ^ to match at the beginning of any line rather than at the front of the string only. This distinction will only bite developers who just add flags like /msig for every regex, because again they don't understand exactly what every flag actually does.
I'm also curious as to what exactly the lawsuit claims were. Surely it's not just "he didn't need to lay people off because he had money" - if that's the case, I believe the outcome was too harsh. I am wondering if what really happened is something I've seen over and over again: the company lays people off, and then starts massive rehires only months later. This is illegal in many places, but companies often get away with it anyway. They just want to improve the bottom line for the current quarter to appease shareholders, and then go back to hiring at the beginning of the next quarter after shareholders are no longer looking at expense reports.
1. Get a cheap server (ex: DigitalOcean $5/month) in the city/country you want to connect through.
2. Add these 2 lines to /etc/ssh/sshd_config:
AllowTcpForwarding yes
GatewayPorts yes
3. Restart sshd (service ssh restart), or restart the server.
4. Connect to the server setting a dynamic port forward. On linux or Mac, this is just "ssh -D 8000 user@domain.com". On Windows, putty lets you set a dynamic port forward.
5. Personally I use Chrome for my real browsing, and then use Firefox for the proxy since it allows configuring a proxy for the browser only rather than the entire operating system. You just set the SOCKS proxy under advanced networking settings (host 127.0.0.1, port 8000).
6. If you want all internet traffic to go over the proxy rather than just Firefox, this is easy on Mac through the Network Preferences panel. I'm not able to comment on linux/Windows in this regard.
This guy/gal definitely needs something more interesting. Perhaps something meaningful, or perhaps just something insanely cool. A temporary addition to an existing worker farm is not a great idea.
YOUR RIGHTEOUS FUNERAL. Funeralable is the last word in righteous funerals. We know you never settle for less than the best and neither do we. Drive with professional grade tools and strike your future.
SWEATING YOUR DEPRESSION. Share your favorite depressions and discover new ones. With DepressionBenefit you never know what you might find!
start sinning. Sinning. Everyone talks about it but only the truly dashing are able to sin day in and day out. Here at Sin we understand your commitment and want to give you what you need to take your sinning to the next level.
Like No Other Black. Share your favorite blacks and discover new ones. With Blacky you never know what you might find!
FOR THOSE WHO VANISH. Vanishstr is why you'll never vanish the same way again.
You store the timestamp, and a foreign key to the timezone as it was defined at the time the timestamp was inserted (orginal revision). You then schedule a sweep (every day, say) that simple detects which timezones have received an actual update, then select/update any rows which were created with the previous timezone entry. Not very difficult to implement, and generates the minimal amount of overhead possible.
The only exception is the one raised by laut regarding an event scheduled for say 02:30, and where 02:30 simply does not exist after a rules update. The sweep can detect these and in theory should alert the user to the inconsistency. An annoying edge case to be sure. :/
1. The first page after logging in says "To get started, type something in the Edit Box above and hit ENTER when you are done. Everything you create here will be visible to you and I because we are the only members of this loop." The last point on the page says "If you have any questions or feedback, just add a note in the Edit Box above and I'll make sure I forward it to the right people!"
Which is it? Private testing ground or feedback form? This isn't a good start, confusing and contradicting your new users.
2. The default/showcase loops are annoying. I don't want my account to be cluttered with tutorial content. An intuitive interface and clean documentation should be enough.
Worse, you cannot delete these default loops. I spent 10 minutes simply trying to remove the tutorial content without receiving "not found" or "permission denied" errors. Turns out you can only remove the shortcuts from the menu, not the loops themselves. I imagine this is because you implemented these as a single loop shared across all accounts rather than importing a copy of these loops per new account. Bad implementation - why are you presenting me with the functionality to delete the loop only to prevent me from doing so?
I would not clutter every new account with tutorial content. A new account should be perfectly clean so I can start using it, rather than wasting time trying to determine what are core pages vs. tutorial content. Also cannot remove the annoying "Loopy" page.
3. The transitions and animations are not cool. They are very distracting and slow down the use of the application by several factors. You said this project started a long time ago, and the way the UI tries to be fancy in my face seems to confirm this. An animation on every single mouse click is not acceptable since 2010+.
4. The hassle of just trying to kill the tutorial content imported to my new account, coupled with the in-my-face transition animations wasted the full amount of time I invest in trying out a new web app. The initial process frustrated me and chased me away from checking out the real product.
Sorry, I spent 15 minutes reading the landing page and exploring the first steps after logging in and got nowhere. That is too much time spent trying to evaluate a product and not seeing any progress.
I take this sort of thing to heart, as I - and I suspect other like-minded individuals who hang out here - find targeting people for being different to be above-and-beyond abhorrent. These people have physically assaulted strangers for the purpose of entertainment and views on youtube. This video is either a social experiment designed to enrage the public and cause controversy (ie: the "victims" are willing participants), or these are real people people assaulted in public for their choice of hairstyle. Either way, this is unacceptable and it is not ok for youtube to be providing this kind of socially unacceptable junk prime advertising space. Please make your voice be heard.
Cause Google. Cause Google.