Oh wow. I can't be sure, but I'm pretty sure I'm the engineer at Pivotal that you paired with. I definitely remember you making reference to homoiconicity in lisp when we were pairing the day that Clean Architecture really clicked in your head. It was a really cool moment.
There's a lot of engineers at Pivotal, and we have a lot of projects, so maybe I can prove I worked on that codebase by referencing obscure details from it? I remember writing a LOT OF TESTS that used quotes from Wutang Clan and 36 Chambers as strings for names of entities, and a lot of references to 90s hip hop. Was this the same project?
Also, I took some time after our project (and several others) to start a small example of applying Clean Architecture in a toy Go Project, which is open sourced. Maybe check it out?
I worked at Apple on OS X server in various capacities for a few years, and really loved the experience. As an open-source user and advocate, I was really sad there because they have a very hostile and defensive position about open source (which is a very reasonable stance, in my perspective).
The fact that there aren't any prolific bloggers, open source contributors or HN commentators is an artifact that the company does not encourage anyone to do that -- in fact, they actively discourage anyone that isn't involved in open source work on Webkit or Obj-C or Swift from talking about their work. For better or worse, they still have a culture of secrecy around their products.
For what it's worth, I really enjoyed my time there and wouldn't trade it for anything else; I worked with a lot of fabulous teams, learned a lot, and got to build some really amazing stuff.
How is it reasonable for them to have a hostile and defensive position in relation to open source when so much of their software is either built upon or enabled by open source?
It's reasonable within their own worldview, which is secretive and closed. I will gladly admit, that was one of the largest driving factors for me leaving the company.
Woah, I'm pretty stoked to see someone link to my ruby implementation (neé Grubby).
It seems like the authors of Golang believe that a lot of problems with languages (refactoring, updating code to work with new libraries / versions, etc) can be solved as parsing problems. Hence, Golang has a lot of good tools for parsing text.
I'd be really delighted if you could show me a better tool for writing a parser, given a grammar in Golang than goyacc. You're absolutely right that the error reporting in yacc isn't that modern, but it's very functional, very powerful and (best of all), a lot of people have experience with it.
I certainly couldn't find any better tools in Golang when I started, but I wouldn't be surprised if someone had started one since.
What happened to the students that were culled? I can't even imagine what you'd do after getting dropped from a class you paid for (even with refund). That must be tremendously demoralizing.
Confirming that my sample size of X Bootcamp students have trouble finding jobs. It's still a competitive market, but it seems like there is an increased demand for skilled talent.
What seems really odd to me, is that the market for creative talent seems to want the cheapest, least skilled talent for some reason. I suspect this has something to do with how we as a culture value creative art labor versus programming labor.
This same comment, except replace "Svbtle" with "Facebook" back when they opened up registrations for college students outside the Ivy League. It's not too far off from the much ballyhooed Slashdot quote on the first ipod.
What an unnecessarily mean-spirited comment. Did you really need to say your first sentence?
That being said, maybe you're missing the point. Maybe svbtle wants to be a mainstream publishing platform and is just bootstrapping its initial user culture by curating the users. Maybe not.
