Bird | Software, Electrical, Mechanical, DevOps, and Data Engineers | Santa Monica/Venice, CA (Los Angeles area) | ONSITE https://www.bird.co/careers
Bird operates a fleet of electric scooters that provide a quick and convenient short trip transportation option. Just find a scooter, scan it with your phone, and off you go! When you arrive, park it anywhere like you would a bike, end your ride, and you're done. We're expanding rapidly, so if you live in the LA area, you've probably seen them around!
We're just getting started here, so there's the opportunity to have a massive impact. Our growing engineering team is looking to add talent in almost all engineering fields and levels of experience. We're looking to hire engineers specializing in DevOps, Backend, Data and Data Science, Electrical, Embedded/Firmware, Mechanical, Mobile, and QA. If the idea of working with a talented and professional engineering organization, and building something that you will see people enjoying around you every single day is appealing, we want to hear from you!
You can email me at david@bird.co, reply to me here, or get in touch through our (slightly out of date) careers page, linked above.
Bird | Software, Electrical, Mechanical, DevOps, and Data Engineers | Santa Monica/Venice, CA (Los Angeles area) | ONSITE https://www.bird.co/careers
Bird operates a fleet of electric scooters that provide a quick and convenient short trip transportation option. Just find a scooter, scan it with your phone, and off you go! When you arrive, park it anywhere like you would a bike, end your ride, and you're done. We're expanding rapidly, so if you live in the LA area, you've probably seen them around!
We're just getting started here, so there's the opportunity to have a massive impact. Our growing engineering team is looking to add talent in almost all engineering fields and levels of experience. We're looking to hire engineers specializing in DevOps, Backend, Data and Data Science, Electrical, Embedded/Firmware, Mechanical, Mobile, and QA. If the idea of working with a talented and professional engineering organization, and building something that you will see people enjoying around you every single day is appealing, we want to hear from you!
You can email me at david@bird.co, reply to me here, or get in touch through our (slightly out of date) careers page, linked above.
Jose Ortega y Gasset was a relative of mine, and I asked this as a kid. What I was told (by my grandmother, his niece) is that it is sometimes done when there's a weirdness in the combination of the two last names that would make it ambiguous, such as someone who has a compound first name like Jose-Maria that makes it harder to tell where a first name/last name breaks, or in this case, where it results in a repeated sound (ga-ga) that feels weird to say. But I have not found any corroboration of this online.
I used to live on the street in Madrid named after your great-great uncle, and I always wondered why he was named like that. The explanation make sense!
Thanks for answering. As a Spanish speaker this makes sense. My dad is from Mexico and no one in my entire family has this so maybe it's limited more to Spain?
It was until the 19th century, when it was somewhat normalized (census, etc.). Since the 20th century naming in Spain is pretty the same as Mexico and other Spanish speaking countries. All my known relatives names/surnames are without "y".
Yep, we are talking about someone who was born in the 1880s. Though as a counterexample in the modern age, there is a well-known Spanish economist at Columbia named Xavier Sala i Martin.
Oh yes, there's a few differences. For example, Clojure also has a radix notation for integers (as in 16rFF = 255) that doesn't seem to be a part of EDN. I had assumed that Clojure would cast the deciding vote in these sorts of things, but now that I think about it, maybe not.
I'm trying to think of what anti-macros Clojure talk by a "key presenter" he might be referring to. I'm only familiar with the talks from Clojure/conj, so the only one that I can think of is Christophe Grand's (not= DSLs macros) talk from 2010[1]. If so, I think his summary mischaracterizes the content of that talk, but it could be another talk he's thinking of.
I think Christophe's is the talk, and Yegge seriously misunderstood it, if he even bothered to watch it. Christophe's point was that basing the underpinnings of a DSL on macros was frequently a mistake, vs a data + functions approach that "leads to greater dynamicity". It is inarguable that macros are less flexible than functions (e.g. they can't be applied) and less composable. Christophe's argument wasn't against macros, but that they should be the last layer of sugar, not the core mechanism of a DSL. This approach has been advocated and practiced by Lispers forever. Ditto the advice to not use a macro when a function will do.
And for Yegge to imply that more serious Clojure devs like Christophe are macro averse because they are afraid they might not understand someone else's macro code shows his complete lack of familiarity with Christophe's macro skills and other work of the community.
Taking potshots at things you don't understand and people you don't know (while leaving out the link so others could verify) smells like a FOX-news rhetorical approach to me. Ditto political labeling (though in the programming community the negative tag is "conservative", whilst in politics it is "liberal"). Tag the thing you don't like with the negative label, then rationalize, and spew misinformation. "Clojure's community came pre-populated with highly conservative programmers from the pure-functional world: basically Haskell/ML types": surveys[0][1] say... nope.
He even ignores the bulk of his own criteria in his labeling exercise. Clojure has almost none of the things on his "Conservative Stuff" list except STM (huh, is GC conservative too?) and almost all of the things on his "Liberal Stuff" list. None of his 1-8 conservative points apply to Clojure (and I see nothing wrong with conservative about speed - Common Lisp has always pursued it, and its pursuit always involves risk), and all of his 9 liberal points apply to Clojure.
Clojure devs are liberals that want their programs to work.
If Yegge doesn't like Clojure, fine. But to rationalize like this is weak.
So, in 2008, you made a comment (below, emphasis mine) about reader macros (yes, which I realize are not identical to macros; please understand that I use a couple reader macros in my day-to-day coding process and am not naive as to their implementation or function) that, at least to me, pretty strongly supports the narrative that Steve is painting: that the goal I somehow "have fewer features that people are less likely to use wrong as otherwise it gets confusing".
> I am unconvinced that reader macros are needed in Clojure at this time. They greatly reduce the readability of code that uses them (by people who otherwise know Clojure), encourage incompatible custom mini-languages and dialects (vs namespace-partitioned macros), and complicate loading and evaluation.
FWIW, this is the same argument that comes up often, from many different members of the community. The namespacing argument is commonly included and sounds technical, but is also trivially solvable; as in, was already solved in a comment during the primary-cited discussion of reader macros on the #clojure IRC channel, but was then dismissed due to the real reason: that reader macros make your code less understandable to other people who know Clojure (the exact same form of argument Steve is talking about, one layer removed).
I'm fairly certain that's the one he's talking about. Having watched it live and on video, its message is not as dire as it's often made out to be. Regardless, it touches on a point of pride for Lisp programmers and as a result is viewed in a negative light by some. I offered a mild rebuttal at the following Conj called "The Macronomicon" (http://blip.tv/clojure/michael-fogus-the-macronomicon-597023...).
Were you planning to touch base with me about having forked my Clojure-HBase library, making changes, and adding novel new version numbers? First I've heard of this.
I posted a pull request to the Clojure Hadoop library earlier this week, I was hoping to get those changes pulled in first as your library depends on that library as well. No offense was intended.
OK, that's cool. I really was asking, you would be within the license rights. I try to keep all my libraries maintained, but sometimes don't have cause to work on some things for a while and things escape my notice.
Though as a footnote, there is no dependency on Clojure Hadoop, they work together without a dependency. I'd take a pull request if the vars that are being moved from defvar- to def have ^{:private true} added to their metadata.
We're just getting started here, so there's the opportunity to have a massive impact. Our growing engineering team is looking to add talent in almost all engineering fields and levels of experience. We're looking to hire engineers specializing in DevOps, Backend, Data and Data Science, Electrical, Embedded/Firmware, Mechanical, Mobile, and QA. If the idea of working with a talented and professional engineering organization, and building something that you will see people enjoying around you every single day is appealing, we want to hear from you!
You can email me at david@bird.co, reply to me here, or get in touch through our (slightly out of date) careers page, linked above.