sctechie
A complex recipe rewards a chef with exceptional results if they follow it perfectly, but also presents more opportunities to fail. A simple recipe might not offer the results but it should be easier to produce with a lower chance to mess up.
I think the concept generalizes here.
Obviously said person would not be an expert, but I've watched competent programmers try to learn complex languages like Haskell and Scala; there is a far more complex mental model that one needs to build before they can use those languages specifically because of all the automagic that happens in the background.
Sure, language like Haskell or Rust have a ton of great features and automagical things but I disagree that they are easier to use. One has to keep far more in your head writing Haskell than Go, a clear indicator of this is the difficulty in learning the language. Like c, you can learn Go in a weekend easily.
I am not saying those others types of languages don't have their own strengths, just that I disagree with your assessment that their features provide a lower mental load.
Abdicating responsibility for personal security to ANY 3rd party makes one less secure, period.
Now, when the government comes knocking, instead of handing over some files or access records, you'll be able turn over the user entire computer. That's the exact opposite of security to me.
If you implement a system that will increase revenues, you should be charging based on that value. Just because you're implementing some back-end system does not mean you're not having an impact on the bottom line. Sounds like you've gotten stuck into thinking your old clients are your friends. Do you not have the confidence to pursue / win new clients if you're 'key' clients disappear?
I'm probably just being ignorant lol. Can you point me to an example company offering a service like this?
Thanks.
Unless you are running a server, there is no reason to be running Linux directly on your hardware. You can, of course, but it's not a good idea.
I'm not a Mac fanboy so take that for what you will. I look at these fanboy 'bro' developers running around with overpriced hardware and laugh. You might not have the same reaction.
Your mother / father / grandmother / etc are not installing openWRT on their routers. Installing one of these CISCO home routers is pretty much hacking yourself. And, just update the firmware is not gonna work.
Try it one day, go up like 10 people and ask them what's a firmware. If the user isn't technical, you're going to get a 0/10 correct responses.
It's quite remarkable how far front and back-end JS development has come since then.
There 18k+ open source repos on github for c#: https://github.com/search?l=C%23&q=c&type=Repositori...
There are 44k+ open source repos on github for java: https://github.com/search?l=Java&q=c&type=Repositori...
I'm not even gonna bother for Asp.Net.
Now, for some real advice. 'Open Source' and microsoft don't exactly go together like peanut butter and jelly. Yes, there are some open source projects for the MS ecosystem but it's just not in the culture.
If you don't want to transfer your current skills to the Linux world, you should find a large, open source c# project and just run with it.
Good luck.
I just looked at the reddit github source. You can get to it from www.reddit.com/r/redditdev
There appears to be an installer script now along with upstart scripts to launch the services. This is vastly simpler than it was when I was using the code. I had to manually install all of the dependencies; looks like they have taken care of that.
There is also a vm floating around with an already installed reddit. I'm not going to track it down but it should be able to get you up and running in a few minutes.
There are a ton of resources online these days. I'd suggest you mainly stick to MIT OCW but many schools have online resources for programming these days. Khan academy is decent but I personally recommend you stick to official college lectures and try to work as many homework / project problems you can find.
Once you establish a solid foundation of programming, it will not take you but a week or two to build the requisite knowledge to put together professional-ish looking websites.
You need to learn javascript. You need to learn javascript. You need to learn javascript.
HTML is not a programming language, you can learn the basics in an afternoon.
CSS is a bit more difficult but you can learn it in a day or two.
Without knowing javascript, you will be hopelessly lost.
For instance, here is one: https://demo2.openerp.com/#action=114 that was posted a few comments up.
I've tried pretty much all of them listed in this thread. They all take me to the same interface that crashes.
As far as the product not being released... The guy is advertising a huge "SUCK IT SAP" website bragging about the new version of their software being released in 9 days. Not exactly an alpha version here.
I fail to see what the size of 'your' specific company has to do with anything. Anecdotal evidence is just that. 'Your' company might have the technical resources to fix bugs in open-source software, but that can't be a serious suggestion. That's like saying every enterprise out there should keep technical staff on-hand to patch the linux kernel. That's silly.
I posted a screenshot in another reply but in case you care, here's the bug that basic, and I stress that word, testing would have caught.
Easily reproducible in two seconds by simply using the interface.
I'm not going to go back and open up the developer tools to see which part of the buggy javascript UI crashed. I will say again though that the UI was throwing 'unhandled exceptions'. Do I really need to defend myself here? When is it ever a good idea for a user of a piece of software; especially ERP software which by it's very nature will interact with non-technical users constantly, to ever see an unhandled exception. Come on.
Just for fun. I went back to their website: demo1.openerp.com. It takes 2 seconds to crash their websites by interacting with it. Just click on their navigation links on the top of the page quickly.
Here is a link: http://imgur.com/fp8oW
This is an easily reproducible problem. Come on.
I liked the overall look, it's a fairly clean design. The #1 issue I have is that the boxes around each deal are scaling in size with the number of lines of text in the item description. This throws off the next element below so that nothing lines up. It might be an OCD issue on my part but I think it is distracting.
Next big thing I noticed is that your first row of deals is rather stale. The first couple I clicked on were both 2 weeks old. They were both in your highlighted section of the first row. That gives me the impression there isn't a reason to come back any soon. Maybe I just need to refresh a few times....
You should always check out your competition so....
For comparison, slickdeals.net has daily deals and pictures for each of their items, local deals on the sidebar, and a huge variety of items. I think your site needs a better 'hook' than just a 'visual UI for deal discovery'.
Your site seems to be a bit more focused on the social aspect of shopping.(sharing deals with friends) That brings up the old chicken-and-egg problem of socially based websites. You need users for a compelling product but you can't get those users without a compelling product.
I suggest you follow the founders of reddit and fake it.
http://arstechnica.com/business/2012/06/reddit-founders-made...
You honestly expect me to make a professional recommendation for software I can't even show the demo for? SAP sucks, we all know but I fail to see how your product sucks any less except for the price tag. Is that your pitch? We suck just like SAP but for less money.
My first startup was back in 2002 or so. We were doing a sort-of ebay for contractors. Today, you have similar services like Angie's List but we were creating a marketplace for contractors and sub-contractors to bid on jobs.
We had meetings with a large (back-then) communications company, had a functioning and viable product with revenues, and were weeks away from securing a large investment. I'm not mentioning names but you can pretty easily figure it out if you know your early 21st century phone tech combined with the fact we were targeting contractors.
In my honest opinion, it was a great idea. The company didn't fail because of a technical issue or bad idea. We failed because of personal issues between myself and the other founder. He decided to pursue other opportunities in his personal life and took most of the equity and product with him.
That being said, I would not trade the experience for anything.
Lessons learned:
1) Having multiple founders is not a boon. It's much better (for you personally) to be a sole founder and then bring on employees or 'co-founders' after you have the company started.
2) Leave yourself options. I put 110% of myself for over a year into this startup. My total compensation for all of my effort was under 10k. I literally put all of my eggs in that one basket of 'this is going to be a success'. Not having a plan for failure was a huge mistake on my part. This could be as simple as maintaining your contacts while working on your startup or even as complicated as looking for other jobs while working on your startup.
3) Get back to work! Failing does not make you weak, unintelligent, incompetent or anything like that. It simply means your idea and / or execution was not good enough. There's only one way to fix that, get back to work.
I don't want to get bogged down in the stats discussion because I was making a broader point and don't claim to be an expert in statistics. We could extend the example to any area where one person has more technical expertise in any certain subject than the people they are communicating with.
So, let's step outside the arena of statistics for a second. If you were teaching someone to cook, would you really explain the process using terms like a 'pinch' or a 'dash' of salt. Sure, to an expert chef or grandmother, a pinch of salt is a perfectly reasonable quantity to add to the recipe. The student just learning to cook can only guess at what that term means. That's why most recipes come with specific amounts or weights of ingredients to add, because we need a common terminology to correctly express the recipe.
Taken totally as an argument for teaching or explaining statistics, I see your point. It's far more important to discuss and quantify the significance of the change rather than simply noting that something did change and by how much.
And yeah, irony went right over my head. I blame Friday. =)
"I've had positive and negative experiences with pair programming. Your blog post only contains the positives. What are some of the negatives that braintree has experienced with your heavy emphasis on pair programming?"
I didn't mean toxic as a personal slight, sorry if you took it that way.
If the other person 'calls it the wrong thing', then how do you know they understand what you're talking about? I think it's worthwhile in that situation, if not necessary, to take a few minutes and define, specifically, what the terms you're using mean.
I simply disagree that communication is not as important as I claim. The value you bring as a statistician is not running a z-test. Any high-school kid with a computer can go to Wikipedia and be running a z-test on some data 10 minutes later. The value comes from being able to understand the results and communicate them effectively to your clients.