I initially thought this article was satire - poking fun at how easy programmers really have it on balance. But no, it’s just a contentless, envy fuelled moan from a position of privilege.
Take a step out of the FAANG-SV-HN salary distortion field for a moment, and the London financial one too for the matter, you will clearly see that 55k is a great salary in the UK. Far more than the average.
If you picked a career that you don’t innately enjoy because you thought it would make you rich, and it’s not, then that’s on you.
£55k is not a great salary in the UK for a middle class professional with a degree and >5 years of experience.
Lawyers, doctors, dentists, accountants, front line sales, and even some nurses earn comfortably more than that - never mind MPs, many of whom are both clueless and useless and still manage to earn more than £80k base before expenses.
Some blue collar workers - mostly trades - can also earn a lot more, especially for contract or high-availability work.
Of course it's not a great salary compared to someone who works a checkout, stocks shelves, or talks to customers on the phone.
But qualifications and experience should matter at least a little.
I think that misses the OP’s point. They point to the lack on “innate” or intrinsic value in the job. In other words, the article seems to be selecting the wrong metric in determining a career choice that is meant to maximize happiness
Indeed; £55k is well over median UK income. I’m quite a senior software engineer in the UK and I don’t earn anything like that — forget about £70k! That’s because I don’t work in finance and I’m fine with that. The hedonic treadmill is not worth getting on, imo.
Yeah London is kinda the outlier with this. Give me that pay in say Cardiff and I wouldn't really have anything to complain about money wise. I could be happy slowly getting pay rises collecting my mountain of gold.
Edit: But of we look at the title of the site I think we can see what the post is actually about
Exactly, I'm currently at 56k and while I'm looking at getting paid more because there is room to do so it's fascinating to me that this person who is in top 10% in term of income think they are doing a job that pays badly...
Perhaps, if you shared a single caravan with hundreds of other people. But other than that I do not think it’s alike at all as you are not dependant on a crew for subsistence nor is your freedom to move/explore restricted in a caravan. Either way both can be very fun holidays if you are willing to see past class prejudices.
It's not so much the class prejudices, it's the booze prejudice. I don't socialize with my wifes upper-middle-class colleagues because they like their wine a little too much.
My worst ever holiday memories are being stuck in a caravan in the late 1980s in wet Wales with way too little room and way too many loud drunk people who kept going until 4am every single night.
Cruise ships are like that only you're completely at the whim of the cruise line. You have 0 freedom and you have to deal with all the tax-evading fake-flag BS which seems to rule the sea.
Not the OP but I would describe my anxiety in identical terms.
When I feel the doubt about past memories/decisions start to creep, I whip out my phone and make some brief notes (usually keep one document per trigger). I will just write a few bullet points detailing what facts I am sure of right now along with the reassurances I am telling myself in that moment.
Then, next time it happens I open the same note, read my previous thoughts and relax into it knowing I’ve been here before.
I suppose it’s just an anxiety journal, nothing novel, but it works for me. Over time as I accumulate more facts the effect sort of compounds and simply knowing I’ve got the notes is enough to push the anxiety away.
Ah, I hadn’t thought of the journaling idea. I do try to start and end my day with brief/debrief note taking to create more continuity in my intentions and memory, but that doesn’t address other sources of anxiety in between. Thanks very much, grateful for your response.
I have the attachable keyboard stand that sits comfortably on my knee when I'm on the train. I can type as fast on that as I can a laptop. Honestly with a half decent IDE/dev toolchain it would be a fantastic little lightweight setup for coding.
I've had some luck using http://continuous.codes to write small C# and F# apps/games. I wish it were more actively developed because there is so much potential there.
Is this an anecdote? E.g. I assume you are calling this a tremendous risk because you have seen it first-hand negatively affect your own kids mental development?
Whilst I agree with the sentiment of less tech = probably better for young kids, your comment reads as FUD. 15 minutes a day watching youtube is probably fine and will likely have minimal effect on development compared to other factors.
The content being consumed plays a huge role in this. 15 minutes a day can range from enriching to neutral to harmful. As an example, a kid repeatedly watching YouTube videos of other kids kicking each other in the balls and laughing is likely to elicit unwanted social behavior.
If introducing a functional language was the aim (EDIT: that's my reading of the motivation here) then, given the political context described, I can't help but feel a better choice would have been F#.
It ticks, or half ticks, most of the points in the "Benefits of Using Haskell" section. Whilst also coming armed with C# interop and integration with the .NET ecosystem in which they were already invested.
In my experience, languages that try to bridge OO and functional ecosystems (F#, Scala, etc) tend to suffer from a lot of split-brain / "worst of both worlds" syndrome. You miss a lot of the advantages of FP unless you go all-in on it like Haskell does.
My experience with F# is that functional programming is the default paradigm while object oriented is used when it is required or easier (or required by a C# library you really want). A striking difference with the little Scala I read in the wild (where object oriented was the clear default).
The same goes for mutability, it is there and you should certainly use it when it makes sense but it is not the default.
Haskell has confined mutation with the State and ST types, which guarantees that whatever may be going on inside, the external interface to the function is pure. My main problem with F# (and other multi-paradigm / "functional-first" languages) is that they do not provide any such guarantees; purity becomes merely a matter of convention and convenience, not something ensured by the language. This misses the entire point of functional programming, IMHO, which is referential transparency, and greatly increases the complexity since there are things that matter in F#, like evaluation order, which purity renders completely irrelevant in Haskell.
(Yes, Haskell does have unsafePerformIO and the like for special cases, but the expectation is still that the external interface remains pure. If you deliberately circumvent the language's protections and fail to adhere to this rule then you get to keep both pieces when it inevitably breaks. The compiler is still going to operate under the assumptions that the result depends only on the explicit inputs and that evaluating the function has no side effects.)
> You miss a lot of the advantages of FP unless you go all-in on it like Haskell does.
I'm not familiar with F# but Scala at least has a far inferior compiler (compared to GHC). There are a lot of functional techniques that simply don't make sense when you don't have dedicated tooling to support them.
If I recall, F# doesn't require managed IO which just opens up a can of debugging worms to where you have no guarantees of where side effects and impurity are happening.
I think this is Haskell's biggest disadvantage in industrial sized applications because it significantly complicates debugging and performance reasoning.
Lots of people say this, very few understand what it actually means and how to do the analyses.
> Laziness is, in my opinion, the wrong default.
Unfortunately, GHC is still the only compiler with first-class support for laziness as well as strictness. And you need both if you want to be able to do immutable functional programming.
But in the grand scheme of things it doesn't really matter if you know what you're doing when you use data structures. Some data structures are meant to be strict, others lazy. Haskell allows you to create data structures that are strict in the right places fairly cheaply.
As a counter to this that may make it easier for a company to adopt and reduce the learning curve. Laziness can make it harder for some to reason about performance as an example.
The default is the whole point. Almost any language can support lazy evaluation, given enough boilerplate, but laziness-by-default is a major contributor toward making Haskell code more composable and reusable compared to idiomatic code in other languages.
In strict-by-default languages one must decide up front whether to permit evaluation to be deferred, and there is a cost to be paid via more awkward syntax to first capture the deferred computation and then explicitly evaluate it. This also tends to add runtime overhead which a Haskell compiler would optimize out in cases strict evaluation can be inferred. As a result, libraries generally expose only strict interfaces—and while most lazy functions can easily be made strict in Haskell with judicious application of `seq`, the reverse is not so simple.
Sure, sometimes excessive laziness becomes a problem. However, these cases are not that common, or particularly difficult for an moderately experienced Haskell coder to identify or work around. Enforcing strictness-by-default just because one does not foresee a need for laziness, without any evidence that laziness is negatively impacting performance, would be a form of premature optimization.
Take a step out of the FAANG-SV-HN salary distortion field for a moment, and the London financial one too for the matter, you will clearly see that 55k is a great salary in the UK. Far more than the average.
If you picked a career that you don’t innately enjoy because you thought it would make you rich, and it’s not, then that’s on you.