"Personalized Advertisements":

No Amazon, I'm not interested in buying any of these phones, I just bought a new one five days ago, remember? You sold it to me! And stop recommending the same book I already got five YEARS ago!

YouTube, why are you always showing me the same ad about an app I already own and use regularly? And why the FUCK do I you show me the new trailer of Star Wars Ep8 as an ad video before the actual video of the new Star Wars Ep8 trailer?

Audi, I am an university student, barely able to pay my rent, why are you telling me to buy your newest car? How do you expect me to afford this?

Monster, why exactly are you showing me job offers as "Technical Product Designer at company X" for which I'm not remotely qualified or even interested in?

Neither do I have 5000£ (I live in Germany, at least match the currency, ffs) to invest in some suspiciously promising stock market schemes, nor am I in any need of rheumatism pills or a hearing aid (I am 19). I cannot afford or want any Rolex watches and PLEASE, I don't know why you think I would, but I really do not need a special new and innovative brand of tampons, my dick is doing fine, thanks.

"Hot local singles near {my actual location} want to fuck!
Click here!!!"
At least there are still some ads you can trust to be relevant...

Hey guys. I'm very proud to present my first book. Artificial Intelligence. A book that speak about convolutional neural network from the scratch and how artificial Intelligence improve our life. It's not a technical volume only but a place to know what there is inside. Now is time to correct it...

I just lost faith in the entire management team of the company I'm working for.

Context: A mid sized company with
- a software engineering departmant consisting of several teams working on a variety of products and projects.
- a project management department with a bunch of project managers that mostly don't know shit about software development or technical details of the products created by engineering.

Project management is unhappy about the fact that software engineering practically never sticks to the plan regarding cost, time and function that was made at the very beginning of the project. Oh really? Since when does waterfall project management work well? As such they worked out a great idea how to improve the situation: They're going to implement *Shopfloor Management*!

Ever heared about Shopfloor Management? Probably not, because it is meant for improving repetitive workflows like assembly line work. In a nutshell it works by collecting key figures, detecting deviation in these numbers and performing targeted optimization of identified problem areas. Of course, there is more to Shopfloor Management, but that refers largely to the way the process just described is to be carried out (using visualisation boards, treating the employee well, let them solve the actual problem instead of management, and so on...). In any case, this process is not useful for highly complex and hard-to-predict workflows like software development.

That's like trying to improve a book author's output by measuring lines of text per day and fixing deviations in observed numbers with a wrench.

Why the hell don't they simply implement something proven like Scrum? Probably because they're affraid of losing control, affraid of self managed employees, affraid of the day everybody realizes that certain management layers are useless overhead that don't help in generating value but only bloat.

Fun times ahead!

Tl;Dr - It started as an escape, carried on as fun, then as a way to be lazy, and finally as a way of life. Coding has defined and shaped my entire life from the age of nine.

When I was nine I was playing a game on my ZX spectrum and accidentally knocked the keyboard as I reached over to adjust my TV. Incredibly parts of it actually made a little sense to me and got my curiosity. I spent hours reading through that code, afraid to turn the Spectrum off in case I couldn't get back to it. Weeks later I got hold of a book of example code to copy out to do various things like making patterns on the screen. I was amazed by it. You told it what to do, and it did it! (don't you miss the days when coding worked like that?) I was bitten by the coding bug (excuse the pun) and I'd got it bad! I spent many late nights on that thing, escaping from a difficult home life. People (especially adults) were confusing, and in my experience unpredictable. When you did things wrong they shouted at you and threatened to take you away, or ignored you completely. Code never did that. If you did something wrong, it quietly let you know and often told you exactly what was wrong. It wasn't because of shifting expectations or a change of mood or anything like that. It was just clean logic, simple cause and effect.

I get my first computer a year later: an IBM XT that had been discarded by a company and was fitted with a key on the side to turn it on. With the impressive noise it made it really was like starting an engine. Whole most kids would have played with the games, I spent my time playing with batch scripts and writing very simple text adventures. And discovering what "format c:" does. With some abuse and threatened violence I managed to get windows running on it. Windows 2.1 I think it was.

At 12 I got a Gateway 75 running Windows 95. Over the next few years I do covered many amazing games: ROTT, Doom, Hexen, and so on. Aside from the games themselves, I was fascinated by the way computers could be linked together to play together (this was still early days for the Web and computers networked in a home was very unusual). I also got into making levels for Doom, Heretic, and years later Duke Nukem 3D (pretty sure it was heretic; all I remember is the nightmare of trying to write levels entirely by code!). I enjoyed re-scripting some of the weapons and monsters to behave differently. About this time I also got into HTML (I still call this coding, but not programming), C, and java. I had trouble with C as none of the examples and tutorial code seemed to run properly under a Windows environment. Similar for my very short stint with assembly. At some point I got a TI-83 programmable calculator and started rewriting my old batch script games on it, including one "Gangster Lord" game that had the same mechanics as a lot of the Facebook games that appeared later (do things, earn money, spend money to buy stuff to do more things). Worried about upcoming exams, I also made a number of maths helper apps, including a quadratic equation solver that gave the steps, and a fake calculator reset to smuggle them into my exams. When the day came I panicked and did a proper reset for fear of being caught.

