Sit down before you read this.

So I interviewed a guy for a "Support Engineer" internship position.

Me and the team lead sit down and are waiting for him to enter, but apparently he's actually making a coffee in the kitchen.

This isn't exactly a strike since the receptionist told him that he can go get a drink, and we did too. It's just always expected for him to get a glass of water, not waste 3 minutes brewing a coffee.

In any case he comes in, puts the coffee on the table, then his phone, then his wallet, then his keys and then sits on our side of the table.
I ask him to sit in front of us so we can see him. He takes a minute to pack and tranfer himself to the other side of the table. He again places all of the objects on the table.

We begin, team lead tells him about the company. Then I ask him whether he got any questions regarding the job, the team or the company . For the next 15 minutes he bombards us with mostly irrelevant and sometimes inappropriate questions, like:
0: Can I choose my own nickname when getting an email address?
1: Does the entire department get same salaries?
2: Are there yoga classes on Sundays only or every morning?
3: Will I get a car?
4: Does the firm support workspace equality? How many chicks are in the team?
5: I want the newest grey Mac.

And then.. Then the questions turn into demands:
6: I need a high salary (asks for 2.5 more than the job pays. Which is still a lot).
I ask him why would he get that at his first job in the industry (remind you, this is an internship and we are a relatively high paying company).
He says he's getting paid more at his current job.
His CV lists no current job and only indicates that he just finished studying.
He says that he's working at his parent's business...
Next he says that he is very talented and has to be promoted very quickly and that we need to teach him a lot and finance his courses.

At this point me and the team lead were barely holding our laughs.

