So you want a burnt out developer to show you enthusiasm of a college kid? Nice try, guys.

My job market feelings for today:
https://youtube.com/watch/...

DevRant Image upload not working...

Isn't it incredibly frustrating when they ask you to be proficient at things you haven't even worked with? I think this has got to be one of the most frustrating things as a developer, as I prefer to know and be skilled with things up front and not be dumped some tech onto me and 'here, figure it out'.

Of course, for those of us who have the deep fundamental skills in their fingertips, this isn't such a problem, and that's where I want to get.

It just hit me. Companies that badly want to use A.I. are really trying to cover for their mass incompetence.

It's hilarious when companies use Box because when someone left the company, you see their name as 'a previous collaborator'. It's sad, but yeah. lol

...or imagine if it's a startup with immature software - it might say 'NULL uploaded a document 3 years ago'. lmao

Rate your SQL skillz:

1: beginner
1a between 1 and 2
2: intermediate
2a between 2 and 3
3: advanced
3a between 3 and 4
4: expert
4a between 4 and 5
5: legendary

I'll start: 1a

!dev Applying to jobs is like solving those ground trap puzzles in videogames. lmao. Carefully make sure you solve each tile correctly... and from there you can apply the framework to vacancies.

!dev I'm currently trying to understand what snek means. Geez, slang these days... it's like fully new alien to me. lol

Hey, I already gave tips on this one. ;p

- Do one thing at a time
- Limit your effort hours (say, keep it to work hours)
- (very important) Keep a steady, hefty pace. Don't study just one hour a day (if you can), study 3 hours per evening or so. The key is to keep it to a long consistency or your brain will just forget
- Have some fun after the effort hours
- Sleep enough (8 hours minimum)

Another learned job tip:
The way you present yourself matters a ton. People respect mystery, not transparency. You don't need to post every little job you did in the past, wide open. If they ask for it explicitly, sure, give them your job history, but don't put all your little jobs on your CV or you will look like shit and get insta-rejections. Instead, wrap them in a block of 'early jobs' or something.

Learned the hard way.

Git, git, gear! Wanna train with coach Frank?

When taking so many temp notes of quick thoughts that your text editor has 40 unsaved instances.
Of course, in time I transfer them to my permanent notes.

Rofl.

What programming feels like:
https://youtube.com/watch/...

Weird error message from webpage: "Hello, my name is Inigo Montoya. You killed my webpage. Prepare to die".

It's a Princess Bride parody...

Developers get creative (or bored) these days with error messages.. Yes, one of those again.

JavaScript keeps surprising me, or I'm just rushing. lol