At 18 I was convinced I was going to be a professional coder as I started a degree in Computer Science. Three months later I dropped out after a bunch of lectures teaching what input and output devices were and realising we were only going to be taught Java and no C++. I started a job on the call centre of a big company, but was frustrated with many of the boring and repetitive tasks we had to do. So I put my previous knowledge to use, and quickly learned VBA to automate tasks. It wasn't long before I ended up promoted to Business Analyst where I worked on a great team building small systems in Office, SAS, and a few other tools.

I decided to retrain in psychology, so left the job I was in and started another degree. During my work and placements my skills came in use a number of times to simplify and automate tasks. I finished my degree, then took a job as a teaching assistant while I worked out what I wanted to do next and how to pay for it. Three years later I've ended up IT technican at the school, responsible for the website, teaching a number of Computing lessons each week, and unofficial co-coordinator for Computing as a subject. I also run a team of ten year old Digital Leaders who I am training in online safety and as technical experts; I am hoping to inspire them to a future in coding. In September I'll be starting teacher training with a view to becoming a Computing specialist teacher. Oh, and I'm currently doing a course in Android Development in my free time.

And this all started with an accidental knock on the keyboard of a ZX Spectrum.

JIT Learning. Just in time Learning. You Don't need read a book from cover to cover. YAGNI. Many technical books talk about topics that you might never need in your career. Focus on what you need to know after making a plan for what you want to achieve.

YAGNI applies to coding as well. Don't create a class or a method just because you Might need it later. Create them only when necessary. This keeps your code cleaner and there is less to test.

I AM TIRED

warning: this rant is going to be full of negativity , CAPS, and cursing.

People always think and they always write that programming is an analytical profession. IF YOU CANNOT THINK IN AN ANALYTICAL WAY THIS JOB IS NOT FOR YOU! But the reality could not be farther from the truth.

A LOT of people in this field whether they're technical people or otherwise, just lack any kind of reasoning or "ANALYTICAL" thinking skills. If anything, a lot of of them are delusional and/or they just care about looking COOL. "Because programming is like getting paid to solve puzzles" *insert stupid retarded laugh here*.

A lot of devs out there just read a book or two and read a Medium article by another wannabe, now think they're hot shit. They know what they're doing. They're the gods of "clean" and "modular" design and all companies should be in AWE of their skills paralleled only by those of deities!

Everyone out there and their Neanderthal ancestor from start-up founders to developers think they're the next Google/Amazon/Facebook/*insert fancy shitty tech company*.

Founder? THEY WANT TO MOVE FAST AND GET TO MARKET FAST WITH STUPID DEADLINES! even if it's not necessary. Why? BECAUSE YOU INFERIOR DEVELOPER HAVE NOT READ THE STUPID HOT PILE OF GARBAGE I READ ONLINE BY THE POEPLE I BLINDLY COPY! "IF YOU'RE NOT EMBARRASSED BY THE FIRST VERSION OF YOU APP, YOU DID SOMETHING WRONG" - someone at Amazon.

Well you delusional brainless piece of stupidity, YOU ARE NOT AMAZON. THE FIRST VERSION THAT THIS AMAZON FOUNDER IS EMBARRASSED ABOUT IS WHAT YOU JERK OFF TO AT NIGHT! IT IS WHAT YOU DREAM ABOUT HAVING!

And oh let's not forget the tech stacks that make absolutely no fucking sense and are just a pile of glue and abstraction levels on top of abstraction levels that are being used everywhere. Why? BECAUSE GOOGLE DOES IT THAT WAY DUH!! And when Google (or any other fancy shit company) changes it, the old shitty tech stack that by some miracle you got to work and everyone is writing in, is now all of a sudden OBSOLETE! IT IS OLD. NO ONE IS WRITING SHIT IN THAT ANYMORE!

And oh my god do I get a PTSD every time I hear a stupid fucker saying shit like "clean architecture" "clean shit" "best practice". Because I have yet to see someone whose sentences HAVE TO HAVE one of these words in them, that actually writes anything decent. They say this shit because of some garbage article they read online and in reality when you look at their code it is hot heap of horseshit after eating something rancid. NOTHING IS CLEAN ABOUT IT. NOTHING IS DONE RIGHT. AND OH GOD IF THAT PERSON WAS YOUR TECH MANAGER AND YOU HAVE TO LISTEN TO THEM RUNNING THEIR SHITHOLE ABOUT HOW YOUR SIMPLE CODE IS "NOT CLEAN". And when you think that there might be a valid reason to why they're doing things that way, you get an answer of someone in an interview who's been asked about something they don't know, but they're trying to BS their way to sounding smart and knowledgable. 0 logic 0 reason 0 brain.

