Clojurians Log v2

Could be, its good to inform them However it could be pshishing email as well, so a hacker send you a link to hack you

On the other hand if it's really a mishandling by AshbyHQ, it's a privacy concern. Who else got such email? How would you know? If the real URL (right-click to copy the actual link, not the displayed text!) looks like from http://subdomain.ashbyhq.com you need to be careful, I would not click on it. If it's really http://ashbyhq.com then it's probably fine. I've seen subdomains being taken over mainly due to cloud resources being terminated without DNS entries being updated accordingly. Send a message to the email at the end of this page if needed: https://www.ashbyhq.com/resources/security

Three companies I applied with recruiters told they that I already applied in the past. This is happening a lot, and it's infuriating

Ashbyhq as well?

in that case who is applying us?

No, mine was Luflox and an undisclosed company that they told me I was already on their process via Simbiosis.

Maybe some ruthless agent/agency that does not care about privacy and code of conduct. I imagine this must be regulated in most countries.

And/or some AI scanning linkedin data and sending CV

You can also share this message on the Zulip of Clojurian in this thread https://clojurians.zulipchat.com/#narrow/channel/151430-jobs

Yeah? Ok, will do - thanks 🙏

And also here in #C05006WDW as well. Quite a few people read that channel and don't read this one. I just forwarded the link to the original post.

@maleghast Oliver, hi! Given it’s about something from the UK, isn’t the recruiter’s name Gary R.? 🙂

Not looking myself but someone I know might be interested, I can pass it on to him

@U0BP4LM0XK8 👆

@conor.p.farrell - Sure - just send them to me here or they can reach me on LinkedIn and I will happily introduce them 🙂

Pretty sure I was just contacted for the same job. Would have jumped on it for 550 quid a day, but they were looking for someone who can do 1-2 days a week in London, which isnt really doable since I am 7 timezones away

I'm currently looking for Clojure roles, I live near London

@sayedhajaj - Sorry that ship has sailed

paging @andersmurphy

build stuff in that language so you learn it and look for employers that have your current stack and newer preferred stack. Then you can help out on both sides. On one side as a beginner, the other as an expert. value from day 1, learn more and contribute in a real codebase

Or see if you can introduce the new language into the existing company. That's what I've done, and I have friends that have also managed to do that.

yeah. internal tools, tests, etc are great ways to add a new stack, let it show off its strengths without being shoehorned in

i think there’s a java collections library from zach tellman that uses clojure for writing very expressive tests. That’s a great way to show off some clojure benefits without needing much buyin from others

Is that common? Finding companies that are moving from one stack to another?

Not necessarily moving. But have both

I'm sure tons of companies have go, c++, and Java in some capacities

Almost everywhere I've worked since the dot-com era has had multiple stacks. It was less common before then (partly because we had fewer languages back then!). Large companies especially tend to have different stacks across different teams or different divisions.

contribute to a valuable things in the language

nothing to add other than this is a great question and something I've been trying to figure out. I have 3 years of Clojure production experience from about 10 years ago (we had full autonomy so introduced Clojure ourselves).

10 years ago i added a test viewing site in clojure to a .net shop. add some value in whatever stack you like and people will respect it

Thanks for the tips. Taking the initiative to provide value where it isn't expected resonates with me. I'll try to keep that as a constant reminder.

Tips above are certainly useful; 2 more cents based on personal experience. Working in consultancies can help as they're more likely to want random folk landing random tech (or shift role, eg work more on infra or data engineering or whatever) whilst with companies with fixed tech stack you're more likely to need to justify the necessity of using something else. And even if you don't land straight away a gig with your target tech, switching between different stacks is valuable as long as you're up for the ride. Valuable because: • you can prove to yourself you can do it the times it gets challenging • it will show in your CV that you're flexi and adaptable (not everyone cares, usually competent people are able to appreciate though 😁) • one way or another you're going to learn in the process Needless to say, with trendy technologies everything gets easier. When it was on the rise it was definitely possible to jump on the Node.js train; and nowadays everyone throws some Python at you. For me it's been waaay harder to just land a Clojure gig (and that was an interesting combo consultancy + luck + right stars alignment). Even with 4 years experience at work with Clojure, I found so far impossible landing a another functional language gig (not a personal goal, but something I'd take more happily than the usual work with most mainstream languages).

I was in the same situation ~10 years ago, and got hired with only a week of practical Clojure experience. I then worked with Clojure for 7 (beautifull) years. I had a ton of luck, so take it with a grain of salt. 1. Make sure you know the limitations/tradeoffs of the language/ecosystem so that you are ready to spend the next few years (at least) working with it full time. 2. Build confidence using the language to solve tiny problems (doesn't have to be entire products, or even public). Exercising the path from spec to deploy will make you discover the ecosystem around the language (options in tooling, workflows, culture of the community, ...). Maybe you already have that. 3. Make yourself discoverable by recruiters in the language (add the language to your linkedin skills, and other online presence). 4. If the bait works, be honnest about your level. Your goal is to reach the step where you have technical discussions with technical people. Your expertise in sofware engineering, your domain expertise in any field you have worked in, your ability to (re-)frame 😁 problems, identify unknowns, etc. All that will be valued by someone in the field. That worked for me to land my first Clojure job. Then when I switched to another company, I was able to start a core project in Clojure as the sole developper on it in a tiny tech team.

Code in that language, become confident, and make something you can show during an interview. For example, I built https://kalkulator-pozyczek.wladyka.eu/ in TypeScript + AI, because I wanted to experiment with AI and compare ClojureScript with TS and the TS tooling. If I wanted to be hired as a TS developer, I would show that code and have something to discuss. And if AI came up, I would show how I built it and why that way. I'm writing an in-depth article about coding with AI. Why do I keep pointing to small app examples? Because of NDAs — I can't show code from my regular work. Small apps + articles are a normal way to prove your skills. Just be ready to discuss it and have something interesting to say. In other words, the point is not only to build an app, but also to make good architectural decisions that show you know what you are doing. Don't be afraid to build small apps. This is the way. You can't show enterprise apps because of the agreements you signed. BTW, this is my first app in Clojure: https://github.com/kwladyka/chess-challenge — proof that I could code in Clojure.