Exactly, which is why I never understood why people demonize these car dealerships, yes they are an unnecessary middle man, yes they are annoying to deal with but they are only doing what is logical.
Exactly, a good friend of mine in college was recommended for a job at the NSA by one of my professors in early 2001. He went to having a heavy online presence and being a constant in our social circles to completely disappearing. His personal site went dormant, he stopped showing up on irc, abruptly dumped his long time girlfriend. My roommate bumped into the guy at a grocery store in Virginia but other than that he doesn't exist to anyone who knew him for years or online.
I know many people love Vice but I find their news coverage to be fairly vapid. Their journalism is more about generating a reaction and less about providing accurate in-depth information for the viewer.
And that is why multicopter enthusiasts, including myself, absolutely hate DJI phantoms. They are marketed as toys but they are powerful enough to do major damage and people who buy them don't even realize it. I've personally witnessed a DJI owner try to stop running propellers with his hands and another who thought it was a good idea to fly dangerously close to the heads of some girls who were sunbathing. It's gotten to the point where I seriously believe you should have to take a safety course and get a license in order to fly these things.
Not really, I live about an hour outside of the city and carpool in everyday. I can tell you first hand that Google is always late in recognizing traffic pattern changes. It's actually become a bit of a joke amongst our car pool because we get the alert once we're already stuck in traffic.
Agreed, that isn't just London, in NYC it is the same way. There are seasonal changes in traffic that can completely alter the route you should take to different parts of the city that seem illogical. Navigation systems don't currently take that into account.
Having built my own pond and faced similar issues dealing with mosquitos I'm highly skeptical that this is as effective as claimed. I've purchased cheap aeration devices that were solar powered in the past and they were not very effective. It took a few months of getting the right combination of fish, plants and a more powerful aerator to solve the problem. Also it seems like deployment of these things in thousands of small standing pools of water which breed mosquitoes wouldn't be feasible.
Sure, there are situations in which I believe there should be a certain expectation of privacy. Personal conversations like interviews are one of those situations. If I put something on facebook or linkedin I understand that there is a certain level of privacy I am giving up, it's a tradeoff many of us make for a service. Also, I have control over what I expose about myself on the internet, a recorded conversation that stays with an interviewer is not data I can control. If I have a one on one conversation with another individual or individual(s), I don't feel I should have to worry that what I'm saying is being recorded for analysis later on.
This may be a bit off topic but there really needs to be a hard line drawn on what information can be collected. The idea of recording an interview for the sake of empirical analysis is creepy as hell and I'm a bit worried anyone would think that is an appropriate thing to do.
I think you're missing out on something fairly basic. About 15%-25% (depending on which survey you trust) of small business loans were in the form of HELOCs (Home Equity Line Of Credit) pre-housing bust.
Banks no longer want to take risks on HELOCs so the qualification standards for getting them are pretty insane. As a result, business owners who used HELOCs as a way to deal with seasonal changes in demand or just as a way to have funding to get a business off of the ground no longer have that option.
Actually I'm not, I think PHP is a perfectly good language for certain things I'm just not blind to the issues with the language. I responded with my reasons that I believe that particular piece of code isn't so great.
I apologize for the late response I was looking at more of the code trying to get a better feel for what it is actually doing.
To answer your question, I'd start with why you are worried about exceptions in rendering your exceptions? Whatever you are using to render your exception should be so simple and stable that you shouldn't need to worry about it.
Also another question, from a fairly quick glance and I admit I didn't read through every last line of code, it appears as if all application execution is wrapped in a try/catch block, instead of exceptions being caught and handled closer to the potential points of failure is there a reason for this?
And one nitpick, because it was kind of a pain to follow some of the code but nested if/else statements five/six layers deep are generally kind of discouraged.
Thanks for taking time out of your weekend to respond and good luck to your team!
Don't take this the wrong way but this is still PHP and I say this as someone that's been writing in PHP since 2001, although I've largely shifted away. It didn't take me long to find some really crazy stuff like these nested try-catch blocks in:
// If execution throws an exception and then trying to render that exception
// throws another exception, we want to show the original exception, as it is
// likely the root cause of the rendering exception.
I'm not saying this is a bad project, it looks excellent and the code is pretty good but you can't escape having to do some nutty things in PHP.
That's definitely a step in the right direction. The biggest hurdle you'll have to overcome is getting your application to enforce a process, that's a lot harder than you think it is because people tend to take the path of least resistance and process is rarely that path. You'll have to get buy-in from very high levels of any organization you work with, otherwise things will devolve quickly. Either way, good luck, I'll check out your product demo when you've completed it.
There are very few places where business rules change so quickly that a rules engine is needed. Rules engines are essentially a poor practice used by businesses who don't clearly define what their goals are and stick to them. The alternative is to have a highly modularized system that is flexible enough for engineers to make changes to the code base in a timely manner, but that requires business to sit down and define the problem(s) they are trying to solve with their software. Getting that sort of time investment is difficult.
Businesses have hundreds of flexible easy systems to let end-users create quick business rule based solutions (particularly for reporting purposes) and have had them since the late 80s maybe earlier, the corporate landscape is littered with them. I wish you the best of luck, that's a tough market to get into.
In my experience, both. It starts with business users creating rules without having a clue what they are doing and it ends with the system becoming so complex that it would have been better off being written by engineers using tools more appropriate for the job.
Typically what happens is that business discovers they can now implement every last feature they desire without getting any push back from engineering so they go wild implementing new features without realizing the consequences. There is no VCS, no QA, no testing. There is no one telling them they cannot do something because it won't scale, it isn't secure or it won't be maintainable.
Their only metric for success is that they get the result they want now and the long term consequences be damned. Worse yet, every single person using the rules engine is acting independently and not as a team. There is no code review, when the rule works to their satisfaction it gets pushed into production.
At first everything works fine and people get promoted for saving money on engineering costs but then the rules start getting more complex, start becoming composed of other rules, need to have more complex actions or need to integrate with third party systems. Eventually the simple rules engine turns into a bastardized programming language that everyone adds onto and never modifies because no one understands how a modification will affect the 4000 other rules in the engine. At that point you end up having to do a complete re-write, which is something I have had the displeasure of doing in the past.
Absolutely. For simple, isolated, inconsequential tasks this works fine. The problem is rules engines always start very innocent and simple, then users request the ability to have rules call each other, then they want to store results, etc. In an ideal world this is a good thing but I have yet to hear of any place where rules engines, used at any significant scale, aren't a complete disaster.
Twitter isn't really a rules engine as it doesn't have the ability to create workflows or manage rule priority afaik but let's ignore that for a second.
Rules engines are typically a terrible idea and I say this as someone who has worked at two large corporations, one a bank, where rules engines were heavily used so they could avoid having the larger development staff they really needed. Rules engines fail miserably every single time and eventually have to be replaced.
The problem is that as time goes on people who don't know any better end up writing larger and more complex rules and workflows without an understanding of the side effects those rules generate. The end result inevitably becomes a huge mess that is extremely fragile and nearly impossible to follow.
It would be interesting to see if having some level of universal basic income and universal healthcare would be far better than having many federal, state and local departments dealing with distribution of a wide array of various government services.
There is a huge difference between those sports and football. Youth football is sponsored and run by public schools whose residents will not want to cover the financial fallout from a lawsuit. Private schools have been ending football programs for awhile now because they have even less ability to pay for a lawsuit, it's only a matter of time before public schools go the same route.
The talent pipeline for professional football is going to dry up no matter what. As more scientific evidence mounts of what we already know anecdotally lawsuits will increase along with the insurance costs for youth football. There is no stopping that.