Let me give you a couple of examples from my unfortunate encounters in the land of the delusional.

I was working at this start up which is fairly successful and there was this guy responsible for developing the front-end of their website using ReactJS and they're using Redux (WHOSE SOLE PURPOSE IS TO ELIMINATE PASSING ATTRIBUTES FOR THE PURPOSE OF PASSING THEM DOWN THE COMPONENT HIERARCHY AGIAN). This guy kept ranting about their quality and their shit every single time we had a conversation about the code while I was getting to know everything. Also keep in mind he was the one who decided to use Redux. Low and behold there was this component which has THIRTY MOTHERFUCKING SEVEN PROPERTIES WHOSE SOLE PURPOSE IS BE PASSED DOWN AGAIN LIKE 3 TO 4 TIMES!.

This stupid shit kept telling me to write code in a "functional" style. AND ALL HE KNOWS ABOUT FUNCTIONAL PROGRAMMING IS USING MAP, FILTER, REDUCE! And says shit like "WE DONT NEED UNIT TESTS BECAUSE FUNCTIONAL PROGRAMMING HAS NO ERRORS!" Later on I found that he read a book about functional programming in JS and now he fucking thinks he knows what functional programming is! Oh I forgot to mention that the body of his "maps" is like 70 fucking lines of code!

Another fin-tech company I worked at had a quote from Machiavelli's The Prince on EACH FUCKING DESK:

"There is nothing more difficult to take in hand, more perilous to conduct, or more uncertain in its success, than to take the lead in the introduction of a new order of things."

MOTHERFUCKER! NEW ORDER OF THINGS? THERE 10 OTHER COMPANIES DOING THE SAME SHIT ALREADY!

And the one that got on my nerves as a space lover. Is a quote from Kennedy's speech about going to the moon in the 60s "We choose to go to the moon and do the hard things ..."

YOU FUCKING DELUSIONAL CUNT! YOU THINK BUILDING YOUR SHITTY COPY PASTED START UP IS COMPARABLE TO GOING TO THE MOON IN THE 60S?

I am just tired of all those fuckers.

Asus have now decided that a removable battery is a feature people do not need anymore on a powerful laptop.

My battery or charger had a fit and blew the fuse on my charger and broke the battery, and now I have to send my laptop back because they can't send me a new battery, as replacing it myself would void the warranty.

Please for the love of all that isn't completely retarded, nobody start taking more pages out of Apple's book, even some completely non-technical people could handle changing a battery before, this benefits no one.

To make things worse, I'm on holiday right now and leaving the country for a year a few weeks after I get back, so if they can't get it back to me fast enough, I won't have the laptop for the whole bloody reason I bought it for, just because some smart arse designer has clearly never owned a laptop in their life.

Fml... you keep getting the weekly discussions right on point.

I started with the last guys right out of university... just out of Hospital.

With a brand new degree and a Crohn’s diagnosis I stepped into the first place I found hiring. They were good guys, after a junior dev... to get stuck in their muck.

I did! I nailed project after project, tricky development after tricky development. I spent 5 years with them and over those years things changed.

They had a mass cull... the original idea was to get rid of the useless middle managers, the ones managing other managers being managed by another manager for no real reason.... the ones that do fuck all with their day.

But the fucking idiots upstairs put the job of working out the cull in the shitty middle managers hands.

So, instead, they cut the titles senior, junior and everything in between. Everyone was just a thing, no senior things, no junior things. Just things.

Once they’d done that they said “we’ll we have this many things, they’re all the same, let’s get rid of the things with the highest pay checks because the other things can do it just as well for less money”...

And that’s how they cut 50% of their senior techs.

I was one of the ones left behind but the damage became obvious quick. The middle managers barked out orders at people who couldn’t complete them, and everything went to shit.

My team was rebranded twice in as many years... an obvious ploy for funding, but the cost of the team fluctuated like hell because contractors had to fill the senior positions at 3 times the cost.

Then the managers started barking out Self contradictory orders. Do this, but this way...

This would work, but not that way... try explaining that to a group of non-technical, useless as fuck middle managers. It took months, and shit flows downstream so we got the bulk of the hassle for it.

Then my boy Morpheus, got a warning... they threatened his contract for saying “this will work, but not that way”.

He kept the contract, and the manager giving him the warning said he didn’t think he should... but he, and all the middle fuckwits don’t have the balls to stand up against nonsense.