class Group {
#group;

constructor(){
this.group = [];
return this.group;
}

add(item) {
// only if it isn't already a member
// value can be part of set only once
if(!this.has(item)) {
group.push(item);
}
}

has(item){
// return boolean: item member of group
for(let i=0; i<group.length; i++) {
if(group[i] === item) {
return true;
}
}
return false;
}

let group = new Group();
group.add(1);
console.log(group);

Error: group.add() is not a function
Why is group.add() not a function?
A.I. analysis:

1. Private field vs public field:
A private field #group can only be accessed as this.#group. But in the constructor, I wrote:
this.group = [];

This creates a new public field, unrelated to #group.

2. Returning from constructor:
return this.group;

In JavaScript, a constructor automatically returns this, which is the instance of the class. Returning this.group replaces the instance with the array. That’s why after new Group(), your variable group is just an array, not an instance of Group. Arrays don’t have the add method — hence the error.

3. Referencing group inside methods:
group.push(item);
Here group is not defined. You probably meant this.group (or this.#group if using the private field).

Note to self: in the magic of computer science, you must be precise. If I loosely define the black box, the result will have a chance of producing anomalies.. kind of like reality. lol

I'm sitting here realizing that Software Development and Computer Science in general, heck, STEM, is the most difficult skillset to endure because of the stress we go through as well when dealing with the workplace, especially the workplace.

I looked up how hard Computer Science is versus Advanced Physics and it is rated 40 vs. 80, the latter being doubly difficult. Now I got to thinking: Could it be us as developers are experiencing near-80 difficulty because of the stress we are put through to rush through deliveries at work? Maybe it's a 50. Hm, hm.

What a delight it must be (no sarcasm) to be able to research and perfect something for 20 years without people breathing down your neck about deadlines.. aaaahhh... lol.

Story:
Useful lesson I learned in a JavaScript book:

"Classes are abstract data types in the sense that they are a layer around the complexity (encapsulation). Their singular nature allows them to be reused without being rewritten everywhere.

A good analogy is thinking of classes as appliances; the complex circuitry and components that an appliance comprises of are made by different people than the abstract shell around these components, of which (another) team only needs to know which buttons to access which parts.
A class abstracts away the internal complexity (components) and only exposes a public interface (the buttons) that the user (yet another group, comparable to the consumer of the class) is going to use."

It reminds me of how Google uses the Facade pattern to only expose the search box and the button as its public interface and all the complex architecture is hidden away.

This helped clarify classes better for me.

!rant Lovely quote:

“There are two ways of constructing a software design: One
way is to make it so simple that there are obviously no
deficiencies, and the other way is to make it so complicated
that there are no obvious deficiencies.”
—C.A.R. Hoare, 1980 ACM Turing Award Lecture

!dev Isn't it hilarious how some companies 'try' to look professional by dumping a bunch of stock images to present their brand? For example, a guy touching a holoscreen, or a bunch of overly stock happy corporate drones smiling and 'working' together in a 'meeting'.

I mean, it's sad. lol

"Block scope in console REPL:
Each line you type in the console is evaluated in a separate, temporary scope. This sometimes makes let and const behave differently than if you wrote the same code in a <script>."

Interesting... I didn't know that. lol

Coding is really just alphabet soup. Buncha libs and frameworks grouped together.

https://stackoverflow.com/questions...

JavaScript sure is a pain in the butt when it also throws errors depending if you are in a REPL or not.

Hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh.

DevRant is slow today.

I came in like a laaaaaaaaaaaaaaaaagging baaaaaaaaaaall, I never hit so haaaaaard in loooooooooove

lmao.

I found a simple code example in a book teaching programming concepts:

let result = 1;
let counter = 0;
while (counter < 10) {
result = result * 2;
counter = counter + 1;
}
console.log(result);
// 1024

...I can't believe I didn't get it right the first time. Yes, the result is 1024 and not 20. For it to result in 20, the statement would have to be:
result = result * counter.

Upon reflection I concluded: An exponent is a multiplication by a multiplication, so... it exponentially grows.

So I ask: how do you develop a second nature for these kind of problems? You studied it? You studied and practiced it? You're awesome at mathematics? It annoys me that my intuition often wrongs me when it comes to mathematics.

typeof NaN
'number'

Yes... in JavaScript, the type of NaN is Number. Go figure...

Like many of us, tired of hearing the expressions: "infused with A.I.", "powered by A.I.", "augmented with A.I.", "A.I.-first", etc.

Good dev: test suites, documentation, tracking

results: decent coverage, more predictable, more maintainable, saves time and money, accountable to stakeholders, happier team thanks to transparency

environment: matured middle-sized to bigger company who takes things seriously (because they usually have to if they work in a heavily regulated sector)

Bad dev: idgaf attitude, let's just run with it and see what happens flow, go for bare minimum happy path

results: a new bug at every possible situation, mystery bugs, an endlessly-growing backlog where people in the team are so depressed no one cares what ticket to take on, morale goes down crapshoot and so does code

environment: start-ups who want quick wins and make money-based decisions only and whose budget is being guarded by the higher-ups

I've worked with a bad dev before and also with a good dev and I appreciate the difference. lol. Nightmare.

Job-hunting feels like playing Age of Empires; the cities are guarded by the recruiters.

Rogan? Wololoo.

Bro. Why?

There are still websites that miss the simple, modern UX feature of saving form state. No, it's not 'push a button to apply the filter' anymore, it should be 'tick the box, slide the slider' and the state gets persisted immediately.

Or something else: perform a search, apply filters, and the original search is lost. Tf, man? lol.

This just shows that some places aren't investing.