billwscott

7 ms·

1.
by billwscott 13y ago
Hmmm... That is kind of humorous, given that Nicholas was a consultant for us early last year as we started this effort. His team was also at PayPal today (from Box). That article was influenced to some degree by me giving a talk at Box HQ
2.
by billwscott 13y ago
Not from Spring. Spring is a solid reasonable framework. Unfortunately the modifications were enough to cause confusion, the Windows-biased support (not good support for Mac) for the dev environment, forcing people to use Eclipse, having lo
3.
by billwscott 13y ago
will ping you.
4.
by billwscott 13y ago
I agree. I am actually not a Java hater :-) In fact I have built 4 distinct Java/JSP frameworks since 1996. You can really create some very nice frameworks with Java using some of what you say below. The Java framework at PayPal made a
5.
by billwscott 13y ago
You raise a great point. Another big challenge we have had is re-educating developers. This has been helped by finding the really sharp engineers internally and hiring new engineers that bring in the right DNA. I think we are getting to a t
6.
by billwscott 13y ago
I can assure you that I had to attack multiple fronts. Process is a big part of it (I brought in LeanUX methodology), but I can tell you (and painfully so) that if we had not changed the technology we would not be moving at anywhere near th
7.
by billwscott 13y ago
I think you are close to the mark. There are ways to work in Java/JSP environment that is pretty quick cycle time. But I will say that our experience at PayPal is the code is more terse, less files, npm so much better than maven for ma
8.
by billwscott 13y ago
We actually had the luxury of comparing parallel efforts. While Node was being readied for production we were writing our new consumer/wallet app with the PayPal Java framework (based on Spring). Meanwhile we started writing the Node v