That was the breaking point for me, I handed in my notice and told them a month was what they could have.

I didn’t have a position or an idea of where to go, a few long-standing offers as back up in a pinch but not the perfect job.

On the Thursday I decided I was done, I let my manager know. Then I boshed the fuck out of my CV and updated my profiles.

My phone started ringing off the hook, a senior NG2/MEAN/Ionic dev on the market is like candy to recruiters. They’re lovely too.

I went to a few interviews that were okay but not great. Then a company got in touch... one that I immediately recognised as an IT book publisher. They said they were looking for NG/NG2 devs, senior. winner! Set up the interview.

So I’d spent the weekend with the missus, about an hour away from mine and 2 from the interview. I hadn’t planned on staying there but at 6ish she looked over at me and said “do you have to go” <- imagine that with puppy dog eyes from a gorgeous Slovenian lass.

I folded quicker than a shitty pancake toss.

We spent the night together but that meant I had to be up at 6, to go back to mine, iron my interview clothes and make it to the train to manage the interview. Fuck. I did it, but I was at the interview wired on caffeine and struggling to be awake and coherent. I still managed, that’s what I do, I make do and try to do well regardless of the situation.

That comes from being ill btw, when you’re dealt a shitty hand you learn to play it well.

They were good guys, the heads all knew what they were on about, not the middle management bs I was used to.

They demoed me live with an ng1 test, which was awesome as hell to play with.

We chatted, friendly and cool guys! I loved the place.

The end of the week they got me in for second round. Ng2 and competence test, again I went for it!

Positive feedback and a “we’ll get back to you ASAP, should be by Tuesday”...

Tuesday was the Tuesday before the Friday I was due to leave the old company... I was cutting it close.

On the Monday the offers started rolling in, a few C# ASP MVC positions, cool but I was holding out for the guys I’d interviewed with.

Then Tuesday comes around, I’m nervous as fuck but it’s okay because I knew regardless I can pay the rent in December with one of the offers.

Then said yes!

The thing that seemed most important in the process was my ability to talk to any fucker. If you’re coming up to interview, talk to everyone, the grocer, your barista, the binmen, anyone. Practice that skill above all others.

I start tomorrow morning! I can’t wait.

Final thought: middle managers are taints.

I propose that the study of Rust and therefore the application of said programming language and all of the technology that compromises it should be made because the language is actually really fucking good. Reading and studying how it manages to manipulate and otherwise use memory without a garbage collector is something to be admired, illuminating in its own accord.

BUT going for it because it is a "beTter C++" should not constitute a basis for it's study.

Let me expand through anecdotal evidence, which is really not to be taken seriously, but at the same time what I am using for my reasoning behind this, please feel free to correct me if I am wrong, for I am a software engineer yes, I do have academic training through a B.S in Computer Science yes, BUT my professional life has been solely dedicated to web development, which admittedly I do not go on about technical details of it with you all because: I am not allowed to(1) and (2)it is better for me to bitch and shit over other petty development related details.

Anecdotal and otherwise non statistically supported evidence: I have seen many motherfuckers doing shit in both C and C++ that ADMIT not covering their mistakes through the use of a debugger. Mostly because (A) using a debugger and proper IDE is for pendejos and debugging is for putos GDB is too hard and the VS IDE is waaaaaa "I onlLy NeeD Vim" and (B) "If an error would have registered then it would not have compiled no?", thus giving me the idea that the most common occurrences of issues through the use of the C father/son languages come from user error, non formal training in the language and a nice cusp of "fuck it it runs" while leaving all sorts of issues that come from manipulating the realm of the Gods "memory".
EVERY manual, book, coming all the way back to the K&C book talks about memory and the way in which developers of these 2 languages are able to manipulate and work on it. EVERY new standard of the ISO implementation of these languages deals, through community effort or standard documentation about the new items excised through features concerning MODERN (meaning, no, the shit you learned 20 years ago won't fucking cut it) will not cut it.

THUS if your ass is not constantly checking what the scalpel of electrical/circuitry/computational representation of algorithms CONDONES in what you are doing then YOU are the fucking problem.

Rust is thus no different from the original ideas of the developers behind Go when stating that their developers are not efficient enough to deal with X language, Rust protects you, because it knows that you are a fucking moron, so the compiler, advanced, and well made as it is, will give you warnings of your own idiotic tendencies, which would not have been required have you not been.....well....a fucking idiot.

Rust is a good language, but I feel one that came out from the necessity of people writing system level software as a bunch of fucking morons.
This speaks a lot more of our academic endeavors and current documentation than anything else. But to me DEALING with the idea of adapting Rust as a better C++ should come from a different point of view.

Do I agree with Linus's point of view of C++? fuck no, I do not, he is a kernel engineer, a damn good one at that regardless of what Dr. Tanenbaum believes(ed) but not everyone writes kernels, and sometimes that everyone requires OOP and additions to the language that they use. Else I would be a fucking moron for dabbling in the dictionary of languages that I use professionally.
BUT in terms of C++ being unsafe and unsecured and a horrible alternative to Rust I personaly do not believe so. I see it as a powerful white canvas, in which you are able to paint software to the best of your ability WHICH then requires thorough scrutiny from the entire team. NOT a quick replacement for something that protects your from your own stupidity BY impending the use of what are otherwise unknown "safe" features.

To be clear: I am not diminishing Rust as the powerhouse of a language that it is, myself I am quite invested in the language. But instead do not feel the reason/need before articles claiming it as the C++ killer.

I am currently heavily invested in C++ since I am trying a lot of different things for a lot of projects, and have been able to discern multiple pain points and unsafe features. Mainly the reason for this is documentation (your mother knows C++) and tooling, ide support, debugging operations, plethora of resources come from it and I have been able to push out to my secret project a lot of good dealings. WHICH I will eventually replicate with Rust to see the main differences.

Online articles stating that one will delimit or otherwise kill the other is well....wrong to me. And not the proper approach.

Anyways, I like big tits and small waists.

Went to a thrift store last week near work and they often have old dev or technology books (I picked up a first edition K&R C book, once) and I found:

1) A book on the history of codes and ciphers throughout history.
2) Beyond good and evil by Nietzsche.
3) A modern publication of a 1673 Spanish demon summoning book (to go into a local town archive).
4) The technical information and construction manual for telegram systems from 1938.

