This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # adventofcode (6)
- # announcements (1)
- # aws (18)
- # beginners (104)
- # boot (11)
- # cljsrn (31)
- # clojure (49)
- # clojure-dev (16)
- # clojure-europe (2)
- # clojure-greece (9)
- # clojure-houston (1)
- # clojure-italy (12)
- # clojure-nl (3)
- # clojure-spec (46)
- # clojure-uk (148)
- # clojurescript (12)
- # community-development (13)
- # core-async (7)
- # cursive (35)
- # data-science (13)
- # datomic (70)
- # events (1)
- # fulcro (22)
- # hyperfiddle (1)
- # jobs-discuss (10)
- # kaocha (3)
- # off-topic (7)
- # om (2)
- # other-languages (32)
- # parinfer (1)
- # portkey (4)
- # re-frame (3)
- # reitit (12)
- # shadow-cljs (49)
- # spacemacs (1)
- # specter (6)
- # sql (5)
- # tools-deps (58)
is it just me or is programming with @annotation (like the Java ones) actually pretty crap? It requires a good understanding about what the annotation means, what it does and how it is affected by other annotations. It isn't code, and that is not a good thing (I think) as it seem to complect things.
example: we had a performance problem with the DB... developer adds some Hibernate Annotations... performance improves... but other things break. suddenly not all the fields from a class get serialised anymore into JSON by Spring due to some other annotation.
I don't want a change to a setting (what an annotation is to a certain degree) to also change the behaviour of my code!!!
It was my experience that Hibernate was very good at the trivial stuff, but very bad as soon as you wanted anything more complicated than 1Row:1Object
Depending on how your database <-> object mapping are it might save you alot of time
devs get into a pure computerscience mindset whereby you want to solve the problem within Hibernate
that is my feeling as well... very easy to get started. When you are just starting a new project and the data model is changing a lot it saves you a lot of time as you only need to write it ones (just the Java code, not also the matching SQL). That makes it easy... but in the long run not simple.
because you are trying to glue two things together that are not quite compatible https://en.wikipedia.org/wiki/Maxibon
no, one kind of ice cream... just one side covered in chocolate and the other in a biscuit.
Trivia for the day. In the early days of support for JPA I patch a problem with the cascade delete in Hibernate. It's not black magic but at that time (about 2004-5 from memory) there was a lot of Aspect Oriented code that had to be wrangled if you wanted to understand the guts of what it did. I was writing a load of AOP code (AspectJ) that sat around Hibernate altering what it did for my specific domain. It was a crazy idea that I objected to to start with, cost me a year of my life and, as I predicted, never went live!
I tend to sum all of this stuff up with favouring explicit code over implicit means you take your pain up front but it's amortised over the lifetime of your code base, versus easy start and then pain or even a deadend later.
it’s also never that much pain. It’s a couple of extra lines to write. 10 minutes here, 10 minutes there.
I'm thinking about going to Spitalfields Market in London for dinner at around 630ish. Anyone around fancy going? (no idea where there, but lots to choose from)
I'm not in London I've always eyed the vietnamese Pho place that is round there though
just need a time and a place to meet and we can decide from there unless you have strong opinions
also in case there are any peter gabriel fans that weren’t aware (or in my case, weren’t born yet) - holy s**t the german versions of Melt and Security are mental
@alex.lynham Still prefer PG3 when it’s all said and done. Because that’s where I Don’t Remember Is…..
@otfrom Did you ever listen to the last St Vincent album, just vocal and piano? Stunning it is.
if anyone else is up for dinner in London this evening, @maleghast and I will be meeting at Spitalfields Market at 18:30
Here’s a thing for tomorrow, relevant to what we talked some time ago (front end, gendering of tech, and the effect of boot camps.) https://www.theguardian.com/technology/2017/mar/14/tech-women-code-workshops-developer-jobs
A thought provoking piece; though I think it ignores the reasons coding initiatives tend to teach front end not backend skills; which is that front end gives you direct visual feedback, and a feeling of creating something sooner. I think this is what biases entry level jobs to those with less experience. It’s not that it’s harder or easier than backend; it’s just easier to get people interested in coding when they can see something. There’s more reward and sense of achievement earlier on. Where as I think backend relies much more on the thrill of solving a problem rather than creating something tangible. On a more positive note — I get the feeling (from purely anecdotal evidence), that more women might be entering data-science, than other areas of computing - and that is comparatively higher paid than other areas. I have no stats to back this up though.
Yeah, this is also my impression, that we get more PhDs who want to be able to make a living and not work insane hours. They leak in from other disciplines.
I’ve been thinking on how to give learners the best feedback and feeling of accomplishment and you know what? Excel.
Now think of how many people you’ve seen sneering at business procedures encoded in Excel, and how they should bring in true programmers and make it all better.
> Also agree with things being most accessible being most denigrated I’m not sure they’re denigrated as such; just if it’s accessible and entry-level there’s more competition for jobs and less for skills which lowers wages. Without meaning to be disparaging of learn to code bootcamps - but I think people think of they’ll “get rich quick”. Being realistic you shouldn’t expect to learn anything valuable to a high standard of proficiency in a few months. A more realistic expectation is to “get rich slow”, and spend a lifetime learning. If you’re getting into a new career with only a few months of experience it seems reasonable that you might expect to start at an entry level. Unfortunately this all starts to sound like the meritocracy it is. I read literally all those links Sean posted on that subject; but I didn’t see many proposed solutions to that… just lots of justified complaints and problems about it.
I agree with all your comments about Excel too. Excel sets a pretty high bar to compete with.
I’m glad people are starting to question the “let’s teach everyone to code”, because realistically once everyone is a coder, coding will no longer pay and we’ll be back to the starting situation.
Salaries can wildly differ depending on location and also whether the company thinks can get away with it.
The author isn’t a developer and might have chosen that as a representative of “backend”.
Dunno :) The stats I found on gender spread came from surveys ran by websites and magazines aimed at engineers, so that could have also been somewhat self selected.
I’ve always wanted to know more about what the industry Really looks like, you know? Because we must be missing huge swathes of population that is not engaged in the same way
I thought the author said the (lack of actual) meritocracy? As in people’s tendency to assume there’s no smoke without fire
Forgive my ignorance but interestingly I’ve never thought of a meritocracy as a negative thing. Now I can start to understand why it isn’t as fair as I first thought! So thanks for this, really helpful 🙂
This is worth a read too https://readwrite.com/2014/01/24/github-meritocracy-rug/
It speaks to a problematic mindset in Silicon Valley as a whole (and it's part of why I detest SV "culture").
devops vs frontend salaries isn’t a fair comparison, but surely on average backend developers should command a significantly higher salary than their front-end counterparts? There are whole classes of problems that a front-end developer never needs to care or know about. JS development is literally just single-threaded CRUD and positioning of elements on the screen. There’s no scaling issues, no race conditions, no out of hours support rotas (urk), no data migrations no exploding databases etc etc etc. It really is a lot simpler than backend work. Am I wrong about this?
Yeah dude, probably. Frontend salaries are lower because the supply is higher, as far as I can tell.
try and build a scalable SPA that works across devices and then tell me how terraform and jenkins and bash are harder 🙂
As a backend developer of 35-ish years, I certainly do not begrudge my frontend counterparts their high salaries, considering the crazy minefields that frontend development is. Cross-browser behavior is a nightmare, and the whole toolchain shifts so rapidly it's a full-time job just keeping up (we're just going through the WebPack 4 pain right now).
I’ve often found front end or JS folks are as good if not better, they just don’t always have much theory (just my experience, sample size of 1) - also true that two of the best engineers I ever worked with were JS
You couldn't pay me enough to take on frontend work. Sure, the problems are different between the front and back and FE folks often have zero idea about the weird stuff us BE folks have to deal with -- but the opposite is also true.
in my last work I was nominally responsible for a team where a female engineer who did full stack JS and was the best dev on the team was routinely sidelined by a male colleague that was just a web designer with some JS
trying to put her in the driving seat - she was smarter and more professional was difficult because of the biases of people around her
even though it was clear she was the best (to me, anyway) - wouldn’t have surprised me if she was paid less too but I don’t know what her comp was
i have seen this many times as well. it’s almost like in nearly all organisations there exists a senior (by time with company, not skills) in sidelining a promising junior (again, by time with company).
We get to test our stuff in isolation or in carefully controlled environments. They can't even begin to test in the actual environments their code will run in. I am continually horrified at the problems that they have to debug and resolve based on bizarre outliers caused by browser/plugin/OS combinations out there 🤯
It’s been my general experience that when I think “X is simple”, it’s just that I didn’t know how complex it was because the pros doing X handled the complexity for me. And when I learn more about X, my mind is blown. (Most recent reason: marketing.)
And you couldn’t pay me to do frontend (people tried, I won’t, I still have IE6 scars.)
thanks for this. i’ll need to ponder a bit more, but don’t think you’ve quite convinced me yet. I’ve done both frontend and backend for many years, and I still feel that the breadth of knowledge and skills required to be successful on the backend is much larger. That said, @seancorfields comment about ‘carfeully controlled environments’ resonated with me.
> when I think “X is simple”, it’s just that I didn’t know how complex it was because the pros doing X handled the complexity for me. oh man this 100%