This is so shortshighted, it's not about 'respect', its about market value.
By bringing an offer your employees are proving their market value, and you don't want to match it, so they will leave.
It's about treating people decently, in my view. It's not necessary to try to set up a bidding war in order to demonstrate market value. The disrespect that rankles me is the treatment of the company that made the offer, honestly.
I just choose not to play that game. It's unnecessary. If an employee can't just come to me and be straight about their compensation requirements, that's a problem.
The balance of power is still vastly in favor of the company that made the offer. Meaning, they could rescind the offer at any time for any reason and possibly ruin the potential employees life. Whereas the reverse case of the potential employee rejecting an offer is much less likely to have a material impact on the company. For this reason I don't think the company deserves that much concern.
But it's not evidence of anything other than than a company has valued that potential employee at a particular rate. What an employee is worth to an employer is pretty subjective. Someone that is worth 7 figures to one company may only be worth 6 or 5 to another.
Having an offer in hand is valuable to the employee, certainly! There's nothing wrong with getting an offer, then asking your current employer for a raise that would meet or exceed that offer. The issue I have is actually communicating that offer to the current employer.
Now, don't get me wrong -- I'd certainly never punish or fire anyone who did that. I'm just not going to give in to what I perceive as extortion, and what I perceive as being unfair to the employer who made the offer.
I don't understand this question. What negative thing would I think?
If someone asked me for a pay raise and I turned it down, I'd also explain exact why I turned it down. (This is hypothetical as I've not turned down a pay raise). I wouldn't think poorly of anyone for just asking for a raise, but I suppose I'd start to get annoyed if they did it daily when the reason that I turned them down was still true.
Seem like the design decision to only allow a single thread to handle writes paid off.
Datomic is a marvel of good design, I wish I could use it again....
I think the language has indeed reached a stable point and found its niche, which is small, but there are certainly domains where Clojure is the best fit.
The ideas behind Clojure (functional, immutable datastructures, homoiconic syntax, focus on simplicity, JVM interop) still stand strong IMO.
There are still some exciting projects done in Clojure: Electric Clojure and Rama come to mind.
clojure is everywhere in fintech - nubank, guaranteed rate, kroo bank, griffin, pennymac, two sigma, dividend finance, treasury prime, gravie. Other big areas are healthcare and midmarket adtech. And of course startups outside of SF/NYC with smaller seed rounds looking for tech advantage - midwest USA, Europe/UK, Latin america
The further you get from silicon valley the more clojure you see — anyone with a network at FANG spent the last 10 years trying to break in and get that huge salary, which means conforming to the recruiting process, i.e. spending your time off grinding leetcode instead of learning new PLs
Speaking from past experience at Guaranteed Rate, management (probably not developers) regrets that experiment. They’ve laid off most of the clojure devs I know of there (I’m sure one or two remain for legacy services.)
I interviewed at Two Sigma like 6 years ago and I was interested in doing Clojure professionally so I asked about it and was told that they had stopped all new development in Clojure
Doesn't this ignore the reality on the ground that Clojure is a niche (but wonderful) programming language that offers very few career opportunities? It simply isn't big in any specific domain.
I also don't buy that you see more Clojure the "further you get from silicon valley ..." without some actual (or even anecdotal) data to support that claim.
I'm not saying there are zero instances of Clojure in production systems. But it is hard for me to think that it represents a large number of professional employed software engineers. The 2023 StackOverflow survey show 1.38% out of 67,053 respondents in their "most commonly used programming language" section naming Clojure. That is less than 1,000 developers. The public university I work at graduated 500+ CS undergrads in 2023. I would bet $100 that zero of those got a first job that paid them to write Clojure professionally. I would bet $1000 for less than ten grads. I would bet $50,000 for less than 25.
I'm not trying to be cute but don't you think there are less than 10,000 software engineers in the US (maybe the freaking world) who primarily write Clojure code in their day job?
Because I'm curious, job searches at the company site of your list for 'clojure':
Nubank - enhum resultado com a palavra "clojure" encontrado (no results)
Guaranteed Rate - no results
Kroo Bank careers page - no tech listings currently
Griffin - open listing for software engineer (London or Remote within the UK, Germany, Sweden or Ireland) - description: Our backend stack is Clojure, FoundationDB, Kubernetes and AWS. Our frontend stack is CLJS, Reframe, Reagent, React, Stitches, Storybook, and Playroom.
Pennymac - Sorry, no jobs were found that match your search criteria.
Two Sigma - No jobs found
Dividend Finance - 0 JOBS FOUND
Treasury Prime - There are no current openings. (for software engineers)
Gravie - Lead software engineer position - description: Advanced programming experience in multiple programming languages ( Java, Kotlin, Groovy/Grails, JavaScript/TypeScript or Python) along with Clojure/ClojureScript or another functional programming language
Indeed.com returns 15 jobs posted in the last two weeks (US) for the Clojure keyword. LinkedIn returns 34 job posting in the last month (again, in the US).
I love Clojure - it has always "worked" in my head as a language to solve problems in. I was at the first Clojure/conj. I have deployed production code that I wrote in Clojure. Clojure made me a better developer in other languages.
But in the big picture for professional software engineers, Clojure might as well not exist.
Technologies: deep experience in stream processing and backend development, Kotlin, Java, Kafka, SQL, Clojure, AWS, GCP, Azure. Looking to get back into AI.
I am a dedicated and versatile software developer with an MSc in Artificial Intelligence and over 12 years of experience in developing innovative software in various domains.
My expertise is designing and building reliable, fast backend systems that handle lots of data. I can support the entire development cycle, from gathering requirements to design, architecture, planning, implementation, testing, DevOps, monitoring and optimization.
Furthermore, I have experience in building interactive dashboards, data visualizations and AI applications such as automated planning, machine learning and natural language processing.
My goal is to deliver high-quality software that solves complex problems. To achieve this, I value understanding the problem, rapid iteration and collaboration with colleagues.
Serialization and going over the network are an order of magnitude slower and error prone than good ol' function calls.
I've seen too many systems that spent more time on marshalling from and to json and passing messages around than actual processing.
reply