I swear I was driving home thinking:

"Please don't crash, if CSI teams have to piece my identity together from these four personal items I dread to think what conclusions they're going to come to..."

It’s throw back Thursday folks...

Today’s post sets us back to a time long before the internet. Before C ... from the days of FORTRAN.. COBOL .. and LISP... How was info not taught in classes and published in large books shared???? Well it’s was journals like these, sent out monthly and quarterly for some. They would publish their findings to these type “magazines” but extremely technical.

This is one of the oldest editions have. Trying to collect them.

I believe in Knuths TAOCP, he references the first article of this edition... I’ve seen that article referenced in one of my books but i forgot which book.. pretty sure TAOCP.. anyway..

Just a fun throw back. Btw... just because it’s from 59’ doesn’t mean the information is irrelevant.. the information is facts the equations are true.

So the Computer Science departent at my university has a shelf where people can give away technical books they don't need anymore. I found a giant UNIX system administration book from 1995 there the other day, and i am blown away by how many useful things i could find in such an old book; basically all of the unix flavours mentioned are long dead (with the exception of bsd and linux ofc), and so is 99% of the software, but all of the core concepts and basic tasks still hold true in 2018... Isn't that amazing? :D Where else can you find a system that still works the same after 23 years?

I finally finished reading the goddamn book. 🥵

I started to get interested in programming at the age of 13. I was started spending a lot time in our school library and read mostly technical books (beginner/hobbyist stuff) about electronics.
Some book was about Quick Basic (hence my username).
On Windoze 95 in a DOS mode IDE I started trying stuff out and soon I had my first tiny console game.
A bit later I started with HTML and CSS stuff, made a website about ongoing jokes in our class and some rants, later I got into VB6 (I hate VB nowadays!) and wrote for a personal school project a learning software (relatively simple one) to learn vocabulary for foreign languages.

At about 15 I started with C++ and later C# .NET, which I liked the most, and started on some new Windows.Forms stuff, created some small websites.

Now I'm working parttime as a professional developer (mostly web, but VR & .NET too) and studying EE at a university.

My parents had no experience with computers at all, so I learned everything myself an with the help of the allmighty internet (the black box with the red dot on top).

That's my story. ;)

Insert your rant about this below this line:
-----------------------------------------

I know I’ll get mixed views for this one...

So I’ll state my claim. I agree with the philosophy of uncle bob, I also feel like he is the high level language - older version of myself personality wise.. (when I learned about uncle bob I was like this guy is just like me but not low level haha).

Anyway.. I don’t agree with everything because I think he thinks or atleast I get the vibe he thinks everything can be solved by OOP, and high level languages. This is probably where Bob and I disagree. Personally I don’t touch ruby, python and java and “those” with a 10 foot pole.

Does he make valid arguments, yes, is agile the solve all solution no.. but agile ideas do come natural and respond faster the feedback loop of product development is much smaller and the managers and clients and customers can “see things” sooner than purly waterfall.. I mean agile is the natural approach of disciplined engineers....waterfall is and was developed because the market was flooded with undisciplined engineers and continues to flood, agile is great for them but only if they are skilled in what they are doing and see the bigger picture of the forest thru the trees.. which is the entire point of waterfall, to see the forest.. the end goal... now I’m not saying agile you only see a branch of a single tree of the forest.. but too often young engineers, and beginners jump on agile because it’s “trendy” or “everyone’s doing it” or whatever the fuck reason. The point is they do it but only focus on the immediate use case, needs and deliverables due next week.