The team lead asks him about his English (English is not our native language).
He replies "It's good, trust me".
Team lead invites him for an English conversation. Team lead acts like a customer with a broken internet and the guy is there to troubleshoot. (btw that's not job related, just a simple scenario)
TL: "Hello, my name is Andrew, I'm calli..."
Guy: *interrupts* "Yes, yes, hi! Hi! What do you want?"
TL: "Well, if you let me fi..."
Guy: "Ok! Talk!"
TL: "...inish... My internet is not working."
Guy: "Ok, *mimics tuning a V engine or cooking a soup* I fixed! *points at TL* now you say 'yes you fixed'".

Important to note that his English was horrible. Disregarding the accent he just genuinely does not know the language well.

Then he continiues with "See? Good English. Told you no need to check!".

After about half a minute of choking on out silent laughter I ask him how much Python experience he has (job lists a requirement of at least 1 year).
He replies "I'm very good at object oriented functional programming".
I ask again "But what is your experience? Did you ever take any courses? Do you have a git repository to show? Any side.."
*he interrupts again* "I only use Matlab!".

Team lead stands up and proceeds to shake his hand while saying "we will get back to you".

At last the guy says with a stupid smile on his face "You better hire me! Call me back tomorrow." Leaves TL hanging and walks away after packing his stuff into the pockets.

I was so shocked that I wasn't even angry.
We both laughed for the rest of the day though. It was probably the weirdest interview I took part at.

Isn't it soo simple :/

The project where I realized I wanted to go from chemist to pro dev.

I built a flow-chemistry spectrometer with monitoring backend in Haskell.

Spectroscopy is where you add a reagent to a glass tube, it changes color, and by measuring the exact color it tells you how much of something (for example, a toxin) is present in the sample.

I had to do that a lot on factory samples, writing down measurements using pen & paper.

I'm lazy so I decided to do the logical thing: Automate it. I bought a second hand spectrometer, stripped the casing, did a shitload of glassblowing and hooked up tubes to the production pipelines, so I could get samples, mixing them in the correct ratio with reagents in continuous flows using valves.

I ended up using 2 home-crafted arduino-like boards (etching PCBs is fun!).

One to calibrate the mixture against known samples and control solenoid valves to continuously cycle through various reagents and deionized flushing water, the other to record the measurements and send them to a server running a Haskell/Yesod API.

The server collected the information into InfluxDB (A time series database), displaying all data on a graphite dashboard.

Eventually I wrote Haskell plugins for most of the chemistry processes, from pH & temperature measurements to polymer property and pigment tests (they made a lot of printer ink).

Then I was fired because they didn't need chemists anymore, and the code "could be maintained by the intern" (poor guy)...

But I did find out that I loved functional programming, chemistry automation projects, and crafting my own electronics during that time.

When you casually read your functional programming book, flip a page and find a juicy meme 😂

“Everything is terrible”

Wrong.

“I never put anything worth seeing on Facebook they don’t know that much about me”

Bitch Facebook can show you a picture ask you 20 questions about it and based on those questions they can probably tell you where your wedding ceremony was.

“I won’t be affected by advertisments”

Good luck! No I’m not talking to you I’m talking to your parents. Hopefully they got you sterilized.

“Every language has advantages and disadvantages”

Right but not the same amount. For the sake of brevity I’m still going to go with wrong. Unless you care to name some
Visual Basic advantages?

“If it gets the job done it’s good enough”

Wrong. Unless you have to maintain your own code and you never quit your job. Then make my day.

“C# fixes the problems in c++”

Sounds to me like you don’t understand a whole lot about c++.

“It’s easier to write java code than c code”

Yeah it’s also easier to walk than it is to run what’s your point? You want to be fat forever?

“Why don’t you respect other people’s choices?”

Some people choose Windows, and some people choose heroin. Are we splitting hairs?

“There are things you can do in C# that you can’t do in c++”

Wrong.

“C++ is missing features”

Yeah because if it wasn’t then they’d be running the risk of shit stained ass wipes like you using them and fucking up your designs.

“Windows has gotten better”

Wrong.

“Every text editor can be good if you learn how to use it”

I dare you to pit 10 average vim users against 10 average vscode users and see who finished first on average. Not the same.

“I don’t have time for projects”

But you have time to whack off once a day and watch tv.

“I’m under so much stress”

Me too.

“I want to be a game dev”

It takes a very unique type of person to be a game dev without losing your enthusiasm for games forever after about a year of work.

“I want to make more of an impact”

Said every generation of young people ever. Just fucking do something you like.

“I like C#”

I had to design a custom compiler for c# once and the language spec would horrify you once you understand what’s really happening with all these useless party tricks. You don’t know what you are talking about and should leave.

“Functional programming is the future”

K

“Gmail is the best”

Why? Because it’s free? I can kick you in the nuts for free if you want.

“The internet is the future”

Yeah we figured that out in 1996 grandpa, and darpa figured it out in 1982.

“Netflix is the best bang for the buck”

Great! Sign me up I want to pay them so I can subconsciously be more glued to my tv. Having no idea how I’m really paying for entertainment is good.

“Got any questions about propane?”

Or propane accessories?

When I started to learn functional programming I asked myself: "What the hell is this?"
Fast forward a couple of years, I still wonder what 'this' is.

So, today I was at my college library, working on an Haskell project that I have for my Functional Programming class. Library's packed and no seats are available, when the lady that works there passes behind me and says:
"There's people that want to study, if you're gonna be playing on your laptop please leave."
What? Excuse me? Are we in the 21st century or what?
How does a lady that works at a library, on an Engineering College, for more than 10 years, doesn't...
Screw it, I just laughed so hard and proceeded working.

Oh and by the way, first time posting on here!

Why are job postings so bad?
Like, really. Why?

Here's four I found today, plus an interview with a trainwreck from last week.
(And these aren't even the worst I've found lately!)

------

Ridiculous job posting #1:
* 5 years React and React Native experience -- the initial release of React Native was in May 2013, apparently. ~5.7 years ago.
* Masters degree in computer science.
* Write clean, maintainable code with tests.
* Be social and outgoing.

So: you must have either worked at Facebook or adopted and committed to both React and React Native basically immediately after release. You must also be in academia (with a masters!), and write clean and maintainable code, which... basically doesn't happen in academia. And on top of (and really: despite) all of this, you must also be a social butterfly! Good luck ~

------

Ridiculous job posting #2:
* "We use Ruby on Rails"
* A few sentences later... "we love functional programming and write only functional code!"

Cue Inigo Montoya.

------

Ridiculous job posting #3:
* 100% remote! Work from anywhere, any time zone!
* and following that: You must have at least 4 work hours overlap with your coworkers per day.
* two company-wide meetups per quarter! In fancy places like Peru and Tibet! ... TWO PER QUARTER!?

Let me paraphrase: "We like the entire team being remote, together."

------

Ridiculous job posting #4:
* Actual title: "Developer (noun): Superhero poised to change the world (apply within)"
* Actual excerpt: "We know that headhunters are already beating down your door. All we want is the opportunity to earn our right to keep you every single day."
* Actual excerpt: "But alas. A dark and evil power is upon us. And this… ...is where you enter the story. You will be the Superman who is called upon to hammer the villains back into the abyss from whence they came."

I already applied to this company some time before (...surprisingly...) and found that the founder/boss is both an ex cowboy dev and... more than a bit of a loon. If that last part isn't obvious already? Sheesh. He should go write bad fantasy metal lyrics instead.

------

Ridiculous interview:
* Service offered for free to customers
* PHP fanboy angrily asking only PHP questions despite the stack (Node+Vue) not even freaking including PHP! To be fair, he didn't know anything but PHP... so why (and how) is he working there?
* Actual admission: No testing suite, CI, or QA in place
* Actual admission: Testing sometimes happens in production due to tight deadlines
* Actual admission: Company serves ads and sells personally-identifiable customer information (with affiliate royalties!) to cover expenses
* Actual admission: Not looking for other monetization strategies; simply trying to scale their current break-even approach.

------

I find more of these every time I look. It's insane.
Why can't people be sane and at least semi-intelligent?

Functional Programming literally has 'fun' in the title; OOP is one letter away from 💩. I rest my case.

It seems like every other day I run into some post/tweet/article about people whining about having the imposter syndrome. It seems like no other profession (except maybe acting) is filled with people like this.

Well lemme answer that question for you lot.

YES YOU ARE A BLOODY IMPOSTER.

There. I said it. BUT.

Know that you're already a step up from those clowns that talk a lot but say nothing of substance.

You're better than the rockstar dev that "understands" the entire codebase because s/he is the freaking moron that created that convoluted nonsensical pile of shit in the first place.

You're better than that person who thinks knowing nothing is fine. It's just a job and a pay cheque.

The main question is, what the flying fuck are you going to do about being an imposter? Whine about it on twtr/fb/medium? HOW ABOUT YOU GO LEARN SOMETHING BEYOND FRAMEWORKS OR MAKING DUMB CRUD WEBSITES WITH COLOR CHANGING BUTTONS.

Computers are hard. Did you expect to spend 1 year studying random things and waltz into the field as a fucking expert? FUCK YOU. How about you let a "doctor" who taught himself medicine for 1 year do your open heart surgery?

Learn how a godamn computer actually works. Do you expect your doctors and surgeons to be ignorant of how the body works? If you aspire to be a professional WHY THE FUCK DO YOU STAY AT THE SURFACE.

Go learn about Compilers, complete projects with low level languages like C / Rust (protip: stay away from C++, Java doesn't count), read up on CPU architecture, to name a few topics.

Then, after learning how your computers work, you can start learning functional programming and appreciate the tradeoffs it makes. Or go learn AI/ML/DS. But preferably not before.

Basically, it's fine if you were never formally taught. Get yourself schooled, quit bitching, and be patient. It's ok to be stupid, but it's not ok to stay stupid forever.

/rant

A is for Assembly, a wizard's spell

B is for Bootstrap, so bland and the same. And also for Brainf*ck, will blow you away

C is for COBOL, your grandad knows that

D is for daemon, your server knows what

E is for Express.js, you node what is coming

F is for FORTRAN, which is perferct for sciencing

G is for GNU which is GNU not UNIX

H is for Haskell using functional units

I is for Intance, An action of Object

J is for Java plays with them Always

K is for Kotlin, Android's new toy

L is for Lisp, scheming a ploy

M is for Matlab, who knows how it works

N is for Node a bloatware of code

O is for Objective Pascal, you did not expect that

P is for programming, we all love to do that

Q is for Queries, A database is made

R is for R, statistics are great

S is for Selenium, you have to test that

S is for Smalltalk, let's make it all brief

T is for Turing Test, how human is this?

U is for Unix, build with all talents

V is for Visual Studio, built with all laments

W is for Web, lets build something cool

X is for XHTML, remember all that?

Y is for Y2K, I'm tired as f*ck

Z is for Zip, let's zip is all now.

Get yourself coffee and back to the grind.

Imagine yourself exploring Medium, looking for some new awesome tools to try out.

You accidentally find the new, promising programming language. It called Blow. It promises itself to be “idiomatic”, “minimalistic”, “simple” and “handsome”. And it also compiles to Electron. You decide to give it a try.

It has its own package manager, simple and idiomatic – every package is “blow add” away. But it’s only three packages available: the “blowsay”, just like “cowsay”, the “this”, printing The Blow Manifesto and “blue”, which is simplistic, simple and minimalistic idiomatic handsome functional frontend framework built with simplicity in mind.

You want to build a todo app, so you type “blow add blue” and press enter.

Following Medium articles written by some guy wearing Ray-Bans, you managed to finally put a todo app together, after seven hours of straight up coding and fighting that simple and idiomatic syntax, trying to make it do what you need. Alright, it’s time to build it.

It has built-in task runner named “job”.

So you type “blow job todo”.

You spending three hours more doing “blow job this”, “blow job that”, trying to blow job everything you see. You’re tired and mad at those damn blow job hipsters created that. You literally suck at programming in that.

Everything falls apart. Things doesn’t work. And after another “ENOENT 0() 0x628 NOT_SUPPORTED”, you give up, admitting that you’ve really sucked at this.

Making a pens touer at work today.

The exact moment when I understood what programming actually was.

I was getting hard times at my 3rd college grade, trying to implement the recursive sudoku solver in python. Teacher spent a lot of time trying to explain me things like referential transparency, recursion and returning the new value instead of modifying the old one and everything related. I just couldn't get it.

I was one of the least productive students, i couldn't even understand merge sort.

I was struggling with for loops and indexes, and then suddenly something clicked in my head, like someone flipped a switch, and i understood everything i was explained, all at once. It was like enlightenment, like pure magic.

I had sudoku solver implemented by the end of the lecture. Linked list, hash map, sets, social graphs, i got all of these implemented later, it wasn't a problem anymore. I later got an A for my diploma.

Thank you @dementiy, you were the reason for my career to blast off.

it's funny, how doing something for ages but technically kinda the wrong way, makes you hate that thing with a fucking passion.

In my case I am talking about documentation.

At my study, it was required to write documentation for every project, which is actually quite logical. But, although I am find with some documentation/project and architecture design, they went to the fucking limit with this shit.

Just an example of what we had to write every time again (YES FOR EVERY MOTHERFUCKING PROJECT) and how many pages it would approximately cost (of custom content, yes we all had templates):

Phase 1 - Application design (before doing any programming at all):
- PvA (general plan for how to do the project, from who was participating to the way of reporting to your clients and so on - pages: 7-10.
- Functional design, well, the application design in an understandeable way. We were also required to design interfaces. (Yes, I am a backender, can only grasp the basics of GIMP and don't care about doing frontend) - pages: 20-30.
- Technical design (including DB scheme, class diagrams and so fucking on), it explains it mostly I think so - pages: 20-40.

Phase 2 - 'Writing' the application
- Well, writing the application of course.
- Test Plan (so yeah no actual fucking cases yet, just how you fucking plan to test it, what tools you need and so on. Needed? Yes. but not as redicilous as this) - pages: 7-10.

- Test cases: as many functions (read, every button click etc is a 'function') as you have - pages: one excel sheet, usually at least about 20 test cases.

Phase 3 - Application Implementation
- Implementation plan, describes what resources will be needed and so on (yes, I actually had to write down 'keyboard' a few times, like what the actual motherfucking fuck) - pages: 7-10.
- Acceptation test plan, (the plan and the actual tests so two files of which one is an excel/libreoffice calc file) - pages: 7-10.
- Implementation evalutation, well, an evaluation. Usually about 7-10 FUCKING pages long as well (!?!?!?!)

Phase 4 - Maintaining/managing of the application
- Management/maintainence document - well, every FUCKING rule. Usually 10-20 pages.
- SLA (Service Level Agreement) - 20-30 pages.
- Content Management Plan - explains itself, same as above so 20-30 pages (yes, what the fuck).
- Archiving Document, aka, how are you going to archive shit. - pages: 10-15.

I am still can't grasp why they were surprised that students lost all motivation after realizing they'd have to spend about 1-2 weeks BEFORE being allowed to write a single line of code!

Calculation (which takes the worst case scenario aka the most pages possible mostly) comes to about 230 pages. Keep in mind that some pages will be screenshots etc as well but a lot are full-text.

Yes, I understand that documentation is needed but in the way we had to do it, sorry but that's just not how you motivate students to work for their study!

Hell, students who wrote the entire project in one night which worked perfectly with even easter eggs and so on sometimes even got bad grades BECAUSE THEIR DOCUMENTATION WASN'T GOOD ENOUGH.

For comparison, at my last internship I had to write documentation for the REST API I was writing. Three pages, providing enough for the person who had to, to work with it! YES THREE PAGES FOR THE WHOLE MOTHERFUCKING PROJECT.

This is why I FUCKING HATE the word 'documentation'.

Curry functions

This page doesnt look like much until I tell you it is written entirely in Clojure using a custom built HTML generator.

PM: Guys, we have to upgrade Java 8

Me: hey check out all these cool functional programming stuff (lambdas)in Java 8.

PM: Sorry you can't do that. Our automated testing software isn't up to date to test Java 8. So you have to code it "vanilla"

Me: Erm, upgrade it?

PM: we didn't budget it for that.

Me: *thinks to me miself* brilliant

#+BEGIN_QUOTE
What’s 5 plus 2?
7.
Correct.

What’s 5 plus 3?
8
Nope. It’s 10, because we turned 5 into 7, remember?
#+END_QUOTE

Let the student use their own laptops. Even buy them one instead of having computers on site that no one uses for coding but only for some multiple choice tests and to browse Facebook.

Teach them 10 finger typing. (Don't be too strict and allow for personal preferences.)

Teach them text navigation and editing shortcuts. They should be able to scroll per page, jump to the beginning or end of the line or jump word by word. (I am not talking vi bindings or emacs magic.) And no, key repeat is an antifeature.

Teach them VCS before their first group assignment. Let's be honest, VCS means git nowadays. Yet teach them git != GitHub.

Teach git through the command line. They are allowed to use a gui once they aren't afraid to resolve a merge conflict or to rebase their feature branch against master. Just committing and pushing is not enough.

Teach them test-driven development ASAP. You can even give them assignments with a codebase of failing tests and their job is to make them pass in the beginning. Later require them to write tests themselves.

Don't teach the language, teach concepts. (No, if else and for loops aren't concepts you god-damn amateur! That's just syntax!)

When teaching object oriented programming, I'd smack you if do inane examples with vehicles, cars, bikes and a Mercedes Benz. Or animal, cat and dog for that matter. (I came from a self-taught imperative background. Those examples obfuscate more than they help.) Also, inheritance is overrated in oop teachings.

Functional programming concepts should be taught earlier as its concepts of avoiding side effects and pure functions can benefit even oop code bases. (Also great way to introduce testing, as pure functions take certain inputs and produce one output.)

Focus on one language in the beginning, it need not be Java, but don't confuse students with Java, Python and Ruby in their first year. (Bonus point if the language supports both oop and functional programming.)

And for the love of gawd: let them have a strictly typed language. Why would you teach with JavaScript!?

Use industry standards. Notepad, atom and eclipse might be open source and free; yet JetBrains community editions still best them.

For grades, don't your dare demand for them to write code on paper. (Pseudocode is fine.)

Don't let your students play compiler in their heads. It's not their job to know exactly what exception will be thrown by your contrived example. That's the compilers job to complain about. Rather teach them how to find solutions to these errors.

Teach them advanced google searches.

Teach them how to write a issue for a library on GitHub and similar sites.

Teach them how to ask a good stackoverflow question :>

1790. Sad - gotta love some xkcd

Functional Programming. Because Moores Law has moved from making processors faster to multiplying cores, and we may eventually have to code on machines that have 1024 cores or more. Mutable state will cause all kinds of hell in those scenarios. We already have problems with it when we have like 2-3 different threads.

Functional programming jokes don't work because there are no side effects

So much for purely functional programming language.

Don't get me wrong, I like funcional programming, but this smug „This would neeever happen with FP“ bullshit really gets on my nerve and kind of turns me off the idea of ever wanting to work with FP programmers.
It's just another paradigm, it's still possible to write unmaintainable fuckugly crapcode with functional programming.
And it is still very possible to write beautiful, clean, well maintainable code with OOP. Get over yourselves and understand that it's a tool and not a religion, and a good dev should know when to pick which tool for which job without childish notions of intellectual superiority.

1h into learning Haskell and I haven't written a single hello world example yet

Change feels good

I already love it

Once I watched a 30min YouTube video on functional programming just because the presenter was cute. 😘
Anyone ever did this ???

And btw the video is Functional programming by Anjana vakil.

I'm working on a programming language with a "bytecode" interpreter and a compiler that translates source code to said bytecode and... it sort of actually works!

I want to recreate an Erlang-style environment, currently you can write functions, call C++ functions via wrappers, have immutable-only values, and it has no explicit control structure apart from statement sequencing and the if-expression because I want to make it as functional as possible. Next thing on the list is to add a green threads implementation and ability to spawn and send messages to processes.

Still a WIP and heck even design-in-progress.

Now for the rant:
I'm using CMake for building C++ (interpreter) and Stack for Haskell (compiler) and I've been trying to get them to talk to each other for hours because I want CMake to manage the Stack build too and shove all the executables into one place. CMake documentation is weird and Stack isn't too helpful either, so I guess I'll just spend another few hours trying to get Stack to fuckin reveal its build directory to CMake and/or build to a given directory. Ugh.

When I started programming Batch Files I decided to go big and and make an Batch Program with a fully functional UI system. Just when I had finished the first menu I kept getting a "goto was unexpected at this time" or something like that. I did everything I could to see about debugging until I finally cleared my calender and spent the next week debugging. A week of debugging goes by and I see someone coding in color rather then black and white at my school. I walk up to him and ask. "What language is that?" To which he replies "Batch". I asked him how he got Notepad to be in color and he simply pointed to the top left of the screen and it said Notepad++.
I get home later that day and look up "Notepad++" and download the first thing I see. I install the .msi file and I see a language bar at the top of the screen. Set it to batch, and drag my .bat file into the program to see six of my dividers are red bars. I look this up and see there's another spacing option "echo.", I replace my current spacers with this and the whole thing starts working. Fml, that's a week I'm never gonna get back

I really like programming in Haskell.
Everyone I know seems to hate it (or prefer to work with oo-languages)
Any friendly Haskeller here who wants to collab/teach/learn from each other? ._.'

One of the biggest barriers to the wide(r) scale adoption of functional programming languages like Haskell, F#, and Scala is how snooty and condescending your average FP developer is. And beginner-unfriendly.

Ask them a question about an intermediate topic (in my case, the Free monad) you're likely to get a whole torrent of category theoretic rubbish in return.

This is a common pattern I see when "experts" answer questions.

Now, it didn't bother me much because I've studied a fair amount of category theory and can usually follow such answers, but, for the sake of the general case, I'd like to shove these rules into the heads of everyone writing an answer to a question (not just FP):

1. If you can't illustrate a concept clearly without going into verbal diarrhoea with phrases like "monad homomorphism" and "just a monoid in the category of endofunctors" then you clearly haven't understood it properly (unless, of course, the answer absolutely requires it). An answer is not the place to show off your knowledge of a topic.

2. Please remember that everyone was a beginner at some point. Including you. Understand that some concepts can be extremely frustrating at first and yet incredibly simple after you grok them (eg. monads).

3. If the person asking the question is a beginner, using complex concepts in an answer just because it's a more "elegant" way to explain it doesn't really help them. They are more likely to get confused and drop the topic.

(Kudos to those people who give highly relevant, insightful, simple, and intuitive answers, you guys are the best).

Which side are you on? Lol

The average functional programmer

Learning Haskell, I'm loving it!

Functional Programming literally has 'fun' in the title; OOP is one letter away from 💩. I rest my case.

2 days into a new java project and I already miss scala so much.

I like this scala library because it's called "cats" 🐱

When I hear, "master/slave" I don't think about terminology and syntax for a programming language I dislike because of its silly functional indent requirements. I think of jumper settings on IDE hard disks in the '90s. Primary master, secondary master, primary slave, secondary slave.

It works. It finally works!

After an 8 hour session I got my crawler to work and give me basically every anime op/ed I long for.
All that using Elixir even though I'm still fairly inexperienced with both elixir and functional programming

I'll try to create an API and eventually Maybe even a database tomorrow (or rather in a couple of hours)

"I'm almost done, I'll just need to add tests!"

Booom! You did it, that was a nuke going off in my head.

No, you shouldn't just need to add tests. The tests should have been written from the get go! You most likely won't cover all the cases. You won't know if adding the tests will break your feature, as you had none, as you refactor your untested mess in order to make your code testable.

When reading your mess of a test case and the painful mocking process you went through, I silently cry out into the void: "Why oh why!? All of this suffering could have been avoided!"

Since most of the time, your mocking pain boils down to not understanding what your "unit" in your "unit test" should be.

So let it be said:

- If you want to build a parser for an XML file, then just write a function / class whose *only* purpose is: parse the XML file, return a value object. That's it. Nothing more, nothing less.
- If you want to build a parser for an XML file, it MUST NOT: download a zip, extract that zip, merge all those files to one big file, parse that big file, talk to some other random APIs as a side-effect, and then return a value object.

Because then you suddenly have to mock away a http service and deal with zip files in your test cases.

The http util of your programming language will most likely work. Your unzip library will most likely work. So just assume it working. There are valid use cases where you want to make sure you acutally send a request and get a response, yet I am talking unit test here only.

In the scope of a class, keep the public methods to a reasonable minimum. As for each public method you shall at least create one test case. If you ever have the feeling "I want to test that private method" replace that statement in your head with: "I should extract that functionality to a new class where that method public. I then can create a unit test case a for that." That new service then becomes a dependency in your current service. Problem solved.

Also, mocking away dependencies should a simple process. If your mocking process fills half the screen, your test setup is overly complicated and your class is doing too much.

That's why I currently dig functional programming so much. When you build pure functions without side effects, unit tests are easy to write. Yet you can apply pure functions to OOP as well (to a degree). Embrace immutability.

Sidenote:

It's really not helpful that a lot of developers don't understand the difference between unit, functional acceptance, integration testing. Then they wonder why they can't test something easily, write overly complex test cases, until someone points out to them: No, in the scope of unit tests, we don't need to test our persistance layer. We just assume that it works. We should only test our businsess logic. You know: "Assuming that I get that response from the database, I expect that to happen." You don't need a test db, make a real query against that, in order to test that. (That still is a valid thing to do. Yet not in the scope of unit tests.)

This is changing my mind!

.Net is masterrace.
C# gives me frequent orgasms.
Use SQL Server for DB, add to that parallel querying and NoSQL capabilities.
Incredible development speed with EF
Incredebly powerful web framework...check
AI and neural networks...check
App Development...Xeck

If you want to do some of that functional programming F# is the language for you.

And the best thing: .Net core runs on Linux too

Just learning but this is beautiful and feels at home

Me in school: Math? When do I need know those details? I can look them up and just code it.

Me in high school: Computer science is way too math-y. I want to code!

Me coding php: Just make it work.

Me coding typescript: Just make it work.

Me coding scala: Just make it ... what ... how do I make it work!?!

Me asking stackoverflow: How do I do X in scala some functional programming stuff in mind in order to keep immutability.

Somebody way smarter than I: "In scalaz, a function A => A is called an endomorphism and is a Monoid whose associative binary operation is function composition and whose identity is the identity function"

Me now: Fuck my old arrogant self.

I ❤️ F#, this function is both beautiful and was an utter nightmare to create 😂

Run away from functional programming!

(source: alvinalexander.com)

So today I saw another 'OOP should die' article.
And I decided I should google around a bit to find out why.

Reasons I found:
- Things get too complicated
- Things get too abstract (same as the above really)

But when I search for alternatives, only functional programming and different ways to use OOP get mentioned.
I still don't get why OOP is supposedly bad though.
Maybe my 20-30k LOC projects aren't big enough to see it?

For me the abstraction works very well. The abstraction is used to keep the complexity low(er).
And the different ways of using OOP are a plus-point for me. (Like the Entity-Component system)

I don't know enough about functional programming to be able to say it's better or worse, but the ideas behind it a perfectly usable in languages like C#.

So if any of you have a good concrete reason to not use OOP, please feel welcome to tell me in the comments :)

So, this is probably somewhat esoteric but...

While studying at university I had a "programming paradigms" module, dunno why they called it that, it was more like "introduction to functional programming".

So, it's kinda mind bending, we'd only really started to get our heads around classical object oriented programming and they throw functional programming at us.

It's worse than that though, for do they use an established language, like lisp/scheme, functional Python, or even given Haskell?

No, of course they didn't. They taught us Oz.

You probably won't have heard of it, but this language is burned into the back of my brain, along with a vague understanding of the n-queens problem we had to solve graphically (using qTk, which I dunno if someone took qt and tk and blended them, I stopped asking questions after a while).

To top it off did this language (at the time) have a stand alone interpreter? Did it buggery! It was coupled to the Mozart programming system, which is just Emacs (which has a bloody lisp built into it,so close, yet so far 😭).

It gets worse, though, oh does it get worse, for pause dear reader and consider, have you ever heard of Mozart/oz before, I'd put money on most of you had not heard of it until today.

For, you see, I believe at the time of writing, one, yes, ONE text book exists on this language. When I was doing my assignment there was merely some published conference notes and language design documents.

That's not all, I was not the only one experiencing difficulties with this language, someone in the class ended up pouring through the mailing lists and found the very tutor teaching the class struggling at first to understand the language.

I had to repeat that year. The functional programming class was one semester.

When I retook that year, it was a whole year long. However, halfway through the year, original tutor was fired and a new tutor was hired to teach the language.

He was, understandably, just as confused as we were.

There was a Starbucks and a pub equidistant from the lecture hall, though in opposite directions. From lecture to lecture we had no idea which one we'd end up in.

I have reason to believe Mozart/Oz it some sort of otherworldly abomination designed to give students the occasional nightmare flashback, long after they've left.

My room had post it notes, sheets of paper, print outs, diagrams, doodles and pens, just stuck to the wall, I looked like a raving lunatic three hours away from being institutionalised. There was string connecting one diagram to the next and images of a chess queen all over. As I attempted to solve the n-queens problem.

Madmans knowledge, I call it. I can never unlearn all that, in fact it seeps into much of the code I write. Such information was not meant for the minds of a simple country bumpkin such as myself...

Mozart/Oz... I wouldn't be the programmer I am today without it, and that's frankly terrifying...

The worst architecture I've seen is WordPress.
How can you be so drunk to design such a filthy mess?
In some way PHP might be to blame. Its API is a fucking mess as well and may have stirred WP developers in this puke around so they couldn't come up with a better CMS architecture.
Don't get me wrong. I do love PHP. But only in it's OO form with namespaces and type hints and composer dependencies.

I've seen enough of PHP functional programming and it still haunts me.

So... I joined the Blacker black side and shit's awesome!
Anyways, just wanted to take a break from my Functional Programming study for my exam I have on Tuesday. My brain's a mess rn.

In a getting started tutorial about Haskell:

"You probably already have haskell installed because you tried to learn it once and failed"

He's so right...

For loops are for noobs.

What do functional programmers eat?

My freelance horror story just happened a few weeks ago. Programming final project was due and a classmate payed me to make his project. It was something very simple so I was able to make mine and his different and functional. Grades went up yesterday; he got an A and I got a B+ 🙃 #wk86

I’m done with people that derail meetings and discussions.

While I want to seek feedback for an Interface that I wrote, these attention seekers decide it’ll be the perfect opportunity to bring up the topic of “how functional programming paradigm facilitates better encapsulation”.

Everyone else follow suit. I try “time checking” and bringing the talk back on track. Never worked.

I’m concluding that meetings are shit and a COLOSSAL WASTE OF TIME.

-I'm gonna learn C for real
-I'm gonna configure Vim
-I'm gonna try November
-Emacs with Evil mode is a better Vim
-I'm gonna learn eLisp
-I'm gonna learn functional programming
-Gonna use clojure for everything now!
-init.el is 400 lines long

int main() {printf("Hello World!");}

Success! 🤦‍♂️

This takes me back 14 years to the past when I first started learning VB.Net and Console Apps.
Learning F# to get my self into functional programming let's hope I don't get carried away with the ability to mix C# with F# :\

Functional programming vs object oriented programming.

I don't believe one can replace the other I just want to know some other people's opinions.

I could write 20 pages ranting but it can be summarized in a few words that describe the situation pretty well:

My 'CTO' doesn't understand basic OO principles (say, inheritance) nor functional programming.

Code written in Lambda Functions and Streams in Java 8

I want the pipeline-operator in JavaScript. I want it now!

... But then I mostly work with Vue.js (because it's awesome) in the last time and I somehow miss vanilla JavaScript. Life is cruel.

Thank you for all the recommendations and sorry for ignoring them.
I'll try F# for now.

I prefer functional style programming because it is easier to me to think in modules and functional hierarchies than it is object style shierarchies.

All in all, languages like F# and Clojure have always been fascinating to me. I wish I could find a use case for Haskell, but I can't. If anything F# is awesome to me because I already know .NET and really dig the entire framework, the strides made by Core are outstanding.

I had tried Scala before and just couldn't get into it. Far easier to just stick to Java even if I hate the idea of extending classes all over the place.

Ocaml is interesting too, but I know little to nothing about it, and Elixir looks far too much like Ruby for my taste even if I do like Ruby.

Choice is good, but sometimes overwhelming

!rant

Need some opinions. Joined a new company recently (yippee!!!). Just getting to grips with everything at the minute. I'm working on mobile and I will be setting up a new team to take over a project from a remote team. Looking at their iOS and Android code and they are using RxSwift and RxJava in them.

Don't know a whole lot about the Android space yet, but on iOS I did look into Reactive Cocoa at one point, and really didn't like it. Does anyone here use Rx, or have an opinion about them, good or bad? I can learn them myself, i'm not looking for help with that, i'm more interested in opinions on the tools themselves.

My initial view (with a lack of experience in the area):

- I'm not a huge fan of frameworks like this that attempt to change the entire flow or structure of a language / platform. I like using third party libraries, but to me, its excessive to include something like this rather than just learning the in's / out's of the platform. I think the reactive approach has its use cases and i'm not knocking the it all together. I just feel like this is a little bit of forcing a square peg into a round hole. Swift wasn't designed to work like that and a big layer will need to be added in, in order to change it. I would want to see tremendous gains in order to justify it, and frankly I don't see it compared to other approaches.

- I do like the MVVM approach included with it, but i've easily managed to do similar with a handful of protocols that didn't require a new architecture and approach.

- Not sure if this is an RxSwift thing, or just how its implemented here. But all ViewControllers need to be created by using a coordinator first. This really bugs me because it means changing everything again. When I first opened this app, login was being skipped, trying to add it back in by selecting the default storyboard gave me "unwrapping a nil optional" errors, which took a little while to figure out what was going on. This, to me, again is changing too much in the platform that even the basic launching of a screen now needs to be changed. It will be confusing while trying to build a new team who may or may not know the tech.

- I'm concerned about hiring new staff and having to make sure that they know this, can learn it or are even happy to do so.

- I'm concerned about having a decrease in the community size to debug issues. Had horrible experiences with this in the past with hybrid tech.

- I'm concerned with bugs being introduced or patterns being changed in the tool itself. Because it changes and touches everything, it will be a nightmare to rip it out or use something else and we'll be stuck with the issue. This seems to have happened with ReactiveCocoa where they made a change to their approach that seems to have caused a divide in the community, with people splitting off into other tech.

- In this app we have base Swift, with RxSwift and RxCocoa on top, with AlamoFire on top of that, with Moya on that and RxMoya on top again. This to me is too much when only looking at basic screens and networking. I would be concerned that moving to something more complex that we might end up with a tonne of dependencies.

- There seems to be issues with the server (nothing to do with RxSwift) but the errors seem to be getting caught by RxSwift and turned into very vague and difficult to debug console logs. "RxSwift.RxError error 4" is not great. Now again this could be a "way its being used" issue as oppose to an issue with RxSwift itself. But again were back to a big middle layer sitting between me and what I want to access. I've already had issues with login seeming to have 2 states, success or wrong password, meaning its not telling the user whats actually wrong. Now i'm not sure if this is bad dev or bad tools, but I get a sense RxSwift is contributing to it in some fashion, at least in this specific use of it.

I'll leave it there for now, any opinions or advice would be appreciated.

Haskell, Scala or Erlang?

Why does every Software Engineering role at the top companies never have PHP or any functional languages in it’s list of languages they want you to be experienced in?

It’s always Java, Python, C#, C/C++, Objective C or Ruby. What about Elixir, Scala, Haskell or Clojure?

Next week I'm starting a new job and I kinda wanted to give you guys an insight into my dev career over the last four years. Hopefully it can give some people some insight into how a career can grow unexpectedly.

While I was finishing up my studies (AI) I decided to talk to one of these recruiters and see what kind of jobs I could get as soon as I would be done. The recruiter immediately found this job with a Java consultancy company that also had a training aspect on the side (four hours of training a week).

In this job I learned a lot about many things. I learned about Spring framework, clean code, cloud deployment, build pipelines, Microservices, message brokers and lots more.

As this was a consultancy company, I was placed at different companies. During my time here I worked on two different projects.
The first was a Microservices project about road traffic data. The company was a mess, and I learned a lot about company politics. I think I never saw anything I built really released in my 16 months there.

I also had to drive 200km every day for this job, which just killed me. And after far too long I was finally moved to the second company, which was much closer.

The second company was a fintech startup funded by a bank. Everything was so much better than the traffic company. There was a very structured release schedule, with a pretty okay scrum implementation. Every team had their own development environment on aws which worked amazingly. I had a lot of fun at this job, with many cool colleagues. And all the smart people around me taught me even more about everything related to working in software engineering.

I quit my job at the consultancy company, and with that at the fintech place, because I got an opportunity I couldn't refuse. My brother was working for Jordan Belfort, the Wolf of Wallstreet, and he said they needed a developer to build a learning platform. So I packed my bags and flew to LA.

The office was just a villa on the beach, next to Jordan's house. The company was quite small and there were actually no real developers. There was a guy who claimed to be the cto of the company, but he actually only knew how to do WordPress and no one had named him cto, which was very interesting.
So I sat down with Jordan and we talked about the platform he wanted to build. I explained how the things he wanted would eventually not be able with WordPress and we needed to really start building software and become a software development company. He agreed and I was set to designing a first iteration of the platform.
Before I knew it I was building the platform part by part, adding features everywhere, setting up analytics, setting up payment flows, monitoring, connecting to Salesforce, setting up build pipelines and setting up the whole aws environment. I had to do everything from frontend to the backest of backends. Luckily I could grow my team a tiny bit after a while, until we were with four. But the other three were still very junior, so I also got the task of training them next to developing.
Still I learned a lot and there's so much more to tell about my time at this company, but let's move forward a bit.

Eventually I had to go back to the Netherlands because of reasons. I still worked a bit for them from over here, but the fun of it was gone without my colleagues around me, so I quit last September.

I noticed I was all burned out, had worked far too much, so I decided to take a few months off and figure out what I wanted to do with my life. I even wondered whether I wanted to stay in programming.

Fast forward to last few weeks. I figured out I actually did want to work in software still, but now I would focus on getting the right working circumstances. No more driving 3 hours every day, no more working 12 hours every day. Just work close to home and find a company with the right values.
So I started sending out resumes and I gave one recruiter the chance to arrange some interviews too. I spoke to 7 companies in the span of one week. And they were all very interested. Eventually I narrowed it down to 2 companies and asked them for offers. And the company that actually had my preference offered me significantly more than I asked for, which settled the deal.

So tomorrow I'm officially signing with them, and starting next week I'll be developing in Kotlin, diving into functional programming and running our code in serverless environments. I'm very excited!

It is still blowing my mind how a button on my raspberry pi is programmatically functional in the same way as if I was programming a database and web app.

Fucking eh, why haven't I been doing this hardware stuff sooner? You can literally make physical shit happen. That is so cool!

A year ago I ranted, that I understood JavaScript callbacks.

That was a lie. I knew nothing.

But I think I scratched the surface by getting into functional programming this time.

New wall paper

Any Haskell programmers here?
I started to learn this language for fun two days ago and so far I find it absolutely amazing and really different to OOP languages. Most of the time the solutions make so much sense, but actually coding them requires really abstract thinking of the problem. How fast did you learn Haskell? How long it took you do code it comfortably? Any advises you can give me? I work mainly through a uni exercise sheet from a friend from a different uni, and the rest is hoogle and google :P

!rant

so the other day i was programming and suddenly i wanted to learn haskell. (i don't know why it hit me so suddenly, maybe because it's a 'pure' functional programming language and these 2 terms i knew nothing about)

and to be honest it's really hard coming from an imperative programming language (C/C++, yes, i know they are different in their ways). it's like learning to program again! you really have to get a different mindset and for me honestly it's hard to grasp the idea that 'variables' are immutable! like, that's soooo weird it still stucks to me. for example how did they define the max or min function without using a while loop? what are monads?

I am just 2 days in but it'll be a fun ride!

What I'm doing now, writing a JS library for a simple kitchen timer (like, something that can be wound up, is ticking, can be paused, etc). Here's a list of neat stuff I've learned:

Polyfilling as a lib author (I decided against it).
Packaging the lib (using Rollup, ES6 modules are totes cool).
Using flow to add static typing in strategic places (started appreciating types in JS since reading up on functional programming).
Modelling state and transitions using an explicit state machine. (Fucking finally. There's usually an implicit state machine somewhere, only spread out all over the app...)
Using mostly side-effect free methods, being very explicit about when and why things are mutated).
Test-first/TDD (ish) using Jest and the awesome Wallabyjs.
Freeing up mental capacity by letting Prettier format my code for me (it was hard to let go but totally worth it).
Started using git.

Did all work on Ubuntu after pretty much a lifetime of Windows (initially to separate work from gaming) and finally swapped MS Visual Studio for Atom.

When it's finished I'm going to publish it on GitHub, which will also be a first for me. Might try out some CI platform while I'm at it.

tl;dr: wrote some js, felt good

One day after typescript , I ditch JavaScript on es5 totally and my college education on objective orient finally pays off ! !

I love functional programming but still insist that objective oriented is better for large project

I know functional programming is hip now, but I wonder if I'll ever see a day when it's considered cutting edge to make every variable global. Possible twilight zone episode?

So guys, do you think I should learn one functional programming language and if so should it be haskell?

Why is it that virtually all new languages in the last 25 years or so have a C-like syntax?

- Java wanted to sort-of knock off C++.
- C# wanted to be Java but on Microsoft's proprietary stack instead of SUN's (now Oracle's).
- Several other languages such as Vala, Scala, Swift, etc. do only careful evolution, seemingly so as to not alienate the devs used to previous C-like languages.
- Not to speak of everyone's favourite enemy, JavaScript…
- Then there is ReasonML which is basically an alternate, more C-like, syntax for OCaml, and is then compiled to JavaScript.

Now we're slowly arriving at the meat of this rant: back when I started university, the first semester programming lecture used Scheme, and provided a fine introduction to (functional) programming. Scheme, like other variants of Lisp, is a fine language, very flexible, code is data, data is code, but you get somewhat lost in a sea of parentheses, probably worse than the C-like languages' salad of curly braces. But it was a refreshing change from the likes of C, C++, and Java in terms of approach.

But the real enlightenment came when I read through Okasaki's paper on purely functional data structures. The author uses Standard ML in the paper, and after the initial shock (because it's different than most everything else I had seen), and getting used to the notation, I loved the crisp clarity it brings with almost no ceremony at all!

After looking around a bit, I found that nobody seems to use SML anymore, but there are viable alternatives, depending on your taste:

- Pragmatic programmers can use OCaml, which has immutability by default, and tries to guide the programmer to a functional programming mindset, but can accommodate imperative constructs easily when necessary.
- F# was born as OCaml on .NET but has now evolved into its own great thing with many upsides and very few downsides; I recommend every C# developer should give it a try.
- Somewhat more extreme is Haskell, with its ideology of pure functions and lazy evaluation that makes introducing side effects, I/O, and other imperative constructs rather a pain in the arse, and not quite my piece of cake, but learning it can still help you be a better programmer in whatever language you use on a day-to-day basis.

Anyway, the point is that after working with several of these languages developed out of the original Meta Language, it baffles me how anyone can be happy being a curly-braces-language developer without craving something more succinct and to-the-point. Especially when it comes to JavaScript: all the above mentioned ML-like languages can be compiled to JavaScript, so developing directly in JavaScript should hardly be a necessity.

Obviously these curly-braces languages will still be needed for a long time coming, legacy systems and all—just look at COBOL—, but my point stands.

How the Common Lisp Community will eventually die soon:

Clojure is the only main Lisp dialect having some sort of heavy presence in today's modern development world. Yes, I am aware of other(if not all) environments in which Lisp or a dialect of it is being used for multiple things, CADLisp, Guile Scheme, Racket, etc etc whatever. I know.

Not only is Clojure present in the JVM(I give 0 fucks about whether you like it or not also) but also has compilation targets for Javascript via Clojurescript. This means that i can effectively target backend server operations, damn near everything inside of the JVM and also the browser.
Yet, there is no real point in using Lisp or Clojure other than for pure academic endeavours, for which it is not even a pure functional programming language, you would be better served learning something else if you want true functional purity. But also because examples for one of the major areas in software development, mainly web, are really lacking, like, lacking bad, as in, so bad most examples are few in between and there is no interest in making it target complete beginners or anything of the like.

But my biggest fucking gripe with Lisp as a whole, specifically Common Lisp, is how monstrously outdated the documentation you can find available for it is.

Say for example, aesthetics, these play a large role, a developer(web mostly) used to the attention to detail placed by the Rails community, the Laravel community, django, etc etc would find on documentation that came straight from the 90s. There is no passion for design, no attention to detail, it makes it look hacky and abandoned. Everything in Lisp looks so severely abandoned for which the most abundant pool of resources are not even made present on a fully general purpose language constrained as a scripting environment for a text editor: Emacs with Emacs Lisp which I reckon is about the most used Lisp dialect in the planet, even more so than Clojure or Common Lisp.

I just want the language to be made popular again y'know? To have a killer app or framework for it much like there is Rails for Ruby, Phoenix for Elixir, etc etc. But unless I get some serious hacking done to bring about the level of maturity of those frameworks(which I won't nor I believe I can) then it will always remain a niche language with funny syntax.

To be honest I am phasing away my use of Clojure in place of Pharo. I just hate seeing how much the Lisp community does in an effort to keep shit as obscure and far away from the reach of new developers as possible. I also DESPISE reading other Lisp developer's code. Far too fucking dense and clever for anyone other than the original developer to read and add to. The idea that Lisp allows for read only code is far too real man.

Lisp has been DED for a while, and the zombies that remain will soon disappear because the community was too busy playing circle jerks for anything real to be done with it. Even as the original language of AI it has been severely outshined by the likes of Python, R and Scala, shit, even Javascript has more presence in AI than Lisp does now a days.

Me: Spend lots of free time (evenings, weekends, sometimes even mornings) learning new languages, new architectures, new libraries. A lot of effort so I'm at the top of the current tech. Swift, Kotlin, MVVM, MVP, C++, functional programming, reactive programming, continuous integration, unit testing...

Get a new job - once again I have to clean up some shitty code, written by someone who went from Java script to objective c, without reading a single book on iOS development. Unused code, commented out code, redundant code, dead code. Unused assets that no one could be bothered to remove for the past 2 years.

Sometimes I wonder why do I even bother if all I ever do is maintain mess done with outdated tech by someone who couldn't give a 🐙🐙🐙

1. Remove 'this.' from your js-syntax.
2. Be happy.

Functional programming literally has 'fun' in the title. OOP is one letter away from 💩

I'm about to take full responsibility for front-end solutions plus doing UI/UX design, and I've pretty much completed the official React and Redux tutorials.

In my defense I only said I was interested in UX but I have a creeping suspicion they think I'm a UX God.

I also used AngularJS for years and I feel that React speaks to me in a completely different way. It's exactly how I want to do things. Big fan of functional programming as well... So I think I'll thrive with React/Redux and friends if I can get some hours in before things kick off. It's just enough pressure for me to put in the work without feeling overwhelmed... for now.

It's thrilling though. I'm somewhere between excited that I'll get to show off my skills and scared that I'll be exposed as a fraud. I have a mild case of impostor syndrome though, so I think it'll work out in the end.

Functional programming is just writing everything as a one liner!!!

Change my mind

I'm trying to learn functional programming with Elixir. Wish me luck.

That moment when you're very happy you just completed a hard Haskell kata in CodeWars, with 8 lines, three functions, a lot of functional concepts (which would take at least 30 lines in Java or C#) and they show you the top voted solution by another user with JUST TWO LINES and a lot of function composition.

My first rant. Woohoo!

Honestly I do the whole shebang ussualy depending on what the needs are from network to servers to coding because for some reason nobody has any technical experience where I work.
I just started app development for a gamedev startup and I am in sheer awe of the amount of transpiling/compiling etc that needs to be done for an multiplatform app for iOS and android with js(x)/typescript, html, css.

I remember when I could just write some spaghetti code to make it working by following a couple of tutorials. Then refractoring and testing it for a couple of hours and be done with it. push it into production.

Now I am lost having to learn OOP, functional programming, reactjs, react native, express, webpack, mongodb, babel, and the list goes on and on...
Why not just make a new backend that does all of that in another language which supports all of that.

I have no formal education in programming/coding and the last time I learned JS it was just some if else, switches and simple dom manipulation.

I just want to get to coding a freakin' game but I have to learn JSX for the front and typescript on the backend.

I am this close to going back to ye ol' lamp stack and quitting this job. 😥

I would like to get a little bit into functional programming.
Do you have any language suggestions to learn?

I am wondering how a #FunctionalProgramming based implementation of a Binary Search Tree would look like?

Has anyone tried it?

I'm still pretty new to elixir and functional programming. There have been numerous cases where I accidentally recreated functions such as Enumerable.map 😅

I mean JavaScript is all cool and everything, but without type safety, it becomes gigantic pain in my ass :'(

Is there anybody who feels the same? :(

Trying out pure functional programming in javascript. First few weeks: wow, this is so fresh, oop can die, etc. Now: this isn't readable at all! 😐

I was very proud that I know some different programming languages.

Until I see some functional programming, trying haskell, and spend hours in order to understand what's going on...

I see everyone complaining here, what old and shitty languages their university are using. So, I want to tell my past experience with unis too.

First time I was studying (software engineering), after I have had finished high school. There was this teacher, he was like 60-70 years old. So, he gave us assignment for the semester - to create GUI application using VBE. Damn, that shit was old. I hate excel ever since... And yeah I quit that university at the end of the semester.

Second time, was after the year, this time I left my home country and went to the Netherlands. I was studying artificial intelligence. At the second semester, there was functional programming course. I was really excited about it, but you can’t fucking imagine how disappointed I was when it started. It was some next level shit. So university had created their own functional programming language in the 90s, the one that was used in this course. It’s called clean (google or ddg, it very serious shit), and syntax is very similar to haskell. But well, the language itself wasn’t so bad. What was bad, that compiler worked only on fucking windows, and I don’t even talk about documentation... And yeah, it had one man community - it was our teacher. In the end of the year I quit again, though there were other reasons (course felt more like law, than the IT)...

I hate it when someone says 'syntactic sugar' and on the other hand wants code to be readable. For me it seems that this are wheels which chain together.

My Gripe With Implicit Returns

In my experience I've found that wherever possible code should be WYSIWYG in terms of the effects per statement. Intent and the effects thereof should always be explicit per statement, not implicit, otherwise effects not intended will eventually slip in, and be missed.
It's hard to catch, and fix the effects of a statement intent where the statement in question is *implicit* because the effect is a *byproduct* of another statement.

Worse still, this sort of design encourages 'pyramid coding recursion hell', where some users will first decompose their program into respective scopes, and then return and compose them..atomically as possible, meaning execution flow becomes distorted, run time state becomes dependent not on obvious plain-at-sight code, but on the run time state itself. This I've found is a symptom of people who have spent too much time with LISP or other eye-stabbingly fucky abominations. Finally implicit returns encourage a form of thinking where programmers attempt to write code that 'just works' without thinking about how it *looks* or reads. The problem with opaque-programming is that while it may or may not be effortless, much more time is spent in reading, debugging, understanding, and maintaining code than is spent writing it--which is obviously problematic if we have a bunch of invisible returns everywhere, which requires new developers reading it to stop each and every time to decide whether to mentally 'insert' a return statement.

This really isn't a rant, as much as an old bitter gripe from the guy that got stuck with the job of debugging. And admittedly I've admired lisp from afar, but I didn't want to catch the "everything is functional, DOWN WITH THE STATE" fever, I'm no radical.

Just god damn, think of the future programmer who may have to read your code eventually.

Lead: alright people what are your ideas and updates for this page refactor we've been talking about.

dipshit: Alright guys, I've done a quick awesome prototype that I really like...

dipshit: *starts to speak super fast* (I catch words about function composition, clean, no side effects, speed, efficiency. Basically a string of brogrammer buzzwords.)

me: what did you mean by that? How does it work?

dipshit: *basically repeats the same drivel*

me: uh..ok I don't quite understand

everyone else looks confused.

me: ok since you've done a prototype, we take a look at it later

*** After meeting, looks at code ***

It was COMPLETE GARBAGE. He used 1,500+ lines of js in 17 files to make what was essentially a simple 2 item list.

We were looking at a way to overhaul the entire page, he "refactored" maybe perhaps 5% of the page.

There was absolutely nothing clean / functional / composable about this monstrosity. It was as if he read chapter 1 of a book on functional programming and decided he understood enough to call himself an expert.

WHY THE FUCK ARE YOU STILL HIRED?

HOW DO YOU CALL YOURSELF A DEVELOPER?

YOU ARE SELF TAUGHT, DISS PEOPLE WITH FORMAL CS/CE DEGREES AND YOU PRODUCE TRASH CODE?!

ARE YOU SO RETARDED THAT YOU DO NOT RECOGNIZE HOW STUPID YOU ARE?

Please die in a fire, along with your jock attitude and unprofessionalism. Take this worthless junk unfit to be called code with you.

Ban visual programming programs, like scratch after the fist month introduce them to enhanced Google search strings and let them code on the command line going from imperative, over functional to object oriented programming styles using languages suited for the current style. Not like using Java from the get go. I hated it, waiting until everyone got to the point where they kind of understood the logic but failed at using correct syntax and efficient coding styles.

Learn JavaScript.!!

Everybody talk about functional programming, I was thinking why php json_encode is not working on large array.

Javascript is Awesome.

Functional programming instead of imperative

I have lately seen a lot of people mentioning that functional programming is better than object oriented programming.

So far I have only experience in oop and I would really like to know some reasons why it is better.

A few weeks ago I posted that my boss allowed to use python for a project we gonna start soon.

Well, after trying out python for one of my side projects, now I think that I should stay with PHP after all.

I mean, python is nice and everything, but as I observed it has it’s own problems. One of them that confused shit out of me was python 2 and 3 versions. Just what the fuck, even php manages successfully migrate to new versions (well I can think some possible explanations, but it doesnt change the fact). I also didn’t like OOP, no interfaces (just abstract classes), no properties visibility (just notion by standards). And then, there are hell too much features, just why they try to make functional language from oop one (i mean all the types system)? Finally, it’s slow. Yeah, yeah, I know, use pypy, cpython.. well, I don’t want to, cuz again it’s fucking confusing. And besides all the amazing ecosystem python has, there is no actual win by ditching php.

Well, to be honest I don’t know what to do, I am supposed to be professional who does, but fuck it, I am confused as fuck, why programming is so fucking hard?

Maybe I just should use golang in conjuction with php?

Not knowing what persistence was and copying JS objects with JSON.parse(JSON.stringify(...)) trying to make it “pure immutable”.

Fml.

I'm on leave but my brain won't stop thinking about ways to refactor that one js module I was working on yesterday into a functional one.

The fuck, brain?? I'm doing you a favor here by letting you take a day off!

Pet peeve: the claim that static typing prevents errors.

Today I worked on a C# project that's a mess of nulls, side-effects, inferences, and race conditions. Then I went back to a JS project that's twice the size but written in a clean, well-tested, FP style and currently has fewer than 10 issues logged.

Look, I get that there are upsides to static typing, and I'm open to introducing typescript or flow for our JS code.

I just can't stand the faux-concern from the static typing dingleberries when they are the ones who produce these horrendous lumps of unmaintainable shit, and the JS/Python/Ruby/etc people are over here quietly reinventing functional programming and code modularity.

My classmate and I stumbled into the idea of third wave programming, like the waves of feminism but coding.

The first is functional programming, the second is object oriented programming, and the third is making everything in electron and bundling an entire chrome in your application.

I'm falling in love with Scala

A functional developer kills a man. When the police arrests him, he gets very surprised. He thought he was stateless.

I read the pragmatic programmer a few months ago. The book advised learning a different programming language every month or so. I was doing Advent of Code so I decided to try out Elm because functional programming is all the rage these days.
It took me one hour to convert a string of numbers to an array of numbers! And when I finally finished with that I couldn't understand how to compare each element with the next one in an array using map or filter.
I realised that I've become too comfortable using javascript. Worst case scenario: In a few years when javascript is obsolete I'll be like those old dudes that know only Cobol. Best case scenario: I'll always be too dumb to earn a nice salary.
On a positive note: The first time I tried Elm I didn't understand jack shit, now I understood a few things.

When you try reactive programming.

React has been a gateway into the practical functional world.

Having a crack at Clojure/Om/Datomic, and then recognising the roots of functional and immutable programming that I've seen before.

I have a lot to learn.

Looking forward to grasping macros fully. Walk before I run though

I learned to program with Game Maker, downloading examples and changing variables to see what they did. After that I wanted to make websites so I followed tutorials and just see what happened if I changed variables and functions. Then came High School where we had exercises with Java and just experimented with the possibilities.

Then in Uni I learned about OOP and Functional which opened even more worlds. After a class on design patterns and designing the architecture of a system, programming was never the same.

And even until this day, I haven't stopped learning better ways to code. Oh how I long for those days where everything is new and how I can build a hello world application and be truly excited about it! That is how I learned to program and why I won't stop anytime soon. 😁

Should I learn Haskell? Would it help me with other coding languages as well?
My main language is JavaScript, also I would like to learn functional programming.

Just watched a video called "object oriented programming is bad" on youtube. Saying that we all should use functional programming only. Your thoughts?

USE F🤬 GNU/LINUX!!! After, make technology really available (there’s cheap but functional options like ltsp). Teach the f🤬 bases of programming! Use open source softwares! How Internet works and privacy thing! Learn to read f🤬 terms of contract and privacy things, teach that ie is fucking shit and also, the most important thing! Use dark theme, don’t hurt others like I was!

And also, use vim

!rant

You knoe, my first insights into computer programming came out of spite. I thought windows to be garbage and wanted to blame someone other than myself for my machine constantly crashing. Thus I discovered programming and down the rabbit hole. But my interest in computer science came from videogames. Portal in particular. I found the idea of GlaDOS fascinating and thought that artificial intelligence would be something interesting to research. The web then gave me Lisp, and boy was the language different from all the other languages I went through. I remember feeling super excited when Racket, Common Lisp and eventually Clojure would help me discover many different ideas. Every time I work with reduce or maps or stuff like that in other languages I always thank languages such as Clojure for having me descipher different ways of manipulating data to get a result. To this day I feel sad whenever I find that my languages do not have the same constructs that Clojure has. I mention Clojure because it is my favorite flavor of Lisp. But one thing that always remains grest to me is firing up Emacs and plugin my code to Slime or Cider and see the repl pop up waiting for something to happen. This feeling is beautiful.

Please guys, if you have not tried it, do so! You might hate it at first or push it aside. But trust me, once you get it it will really change the way you think about programming in general. Try the great Clojure for the Brave and true, and go through the third chapter succesfully. If you do not like Lisp by them then no harm done! You would at least know that there are other options.

Now, here are some cool things:
For the standard implementation, try Common Lisp

For a more modern Scheme, try Racket or Guile

For targetting the JVM try Clojure (more akin to Common Lisp) or Kawa (scheme like)

For the python AST get Hy (pun totally intended)

For JS try Clojurescript

For emacs scripting try Emacs Lisp (has way too many disasdvantages but still relatively close to common lisp)

Honorific mention to more pure functional programming languages for Haskell, F#, Ocaml.

Also worth mentioning that Js , Ruby and Python have great functional constructs.

(println "you will not regret it!")

Do you guys know a cool language to get a bit more into functional programming?
Doesn't matter if purely functional or a mashup of functional and imperative programming.
And please a real-world language, let Haskell stay in its Ivory-tower where it belongs.

Functional programming languages...

Functional Programming being touted as the silver bullet for all types of modern programming challenges.

Why? As far as I can tell, it doesn't deliver. Sure certain approaches help with specific kinds of problems. Yet, it is cumbersome for general purpose problems and downright harmful for performance critical problems. For doing math problems it is great and I see value. For most else, eh, I have work to do.

Stuck between functional programming and the other one.

Started to learn haskell.
.
.
.
suddenly my whole life seemed to become a 'list' of events 🤐😔

Alright everyone. Who uses elixir and how do you like it? Thinking of writing a fairly large application using elixir and Phoenix

I came from a procedural background, then adopted object-oriented programming, and now I am very enthusiastic about functional programming. Is this kind of an evolutionary path as a programmer? Or am I just late to the party?

And what paradigm follows?

So, JQuery is a functional programming language?! Why did nobody tell me!

Complete my Clojure POC and do a knowledge sharing session in work on Functional Programming. Also get promoted to Senior Software Engineer.

man... fuck java's approach to lambda expressions and like passing functions as arguments and the lot.
it's honestly just so terribly bad. it's sucks so much.

WARNING - a lot of text.
I am open for questions and discussions :)

I am not an education program specialist and I can't decide what's best for everyone. It is hard process of managing the prigram which is going through a lot of instances.
Computer Science.
Speaking about schools: regular schools does not prepare computer scientists. I have a lot of thoughts abouth whether we need or do NOT need such amount of knowledge in some subjects, but that's completely different story. Back to cs.
The main problem is that IT sphere evolves exceedingly fast (compared to others) and education system adaptation is honestly too slow.
SC studies in schools needs to be reformed almost every year to accept updates and corrections, but education system in most countries does not support that, thats the main problem. In basic course, which is for everyone I'd suggest to tell about brief computer usage, like office, OS basics, etc. But not only MS stuff... Linux is no more that nerdy stuff from 90', it's evolved and ready to use OS for everyone. So basic OS tour, like wtf is MAC, Linux (you can show Ubuntu/Mint, etc - the easy stuff) would be great... Also, show students cloud technologies. Like, you have an option to do *that* in your browser! And, yeah, classy stuff like what's USB and what's MB/GB and other basic stuff.. not digging into it for 6 months, but just brief overview wuth some useful info... Everyone had seen a PC by the time they are studying cs anyway.. and somewhere at the end we can introduce programming, what you can do with it and maybe hello world in whatever language, but no more.. 'cause it's still class for everyone, no need to explain stars there.
For last years, where shit's getting serious, like where you can choose: study cs or not - there we can teach programming. In my country it's 2 years. It's possible to cover OOP principles of +/- modern language (Java or C++ is not bad too, maybe even GO, whatever, that's not me who will decide it. Point that it's not from 70') + VCS + sime real world app like simplified, but still functional bookstore managing app.
That's about schools.

Speaking about universities - logic isbthe same. It needs to be modern and accept corrections and updates every year. And now it depends on what you're studying there. Are you going to have software engineering diploma or business system analyst...
Generally speaking, for developers - we need more real world scenarios and I guess, some technologies and frameworks. Ofc, theory too, but not that stuff from 1980. Come-on, nowadays nobody specifies 1 functional requirement in several pages and, generally, nobody is writing that specification for 2 years. Product becomes obsolete and it's haven't even started yet.
Everything changes, whether it is how we write specification documents, or literally anything else in IT.

Once more, morale: update CS program yearly, goddammit

How to do it - it's the whole another topic.

Thank you for reading.

How many of you feel functions API in Java8 should have support wiring up a Function and a Consumer :/

What fo you think, is it still a good idea to learn fortran in order to learn programming concepts?
I don't know what else would be nice...
I only had experience with shell scripting, which is rather functional.
Other languages i considered were dlang, c#, go and rust.
I have no explict application, which bothers me a lot.

It's impossibru: I'm doing RxJava + RxKotlin + RxAndroid and I'm understanding it.

Somewhat.

My tests pass, at least that's something. It's not yet doing completely what I want, but the hardest part is behind me. 🤩

I realized only now that OOP is POO when read backwards. I wonder if this is a secret message encoded by somebody to make us all switch to functional programming

Do we have any C# devs who have switched to Scala?

I've got a very sweet job offer... at a company that develops in Scala. On the one hand, I'm pretty pleased with my depth of C# knowledge, for a variety of reasons. And I've been targeting .Net shops in my job search.

They know Scala devs are rare, so they are aware they need to train new employees, which is nice. But I don't have strong opinions yet on whether this is a language I want to pivot to.

Does anyone have any thoughts/opinions/experiences?

How do I become good with functional features(map,reduce,filter,zip,flatmap) in Javascript and Python?

It feels so alien. I'm so used to writing plain old loops.
Reading and undersranding this kind of style in other people's code is really hard for me, especially if all this is happeining on the same line.

Next Monday I'll go back to work after vacation and I'm still wondering what the fuck is a monad!

3 weeks into Elixir and Functional programming in general. Words can't describe how much I love developing software with this toolset. Can this get any better ?

dev && !rant

I am thinking about picking up a functional language. Currently I use Kotlin (and I fucking love that language) but I have to admit that it's support for functional programming is limited.

But I think their lies a certain beauty in fp and I want to do some project with it.

The 2 main problems are:
1. I have no experience in functional programming. I have no clue how to structure my program (potantialy without oop) and write clean testable code.
2. I don't know what language to use. Scala seems great since it has good IDE support and I like the Java ecosystem and Haskell seems to have more beauty but is missing that IDE support and it is very unfamilar for me.

So what do you guys think I should pick up? And how do I learn to write good software with it?

Finish my only pet project;
Learn a new compiled language;
Get better at functional programming;
Read more books about networks and software engineering;

Today, I used a curry function for the first time outside the context of a classroom/assignment, to solve a real-world problem. boy do I love functional programming.

My apologize to everyone I told that functional programming is declarative.

It's actually imperative. Thank you @AndSoWeCode for figuring that out. I spent the whole day thinking about it.

Lisp is imperative. It's just different way to define the exact data transformations, and that's quite imperative.

On the other hand, HTML, CSS, config files and markup languages are declarative.

But writing the imperative program which is configured with declarative configs seems like great idea. Consider Apache web server and others.

My current side project. I’m doing a POC to upskill in functional programming. A Java/Dropwizard web service calling onto business logic written in Clojure. The bit im excited about is an HTML engine im writing in Clojure. So instead of inter-mixing raw HTML with code, my views will be written entirely in Clojure

As a part of a project in university, we are making an extension to a functional programming language, made in Scala. One of my groupmates had made some fancy logic with spawning threads, but we had some issues with multiple function parameters. Me and another mate have then spent like 3 days trying to figure out the problem, only to realise he forgot a $ sign in string interpolation for naming parameter. Talk about feeling like you're wasting time 🙃

I dare you to beat my wallpaper 🤪

It's kinda cute how people think strict typing is going to prevent bugs and make software reliable. It's all the rage now. I am not saying that there is anything wrong with strict typing but after all it was the original state of affairs and dynamically typed languages where developed to fix it.
Same hype with pure functional programming. It's going to push bugs out to the edges and make everything work. The pursuit of purity is no new thing and it breaks down on contact with the real world, such as a complex JSON. A switch to Haskell won't change that much. I have seen people hunt peculiar bugs in Haskell for ages.

Silly question: what is the main difference between a procedural programming paradigm and a functional paradigm?

Functional Programming Class, an assignment it's that we should develop a calculator, creating our own basic functions (addition implementation with a half-adder and string manipulation).

Teacher tolds us that it has to be coded in Haskell and for the GUI we can use whatever we want, then this fucktard comes around and speaks like he knows everything

Him: Oh, yeah we will use IntelliJ to link the Haskell code with a GUI, because IntelliJ supports Haskell

Me: But IntelliJ it's a(damn) IDE, you still need to code the GUI.

Him: But IntelliJ supports Haskell, we will use it to build the GUI.

Me: Yet what you're trying to say it's that you will use Java to create the GUI and call from there Haskell, and that you will use IntelloJ forms to create the UI

Him: No, no, we're not using Java, we will use IntelliJ, are you dumb? Don't you know what's IntelliJ for?

*Fucking facepalm*

I don't know but at this point I'm not feeling proud that THIS kind of retards are going to graduate in this year...

Implementing a for loop in js because I need to skip some elements in a map as I transform. I'm feeling dirty

* cries in functional *

Just starting with scala. And while I dig the more functional programming approach I am having the hardest of times dealing with naming higher-ordered functions, in my case a function returning another function.

Started out as `foo`, went through quite a lot of changes, and now it has become the beast: `createReplacePriceByPassengerConfigurationMapperFunction`. It won't stay that way but: GOSH! Naming. It's hard! Or I might as well suck at functional programmig. It's not like that these two things are necessarily mutually exclusive.

One of my supervisors once said: "A computer without mutable state is just a glorified electrical heater."

Meaning that at some level you'll need some mutability.
A processor/memory unit without mutability is not worth very much, except if you want to build a new one for every clock tick...

Our company cooperates with a university in training students. In my time that meant learning about HTML, CSS and OOP in the first semester, so that we'd be able to actually do stuff in the company. Nowadays it means learning none of that crap but instead Racket. "What the flying shit is Racket", you ask? "Oh, it's a functional programming language. It has lots of parentheses!", student says. Well fuck me. Out go 2 days of careful planning what task they should be able to handle, in go 3 weeks of tutorials and explaining basic shit they are supposed to learn in university...

I hope that when I wake up in the morning, the racket code I just wrote from midnight to 3am makes as much sense to me as it does at the time of writing.

Banana Language always seems to flow easier when exhausted.

Working with technologies that excite me, which at the moment would be functional programming, CQRS, Event Sourcing, and the actor model, with a side of machine learning and serverless architectures. At a company that is large enough to pay well and grow in, but small enough that my contributions are recognized and appreciated. Or even better, one that I own and run.

The first dev project, like real dev project, I participated in was a school one and it was double.
The class was meant to make us learn about the software's life cycle, so the teacher wanted us to develop a simple, yet complicated, thing: a Web platform to help tutors send/refer students to the university services (psychologist, nutriologist, etc) and to keep track of them visits.
We all agreed on it being easy.
Boy were we so wrong.
I was appointed as dev leader as well as some others (I was the programming leader, the other ones were the DB guy and the security guy) and as such I was in charge of the technology used (well, now we all know that the client is the one in charge of that as well as the designer) and I chose Django because we had some experience with it. We used it for the two projects the teacher asked us to do (the second one was to find a little shop and develop something for it, obviously with the permission and all that), but in the second one I decided to use React on top of Djangl, which ended being a really good combination tho.
So, in the first project, the other ones (all the classroom) started to discuss and decided to use some other stuff like unnecessary carousel for images, unnecessary functions, they created mock ups for stuff that was never there to begin with, etc. It was really awful, we had meetings with the client (the teacher) with updates on the project, and in not a single one he was satisfied with the results. But still, we continued with the path the majority chose and it was the worst: deadlines were not met, team members just vanished until the end of the semester, one guy broke his leg (and was a dev leader) and never said a word not did anything about the project. At the end, we presented literal garbage, the UI was awful, its colors were so ugly because we had to use the university official colors, the functionality was not there, there literally was a calendar to make appointments for the services (when did the client ask for that? No one knows), but hey, you could add services and their data to it, was it what the client wanted? Of course not! What do you think we are? Devs?
Suffice to say that, although we passed with good grades, the project and the team was shit (and I'm counting me in)
The good part is that the second project was finished by me and it looked really good, yet it didn't matter, the first project was supposed to be used by the university, but that thing was unusable.
Then, in the subsequent vacations I tried to make pretty and functional/usable, yet I failed because I had a deadline for another thing I had to do, but hey, the login screen looked amazing!

What's your opinion on functional shortcuts and 'hacks' in many languages, like map/reduce/filter, ternary operator, lambdas,inner/anonymous classes?

Imo they can make development faster and more efficent but they make the code very unreadable, especially if someone else has to read it, Therefore I try to use them only when it's appropriate. My dev friends use them too much and it makes reading their code a hellish experience, especially in Javascript with Rx.

!rant

Do you think it is worth learning functional programming and specifically haskell. It seems like a really good concept, but a lot of people claim that it's not applicable in real scenarios.

What do you think of Elixir + Phoenix to build API’s? Is it a better choice than a more established language like Python or something more new like Scala or Clojure?

At my company we're going through a watershed moment where we're starting to discuss and think about re-building our digital foundations and nothing is off limits. I'm leading the discussion about our architecture where everyone can have their say into what the future looks like for our applications. We're currently on a Drupal (CMS)  + PHP7/Symfony (Backend Content Repository) + Symfony Twig templates (Frontend)

Even though I have been developing in PHP most of my career, I personally love Elixir and spend a lot of my time away from work learning it but many of my reasons feels subjective like pattern matching, it's actor concurrency model, immutable data and not having to deal with classes/objects, and I'm not entirely sure how that translates to business value, advocating successfully for a tech stack change requires solid reasoning and good answers to challenges like how do we find Elixir developers when existing devs leave, how easy is it to build a CI/CD pipeline for Elixir/Phoenix, etc.

Tired of imperative different-yet-all-the-same programing languages. What's the most awesome funcional language ever?

Bonus: sweet projects you've done in that language

Programming Paradigm Convergence.

I can already see it in JS and C#. Both have functional/OO aspects and keep growing more similar in terms of language features.

I'd rather see OOP die a fast and horrible death though 🤷‍♂️

Lambda expressions in Java 8, because I love functional programming.

Functional programming course starts today. I'm really looking forward to it, but it is so early compared to my other courses

Being pretty much the only one who has some knowledge of how to code and get my way around tech (even if minimal, I'm too lazy for my own good) in my familiar household - and by extension, my family (Family extends FamiliarHousehold - LoL I'm sorry) - (my brother is on his first grade of a programming course in high school, I'm a 2nd grade uni student aiming to become a game dev) sometimes I wish I knew nothing of it.

Don't get me wrong, I do like working on code (if in Java. C is making me wanna tear my eyes out) but sometimes ignorant family members push me through the edge.

I worked on a business thing my family started this summer and one of the "jobs" was managing everything via a website.
Fair enough, I knew nothing of it when I started but I learn fast and just like that I knew my way around it. The problem came when I had to teach the person who started the project how it worked. This doesn't sound all that bad except he is kinda in the stone age regarding informatics.
He got a computer a few years ago and he pretty much only played poker in it, and he still had one of those old nokias you could throw to a wall and get a hole into it. The computer is like 9y and runs like crap.
To make things worse he bought a new phone, a smartphone, and pestered me to teach him. I swear trying to teach him is like repeating the same thing 1000x and pray he keeps it in his head. Spoiler: he doesn't. ( sanity--; )
So to try and easy my suffering I decided to make a manual for the website (which is outdated by now because the team behind the website did a 180 and some things looks different), but it acted as if I'd done nothing. ( sanity--; )
To top this off he keeps on saying I don't wanna help him. ( sanity--; )
This kept going for the whole damn summer, and meanwhile I had to go back to uni and in the first days I still got like 4-5 calls/day, half of those might about the smallest things because he's so panicky.
Like (both examples happened while I was still there but it kinda goes along those lines sometimes):
- (During the period they changed the website the first time since we're there; they were mostly doing changes back and forth and testing because it had a new layout for a day or 2 before going back; also the site was totally functional, except for a thing or 2)
Him: "They're changing the website, why are they doing that?"
Me: "Because it's their website and they can?"
Him: "WHY DIDN'T THEY LET US KNOW"
Me: "They don't have to, they don't work for you." ( sanity--; )
Or (during the same period; the pages have a menu on the left; one of the submenus has a counter that resets every time the session ends; during that maintenance time they must've "disabled" the function because the number kept growing even after the session ended):
Him: "WHY IS THE NUMBER GROWING?"
Me: "They're working on the code, relax, it's nothing."
Him: "But why." ( sanity--; )

The only quesion he pretty much hasn't asked me yet is why "Is the website's colour this one and not that one?".

when you used to functional programming, every time you see a for loop, you can not resiste but to refactorit.

Arghhh! Reactive programming took away all the fun, but oh well, we can be more lazy now. Functional programming just made a big come back this year.

to be honest, i hate every OOP, in my opinion it's just add complexity in every way. yet i would like to use Functional Programming but it's fukking hard to learn and hard to get use to. Tryna get used to Haskell.