What’s wrong with that?? Well an undisciplined engineer doing agile (no I’m not talking damn scrum shit and all that marketing bullshit).. pure true agile.
They will write code for the need due next week, but they won’t realize that hmm I will have the need 3 months from now for some feature that needs to connect to this, so I better design this code with that future feature in mind...

The disciplined engineer would do that. That is why waterfall exists so ideally the big picture is painted before hand.

The undisciplined engineer will then be frustrated in the future when he has to act like the cool aid man thru the hard pre mature architectural boundaries he created and now needs links or connections that are now needed.

Does moving to agile fix that hell no.. because the undisciplined engineer is still undisciplined.

One could argue the project manager or scrum secretary... (yes scrum secretary I said that right).. is suppose to organize and create and order the features with the future in mind etc...

Bullshit ..soo basically your saying the scrum kid is suppose to be the disciplined engineer to have foresight into realizing future features and making requirements and task now that cover those things? No!
1 scrum bitch focuses too much on pleasing “stake holders” especially taken literally in start ups where the non technical idiots are too involved with the engineering team and the scrum bastard tries to ass kiss and get everything organized and tasks working so the non technical person can see pretty things work.

Scrum master is a gate keeper and is not needed and actually hinders the whole process of making a undisciplined engineer into a disciplined engineer, makes the undisciplined engineer into a “forever” code grunt... filling weekly orders of story points unable to see the forest until it’s over because the forest isn’t show to the grunt only the scrum keeper knows the big picture..... this is bad this is why waterfall is needed.

Waterfall has its own problems, But that’s another story for another day..

ANYWAY... soooo where were we ....

Ahh yess....

Clean code..

Is it a good book, yes.. does uncle bobs personality show thru the book .. yes lol.
If you know uncle bob you will understand what I just did with this post lol. I had to tangent ( at least mine was related to the topic) ...

I agree with the principles of the book, I don’t agree with the extreme view point. It’s like religion there’s the modest folks and then there are the extremists. Well he’s the preacher of the cult and he’s on the extreme side.. but that doesn’t mean he’s wrong.. many things he nails... he just hits the nail thru the wall just a bit.

OOP languages are not the solution... high level languages do not solve everything.. pininciples and concepts can be used across the board and prove valuable.. just don’t hold everything up like the 10 commandments of which you cannot deviate from.. that’s the difference here I think..

Good book, just don’t take it as the Bible as a beginner, actually infact DONT read this book as a beginner. Wait a bit learn then reflect by reading this.

Now that my math posts have failed to garner the anger they formerly did, we here at Wisecrack Studios, like all teams of people completely out of ideas, have come up with a brilliant never-before-tried concept to bring fresh shitposts to your pocket-telescreen this fine year of 2020.

We present to you the DevRant shitposter census!

Yes we pride ourselves in our quality bait and bullshit here at WS. Founded in [previous year a long long time ago], we focus on craftmanship, tradition, and doing it right. Our bait is loved the world over for "it's fresh flavor", "so good, it's like you're abusing heroin right along with the company employees!'

And now, you too get to participate and choose your very own bullshit!
You could say we may have invented a totally new word just to describe it: crowdsourcing!
Isn't it just *brilliant*.

Here is Wisecrack's "Private Select" census, of only the most choice *premium* finely-aged shitpost ideas for this [current year].

Please, please, one vote per customer!

* Moar javascript shitposts (no we won't be doing any more, even WE are tired of js rants).

* Overly pixelated memes (obviously not) blatantly ripped and automatically uploaded via shitty selenium scripts

* Real life hijinxs, trolling shitty companies hiring processes for fun at their expense!

* DevRantCon now with 100% more orgies. Reserve your kickstarter ticket today.

* Disappointing vaporware announcements that take ten minutes to read and build your excitement up only to crush it before your very eyes like a child's first lego build in the hands of an angry nd merciless andre the giant disappointed by the craftmanship of a five year old.

* A livestream of a monkey on an actual typewriter, with a btc betting pool each time an actual word is typed, along with a $5 "shock the monkey" button to spice things up a bit
(our lawyers are informing us this may or may not be illegal in some or all nations. We'll get back to you when sealand responds with our request about their laws on unnecessary animal cruelty. )

* Video conference with devrants creators where we all play "I've never" that doesn't end until at least one person passes out black drunk.

* Weekly comedy write ups with jokes (not obviously) blatantly stolen from cards against humanity

* HipsterRants: why your favorite [thing - game, music, movie, book] sucks, and why I hate you for liking it.

* Did we mention javascript rants?

* Cool new projects by devranters and our merciless breakdown of why each one is pure, unadulterated shit, everything that was done wrong, and why you should personally be ashamed for using it.

* SadRants: cancer, meth abuse, homelessness, how we'll all die at the end, and how the sun will one day turn into a giant ball of fire that will consume the earth and leave no trace that anyone ever existed, and nothing we do will ultimately matter.

* HappyRants: ( ͡° ͜ʖ ͡°) oh yeah, you feeling it now mr krabs?

* Technical breakdowns that are completely wrong, utterly incompetent, intentionally misleading, and wildly upvoted by people who are unfamiliar.

Vote for your favorite topic/idea today! or even submit your own for our 'consideration'!

Clickbait, now in technicolor!

"The Phoenix project" alternative ending:

Bill Palmer manages to avert disaster with heroic efforts, working 18 hours per day for weeks.
His wife files for divorce. He starts to sleep at office, next to the servers room.
At the last moment a huge hacker attack almost destroys everything, but he finally manages to announce that Phoenix is ready on time, security auditing passed and any kind of great improvements.

Steve, the CEO, calls him and says: "are you crazy? we put you on an impossible project with short notice to make you fail! All our investors have been secretly short selling our stocks, so now they are waiting a big failure to cash in. We also paid korean hackers to bring you on your knees. But you are really stubborn! "

All Phoenix Project is rolled back, huge shit happens, stocks fall, investors ripe great benefits. All IT is outsourced to an external company (owned by members of the board)

Bill is fired. His reputation tainted by the failure, he can't find job anymore. his technical skills and knowledge are out of date.
As he didn't have time to take care of divorce he has lost also all his personal wealth.

He writes a book about his experience, well, actually a rant, but the company sues him forcing him to pay more money.

In the final scene, police arrests him, drunk while trying to burn a server farm with matches.

The world of SSO (Single sign on) it's a real shit.

At start I tought its a pretty common feature that lots of people want, so there should be a lot of open source options for making a server and client libraries.

So far I've only found to libraries, written in java with a fucking big book instead of a simple documentation with billions of options and features but without a fucking guide to get it running and connect with a database.

It's that hard to write an easy manual with the steps to get it running instead a giant book with million's of technical terms and architectural details?

Found this book amongst other 7 grade school books...
Fuck, kids are learning the basis for every technical job this days, in my time even chemistry was only theory... Let alone practical lessons

I’m struggling in studying and that’s seriously holding me back, regardless of the type of technical book I’m reading I’m always in a fight with my brain. Even if I enjoy the topic and then I’ll enjoy using what I read while I study I struggle to learn more than 1-2 chapters (sometimes even less) at time then my head starts to hurt, my focus drifts away and if I force myself to go ahead my brain just refuses to store the new informations, it feels like filling a full tank.

At this point I should have learned C++ and Swift and started to contribute to projects which aren’t overdone web apps but all I have are two half read books which silently “judges” me anytime I open my eBook library and I dread returning to having associated them to headache and frustration and the only things I read this year are design patterns (which haven’t found a single real life use since then) and F# (which I never used with the exception of some little demos and is now slowly fading away in my memory).

Have you got any study advice to help me dealing with this frustrating situation?

What's your favourite technical book? Mine's this.

On average it takes me 2 months to read a technical book, I'm not sure it's a pace I should be proud of...

Here’s Today’s book, a little late in the day but we had a storm here and lost power. Powers back

Anyway Programming Pearls, this books isn’t so much a tutorial book, or like “how to program book” it’s more an influential book and thought book. Similar to the mythical man month book.

It’s short book little over 200 pages, of short essays on problems that have irritated programmers over the years. Hence the amage to pearls as a pearl is developed from grains of sand that irritate oysters. This book is a collection of irritants of programmers. (No not the social or business side of things) but technical problems we all face.
These articles are compiled from the original postings that occurred in the Communications of ACM journal, back in the late 90s.

This books offers workable solutions to these “pearls”.

Think of this like one of the precursors to what we have now as stack overflow .. information was shared via journals since the internet wasn’t available but not so much question then respond like we do more of hey I had this problem here’s the solution sort of system.

It’s the type of book, when your bored and you don’t want to read some “how to book” you read this, just like mythical man month and others.

This book references items from knuths books. As well as references to others.

So here’s to the pearls the plague us all.

Probably the best technical book ever I saw. 😂 😂 😂

Amazon prime days sale...
I find a Fire 7 for $30 instead of $50. I think that would be great to put books on. I am thinking Kindle is an Android type device. Even some searches for Android tablets bring up Kindles on Amazon and web.

I get my kindle and like it. I signed up for trial of Kindle Unlimited. There is almost no selection for Kindle Unlimited for technical books. So I think I can just put the Paktpub app on the Kindle. No app for Kindle. That is okay, I can just put the Play store on there. Technically you can, if you side load it, but it will stop functioning after a day. Not an officially licensed Android device so cannot use Google services.

At this point I am not happy with the Kindle. I got it to read technical books and the selection of technical books is poor. At least on Kindle Unlimited. So I start looking at tablets on Amazon.

I find that there is a serious price breakpoint on Android tablets (cannot get Paktpub app for Windows tablets). For $100 (US) they are not very good. At > $150 they start getting really good feature wise. I end up buying a Samsung tablet for $200. It has 2GB ram and 8 cores at 1.6GHz.

I have been using the tablet for a few days now and am happy with what I can do with it. Now I have to wonder if Kindle is actually an upsell product rather than a serious product. I might not have went for a $200 tablet unless I had not had issues with the Kindle. Not sure there. Amazon made out for both product sales as I just gave the Kindle to the kids.

In the end I am very happy. Paktpub has all the tech books I can handle at the moment. Will probably not consider Kindle Unlimited again. This tells me that competition is good in the book sector. Good for the end user.

Please if you write a math book, don’t write it in a technical, boring, orthodox textbook. Write it like u want to share it with someone you love as a grandiose story of personal adventure. Write it as an exciting narrative. This is what the OGs did.

Having a lot of bad experiences while working as intern in startups and about to join a MNC, i wanted to share my work life balance and technical demands that i expect from a company. These are going to be my list of checkpoints that i look forward , let me know which of them are way too unrealistic. also add some of yours if i missed anything :

Work life balance demands ( As a fresher, i am just looking forward for 1a, 2a and 8, but as my experience and expertise grows, i am looking forward for all 10. Would i be right to expect them? ):

1a 8 hr/day. 1b 9h/day
2a 5days/week. 2b 6 days/week
3 work from home (if am not working on something that requires my office presence)
4 get out of office whenever i feel like i am done for the day
5 near to home/ office cab service
6 office food/gym service
7 mac book for working
8 2-4 paid leaves/month
9 paid overtime/work on a holiday
10.. visa sponsorship if outside india

Tech Demands (most of them would be gone when i am ready to loose my "fresher " tag, but during my time in internship, training i always wished if things happened this way):

1. I want to work as a fresher first, and fresher means a guy who will be doing more non tech works at first than going straight for code. For eg, if someone hires me in the app dev team, my first week task should be documenting the whole app code / piece of it and making the test cases, so that i can understand the environment/ the knowledge needed to work on it

2. Again before coding the real meaningful stuff for the main product, i feel i should be made to prepare for the libraries ,frameworks,etc used in the product. For eg if i don't know how a particular library ( say data binding) used in the app, i should be asked to make a mini project in 1-2 days using all the important aspects of data binding used in the project, to learn about it. The number of mini tasks and time to complete them should be given adequately , as it is only going to benefit the company once am proficient in that tech

3. Be specific in your tasks for the fresher. You don't want a half knowledgeable fresher/intern think on its own diverging from your main vision and coding it wrong. And the fresher is definitely not wrong for doing so , if you were vague on the first place.

4. most important. even when am saying am proficient , don't just take my word for it. FUCKIN REVIEW MY CODE!! Personally, I am a person who does a lot of testing on his code. Once i gave it to you, i believe that it has no possible issues and it would work in all possible cases. But if it isn't working then you should sit with me and we 2 should be looking, disccussing and debugging code, and not just me looking at the code repeatedly.

4. Don't be too hard on fresher for not doing it right. Sometimes the fresher might haven't researched so much , or you didn't told him the exact instructions but that doesn't mean you have the right to humiliate him or pressurize him

5. Let multiple people work on a same project. Sometimes its just not possible but whenever it is, as a senior one must let multiple freshers work on the same project. This gives a sense of mutual understanding and responsibility to them, they learn how to collaborate. Plus it reduces the burden/stress on a single guy and you will be eventually getting a better product faster

Am i wrong to demand those things? Would any company ever provide a learning and working environment the way i fantasize?

I am planing to create a reading list for technical books and am looking for recommendations.
Currently I have:
- Spark: The definitive Guide (need it for a university project)
- Clean Code
- Clean Architecture
- Functional Programming, simplified (or any other beginner-friendly book about FP)

Do you have any recommendations and must-reads for a more junior developer? I am looking for stuff about FP, Code Quality, Java, Python, Scala, and any general interesting technical stuff.

Lockdown has got me reading a lot of books. Books about business or startups are a lot faster for me to read. It’s like reading a story book and I’m done in a week. But reading technical books (like I’m currently reading SICP aka wizard book) is a lot more heavy duty mental work. Y’all got any pointers for me about this?