As a developer, sometimes you hammer away on some useless solo side project for a few weeks. Maybe a small game, a web interface for your home-built storage server, or an app to turn your living room lights on an off.

I often see these posts and graphs here about motivation, about a desire to conceive perfection. You want to create a self-hosted Spotify clone "but better", or you set out to make the best todo app for iOS ever written.

These rants and memes often highlight how you start with this incredible drive, how your code is perfectly clean when you begin. Then it all oscillates between states of panic and surprise, sweat, tears and euphoria, an end in a disillusioned stare at the tangled mess you created, to gather dust forever in some private repository.

Writing a physics engine from scratch was harder than you expected. You needed a lot of ugly code to get your admin panel working in Safari. Some other shiny idea came along, and you decided to bite, even though you feel a burning guilt about the ever growing pile of unfinished failures.

All I want to say is:

No time was lost.

This is how senior developers are born. You strengthen your brain, the calluses on your mind provide you with perseverance to solve problems. Even if (no, *especially* if) you gave up on your project.

Eventually, giving up is good, it's a sign of wisdom an flexibility to focus on the broader domain again.

One of the things I love about failures is how varied they tend to be, how they force you to start seeing overarching patterns.

You don't notice the things you take back from your failures, they slip back sticking to you, undetected.

You get intuitions for strengths and weaknesses in patterns. Whenever you're matching two sparse ordered indexed lists, there's this corner of your brain lighting up on how to do it efficiently. You realize it's not the ORMs which suck, it's the fundamental object-relational impedance mismatch existing in all languages which causes problems, and you feel your fingers tingling whenever you encounter its effects in the future, ready to dive in ever so slightly deeper.

You notice you can suddenly solve completely abstract data problems using the pathfinding logic from your failed game. You realize you can use vector calculations from your physics engine to compare similarities in psychological behavior. You never understood trigonometry in high school, but while building a a deficient robotic Arduino abomination it suddenly started making sense.

You're building intuitions, continuously. These intuitions are grooves which become deeper each time you encounter fundamental patterns. The more variation in environments and topics you expose yourself to, the more permanent these associations become.

Failure is inconsequential, failure even deserves respect, failure builds intuition about patterns. Every single epiphany about similarity in patterns is an incredible victory.

Please, for the love of code...

Start and fail as many projects as you can.

Interview.

X: So, do you have any weaknesses?
Y: Yes, I'm very honest.
X: But I don't think that's a weakness
Y: I don't give a fuck what you think

Things I wish I could tell my 18 year old self.

1) Accept you will make mistakes.
2) Truly learn the language you are using.
3) Write idiomatic code for the language you are using.
4) Be upfront about not knowing something.
5) Don't let not knowing something stop you from learning it.
6) None of us knew X until we learned it.
7) Understand your strengths and weaknesses as a developer, play to them.
8) Be willing to try new things.
9) X language isn't ALWAYS the best choice, X paradigm isn't ALWAYS the best choice. Choose wisely.
10) You won't know everything, but you might know more than others.
11) Your ideas and ego don't matter more than ensuring the product works.
12) "Perfection is the enemy of the good [enough]" - Voltaire
13) "Perfection is not achieved when there's nothing more to add, but when there's nothing more to remove." - Einstein.
14) Conflicts happen, deal with it.
15) Develop a toolset and really learn them.
16) Try new tools, they may prove better than what you were using.
17) Don't manage your own memory unless you absolutely have to, you are probably not smarter than the collective intelligence of the team that built the various garbage collection methods.
18) People can be dicks, especially online.
19) If you are new and people are being dicks to you, did you skip past the irc message about etiquette? If you did, you're the dick in this situation.
20) It can be tough, but it is fun, so have fun!

Worst of 2020:

Seeing company get stuck in an organizational swamp. Devs tend to be reasonably good at working from home...

Management isn't. Meeting quality has gone down the drain, half of management thinks "if the boss can't see me why work at all?", the other half has constant calls with tiny working groups where nothing is final and everyone is left confused.

I'm convinced: Everything management is afraid of about allowing devs to work from home is based on projection of their own weaknesses.

They're not passionate enough to work without oversight. They might not be introverts, but extroverts are perfectly able to communicate poorly, especially when a few digital hurdles get in the way.

The average developer might actually be more attuned to the intricacies of emotionless text chats, and preventing disruptive elements in video calls.

Also, unless someone physically helps a manager to remove their head from their own ass once in a while, their "gut feelings" about the market and products are actually just amplified bias caused by their endless self-absorbed yelling into the echo chamber that is their stretched out rectum.

Holy motherfucking hell, have I seen some weird projects float by in 2020, pooped out by isolated product managers whose brain clearly has melted when they had to survive without office fruitbaskets and organizational post-it walls.

Yeah let's promote our international character, by giving away travels and hotel bookings, using pictures of happy hugging people in foreign countries... Great promo during a pandemic.

Or let's get "woke" and promote the "colored users" on our platforms, by training ML to categorize people by skin pigment (Apart from how illegal and ethically insane that is on multiple levels, about 85% of our users pick shit like anime characters and memes for their avatar).

Or how about we make a Microsoft Store app, even though the vast majority of our end users are students using cheap Android phones, older iPhones, Macbooks and Chromebooks.

😡

Anyway, now that I have dressed up my Christmas tree with some manager intestines...

Best of 2020:

I got to play through my Steam backlog, work on hobby projects, and watch a lot of YouTube.

All this pandemic insanity has convinced me all the more that I want to work way more in Rust, and publish way more on open source projects.

I became maintainer/collaborator on a bunch of semi-prominent libraries & frameworks, and while no community is perfect, I enjoy my laid-back coffee-fueled debugging on those packages much more than listening to another crack addicted cocksucker in a suit explain their half-assed A/B test idea to me at 9AM.

So, 2021 will be me half-assing through the spaghetti at my official fuckfest of a job so I can keep filling my bank account — and investing way more time and effort into stuff I find truly engaging, into projects with a heart and a soul.

So, I was participating in a competition, but little did I know that you could only participate in pairs. Seeing that a lot of famous indie devs were participating I was extremely hyped. But since it seemed like I was the only idiot who didn't have a partner I felt like kicking myself. Then a guy about whom I had never heard of before, probably a newbie, comes out of the blue and asks me to be his partner. Since I had no choice, I reluctantly agreed to pair up with him. The rules of the competition were to create a game based on a particular theme in a period of 1 week. To get started, I asked him about his skills as it would be better to know what our strengths and weaknesses were. He said that he was good at art and proceeded to show me some of his "previous works". I was genuinely impressed. Honestly speaking his drawing seemed a bit off but was but for a newbie, it was good. So we decided that he would take care of the art and I would code, create some basic music (nothing too fancy because of the lack of time) and if time permits, refine his art(correcting ratios, colour combinations, shading, etc.). On the first day, he would like to work in privacy and would show only the finished products to me. It seemed a bit fishy, but hey, I am all up for respecting the wishes of fellow team members.
So all was going well, or so I thought, till on the fifth day the guy confesses that he didn't get shit done. Apparently, his "previous works" were random stuff taken from the great land of internet and that he had to leave town the next day. He just wanted to "experience the life of a game developer" and "meant no harm". I flipped out, half lectured half screamed at him then asked him to get the fuck out which happened to be the only fucking thing that he was able to do correctly. I thought for an hour or so, then contacted the staff and informed them about my situation. They said that if I was okay with the handicap, I may continue. I then pulled three all nighters with about 3 hours of sleep (that too in parts of about 1 hour) everyday and was barely able to submit my game on time.
I secured the fifth place, which was pretty good if I may say so myself, but it an important lesson in my life that taught me to never trust anyone blindly.

Working on the notes service and I'm still at the signup/login/password reset part.

Spending hours on thinking the process through, trying to think of any possible weaknesses in the system and writing patches right away.
I find it funny how thinking through every step (code-wise and user-wise) gives a very broad overview of how secure/insecure this thing is.

I fucking love doing this.

I taught my 9yo sister to SSH from my Arch Linux system to an Ubuntu system, she was amazed to see terminal and Firefox launching remotely. Next I taught her to murder and eat all the memory (I love Linux, as Batman, one should also know the weaknesses). Now she can rm rf / --no-preserve-root and the forkbomb. She's amazed at the power of one liners. Will be teaching her python as she grew fond of my Raspberry Pi zero w with blinkt and phat DAC, making rainbows and playing songs via mpg123.
I made her use play with Makey Makey when it first came out but it isn't as interesting. Drop your suggestions which could be good for her learning phase?

Another hackathon is over.

Didn't win this one either but I am slowly recognising my weaknesses and (hopefully) getting better.

A good night's sleep and I'm ready for the next one. :)

Beyond Hackathon 2017 @ Athens, Greece

Story time on my job hunt: Currently interviewing with Google during my notice period.

I always had a love hate relationship with Google. Unlike my hate towards Meta or Amazon, where I had a reason to hate them for how ill intended they are, I never had a valid reason to dislike or hate Google apart from the fact that they steal my data.

That's it. That's my only reason why I hate Google. But I fell in love with their products during my trip to Istanbul and how throughout my journey, Google products were there for me to solve all my needs.

As y'all know, I was treated badly during my Meta interview, last October. With Google, the experience is on another level.

People are fucking smart and ingenious, but at the same time very polite, humble, and respectful.

During my 3 interviews so far (2 more remaining), each one of them made me so comfortable that I was more anxious before the interview than during or after.

They supported me during each question they asked. They made me felt heard and focused on my strength, instead of the weaknesses (or trying to break me down unnecessarily).

The interview syllabus is so fucking vast, and recruiters know so much that they helped me not only with preparation material, but also guided me personally. Haven't seen such knowledgeable recruiters.

The questions were dynamic in nature and thankfully because of my preparation, I was able to answer them most.

Overall, the culture at Google seems brilliant and an environment where one can flourish. No wonder companies are trying to copy every aspect of how Google operates and no surprise that Google is doing well at scale.

I feel so high on emotions (positively), after these interviews that I wonder how would it be to work at Google with such phenomenal people and exceptional environment.

To long to read. So don’t do it.

I feel disappointed. It’s not about job or stuff. I’m disappointed about world in general. I don’t see my future on this planet anymore.

The world more or less looks like that :

Politics are trying to help you by stealing more money from you. The more you’re lucky the more money you will pay for it.

Media punch you with some family stuff from everywhere, give you young rich and far away, beautiful picture photos of places, people and food that you at most could visit once or twice per year during holidays that are break from work concentration camps.

If you’re lucky you’re rich or got rich or wealthy and infamous so you can walk wherever you want and don’t give a fuck what you wear but again your old friends are not so lucky bastards so you need to find new friends that are probably assholes. At the end most of the days you you’re doing nothing except killing time to meet with people you like during weekends or evenings.

Then there are families and everyone want to tell you that’s important. Family is like herd of assholes, if you’re weak they will sacrifice you and tell that you’re looser behind your back but when you get wealthy they will come back to tell you that when you were young and stupid they played with you so now you have to buy them some stuff or get them a job.

At the end there are people with “I wrote that book” certificate of excellence try to sell you opinions on everything starting from sexual positions ending on how to take a good dump. The problem is that the moment they wrote that book it becomes obsolete. Teachers of useless knowledge from last century that forgot about google or wikipedia.

All of them are playing your emotions, cause impulses and hormones are what makes you weak and people are looking for your weaknesses to take advantage of you. Get your money or get your attention and maybe even both at the same time. Cause views matter you know it. So like and subscribe dumb fucks.

If you’re lucky you find couple of them who aren’t doing that. Who the fuck knows why but this shit happens. It doesn’t matter if they’re family or you met them month ago. Those are only to keep and hardest to find. Unluckily those also can change by other people they meet or when they’re young.

If you can’t find a friend get a dog or cat or whatever animal you like. Their love is unconditional and obvious to read.

Well that’s most of the “I want to be spotted” culture that is all boring as fuck. Personalized ass and glamorous pictures and short movies of everything you don’t need but looks awesome. And as you see it’s still growing with more specialized portals like onlyfans, twitch and tiktok. We all need to look at what everyone else have or want to have cause 99% of time 99% of us are boring and is bored as fuck. Most of us can repeat same small amount set of stories all their life cause we’re not created to entertain.

I don’t feel joy looking at this shit fucked full of shit people arguing who’s dick is bigger. Who can post most dumb thing. I think I need a break but how to break from everything ? How to break from culture of money where to live on your country land you need to pay property tax ?

That’s all fucked up. Life’s fucked up.

Best: give him a GitHub repo and tell him to add a feature or change something

Worst: What are your greatest strengths and weaknesses?

"What are your strengths/weaknesses?" and similar questions.

"Name 5 weaknesses of yours in the workplace and explain to me how you try to improve yourself based on these."

Just laughed at the question since I expected to name maybe 1 or 2 instead of 5. Only named a few from the top of my head, but this question is bullshit anyways.

Should just have noped out of there instead though since the company was poorly organized.

Just had a great interview :)

The guy was really cool, asked actually relevant questions (my learning process, what I specialize in, etc), talked about the tech they'll be using and none of that "wHaT aRe YoUr WeAkNeSsEs?" bullshit.

He seemed to like me, he seemed to like the fact that I've been programming for a long time even though I'm in my second semester in college and he also seemed to like that I'm somewhat of a Swiss army knife, a jack of all trades but master of none.

I just I was a bit too informal in the interview but whatever. I'm not taking this very seriously, if I get the job I get the job, if I don't that's fine too.

Do real interviewers (I mean those who are smart and have some experience) still ask questions like "what are your weaknesses"?

Dumbass, why the fuck should I declare, not just to you but also to myself, that I have some particular weaknesses? I know what I'm not good at, and I'll keep trying to improve. But unless my weakness is that I get a massive boner during team meetings, you don't need to know about it. I'm not telling you. Just know my strengths - that's enough. If you're just following a standard list of interview questions that you didn't even come up with, stop pretending to be an interviewer for heavens' sake.

dev, ~boring

This is either a shower thought or a sober weed thought, not really sure which, but I've given some serious consideration to "team composition" and "working condition" as a facet of employment, particularly in regard to how they translate into hiring decisions and team composition.

I've put together a number of teams over the years, and in almost every case I've had to abide by an assemblage of pre-defined contexts that dictated the terms of the team working arrangement:

1. a team structure dictated to me
2. a working temporality scheme dictated to me
3. a geographic region in which I was allowed to hire
4. a headcount, position tuple I was required to abide by

I've come to regard these structures as weaknesses. It's a bit like the project management triangle in which you choose 1-2 from a list of inadequate options. Sometimes this is grounded in business reality, but more often than not it's because the people surrounding the decisions thrive on risk mitigation frameworks that become trickle down failure as they impose themselves on all aspects of the business regardless of compatibility.

At the moment, I'm in another startup that I have significantly more control over and again have found my partners discussing the imposition of structure and framework around how, where, why, who and what work people do before contact with any action. My mind is screaming at me to pull the cord, as much as I hate the expression. This stems from a single thought:

"Hierarchy and structure should arise from an understanding of a problem domain"

As engineers we develop processes based on logic; it's our job, it's what we do. Logic operates on data derived from from experiments, so in the absence of the real we perform thought experiments that attempt to reveal some fundamental fact we can use to make a determination.

In this instance we can ask ourselves the question, "what works?" The question can have a number contexts: people, effort required, time, pay, need, skills, regulation, schedule. These things in isolation all have a relative importance ( a weight ), and they can relatively expose limits of mutual exclusivity (pay > budget, skills < need, schedule < (people * time/effort)). The pre-imposed frameworks in that light are just generic attempts to abstract away those concerns based on pre-existing knowledge. There's a chance they're fine, and just generally misunderstood or misapplied; there's also a chance they're insufficient in the face of change.

Fictional entities like the "A Team," comprise a group of humans whose skills are mutually compatible, and achieve synergy by random chance. Since real life doesn't work on movie/comic book logic, it's easy to dismiss the seed of possibility there, that an organic structure can naturally evolve to function beyond its basic parts due to a natural compatibility that wasn't necessarily statistically quantifiable (par-entropic).

I'm definitely not proposing that, nor do I subscribe to the 10x ninja founders are ideal theory. Moreso, this line of reasoning leads me to the thought that team composition can be grown organically based on an acceptance of a few observed truths about shipping products:

1. demand is constant
2. skills can either be bought or developed
3. the requirement for skills grows linearly
4. hierarchy limits the potential for flexibility
5. a team's technically proficiency over time should lead to a non-linear relationship relationship between headcount and growth

Given that, I can devise a heuristic, organic framework for growing a team:

- Don't impose reporting structure before it has value (you don't have to flatten a hierarchy that doesn't exist)
- crush silos before they arise
- Identify needed skills based on objectives
- base salary projections on need, not available capital
- Hire to fill skills gap, be open to training since you have to pay for it either way
- Timelines should always account for skills gap and training efforts
- Assume churn will happen based on team dynamics
- Where someone is doesn't matter so long as it's legal. Time zones are only a problem if you make them one.
- Understand that the needs of a team are relative to a given project, so cookie cutter team composition and project management won't work in software
- Accept that failure is always a risk
- operate with the assumption that teams that are skilled, empowered and motivated are more likely to succeed.
- Culture fit is a per team thing, if the team hates each other they won't work well no matter how much time and money you throw at it

Last thing isn't derived from the train of thought, just things I feel are true:

- Training and headcount is an investment that grows linearly over time, but can have exponential value. Retain people, not services.
- "you build it, you run it" will result in happier customers, faster pivoting. Don't adopt an application maintenance strategy

/rant

Once again I have loads.

My best teachers were...

The contractor that taught me C#, ASP MVC and SQL Server. Dude was a legend, so calm and collected. He wanted to learn JQuery and Bootstrap so at the same time as teaching, he was learning from me. Such an inspirational person, to know your subordinates still have something to teach you. He also taught me a lot about working methodically and improving my pragmatism.

The other, in school I studied computing A-Level. 100% scored at least one of the exams... basically I knew my stuff.

But, as a kid, I didn’t know how to formulate my answers, or even string together coherent answers for the exams. This dude noticed, first thing he did was said “well you’re better at this bit than me, practice but you’ll be fine” (manually working out two’s complement binary of a number).

Second thing he did was say “you know what man, you know what you’re on about but nobody else is ever going to know that”.

He helped me on the subjects I wasn’t perfect on, then he helped me on formulating my answers correctly.

He also put up with my shit attendance, being a teenager with a motorcycle who thinks he knows it all, has its downsides.

As a result, I aced the hell out of that course, legendary grades and he got himself a bit of a bonus for it to use on his holiday. Everyone’s a winner.

Liam, Jason, if you guys are out there I owe you both thanks for making me the person I am today.

The worst, I’ve had too many to name... but it comes down to this:
- identify your students strengths and weaknesses, focus on the weaknesses
- identify your own and know when to ask for help yourself
- be patient, learning hurts.

You can always tell a passionate teacher from one who’s there for the paycheck.

(long post is long)
This one is for the .net folks. After evaluating the technology top to bottom and even reimplementing several examples I commonly use for smoke testing new technology, I'm just going to call it:

Blazor is the next Silverlight.

It's just beyond the pale in terms of being architecturally flawed, and yet they're rushing it out as hard as possible to coincide with the .Net 5 rebranding silo extravaganza. We are officially entering round 3 of "sacrifice .Net on the altar of enterprise comfort." Get excited.

Since we've arrived here, I can only assume the Asp.net Ajax fiasco is far enough in the past that a new generation of devs doesn't recall its inherent catastrophic weaknesses. The architecture was this:

1. Create a component as a "WebUserControl"
2. Any time a bound DOM operation occurs from user interaction, send a payload back to the server
3. The server runs the code to process the event; it spits back more HTML

Some client-side js then dutifully updates the UI by unceremoniously stuffing the markup into an element's innerHTML property like so much sausage.

If you understand that, you've adequately understood how Blazor works. There's some optimization like signalR WebSockets for update streaming (the first and only time most blazor devs will ever use WebSockets, I even see developers claiming that they're "using SignalR, Idserver4, gRPC, etc." because the template seeds it for them. The hubris.), but that's the gist. The astute viewer will have noticed a few things here, including the disconnect between repaints, inability to blend update operations and transitions, and the potential for absolutely obliterative, connection-volatile, abusive transactional logic flying back and forth to the server. It's the bring out your dead approach to seeing how much of your IT budget is dedicated to paying for bandwidth and CPU time.

Blazor goes a step further in the server-side render scenario and sends every DOM event it binds to the server for processing. These include millisecond-scale events like scroll, which, at least according to GitHub issues, devs are quickly realizing requires debouncing, though they aren't quite sure how to accomplish that. Since this immediately becomes an issue with tickets saying things like, "scroll event crater server, Ugg need help! You said Blazorclub good. Ugg believe, Ugg wants reparations!" the team chooses a great answer to many problems for the wrong reasons:

gRPC

For those who aren't familiar, gRPC has a substantial amount of compression primarily courtesy of a rather excellent binary format developed by Google. Who needs the Quickie Mart, or indeed a sound markup delivery and view strategy when you can compress the shit out of the payload and ignore the problem. (Shhh, I hear you back there, no spoilers. What will happen when even that compression ceases to cut it, indeed). One might look at all this inductive-reasoning-as-development and ask themselves, "butwai?!" The reason is that the server-side story is just a way to buy time to flesh out the even more fundamentally broken browser-side story. To explain that, we need a little perspective.

The relationship between Microsoft and it's enterprise customers is your typical mutually abusive co-dependent relationship. Microsoft goes through phases of tacit disinterest, where it virtually ignores them. And rightly so, the enterprise customers tend to be weaksauce, mono-platform, mono-language types who come to work, collect a paycheck, and go home. They want to suckle on the teat of the vendor that enables them to get a plug and play experience for delivering their internal systems.

And that's fine. But it's also dull; it's the spouse that lets themselves go, it's the girlfriend in the distracted boyfriend meme. Those aren't the people who keep your platform relevant and competitive. For Microsoft, that crowd has always been the exploratory end of the developer community: alt.net, and more recently, the dotnet core community (StackOverflow 2020's most loved platform, for the haters). Alt.net seeded every competitive advantage the dotnet ecosystem has, and dotnet core capitalized on. Like DI? You're welcome. Are you enjoying MVC? Your gratitude is understood. Cool serializers, gRPC/protobuff, 1st class APIs, metadata-driven clients, code generation, micro ORMs, etc., etc., et al. Dear enterpriseur, you are fucking welcome.

Anyways, b2blazor. So, the front end (Blazor WebAssembly) story begins with the average enterprise FOMO. When enterprises get FOMO, they start to Karen/Kevin super hard, slinging around money, privilege, premiere support tickets, etc. until Microsoft, the distracted boyfriend, eventually turns back and says, "sorry babe, wut was that?" You know, shit like managers unironically looking at cloud reps and demanding to know if "you can handle our load!" Meanwhile, any actual engineer hides under the table facepalming and trying not to die from embarrassment.

If I had to name one of my weaknesses it would definitely be impatience.

When I'm working on a backlog issue I want it to be done, finished, pronto. In the real world that's ofcourse not always the case, I can't disturb my colleagues with every question or ask for feedback every minute. I also hate it to have to wait for someone else to do something for me if it's blocking me, like when I need to fix something on a server but don't have access or when I somehow don't have permission for something and have to wait for someone to come and fix it. Even worse: Slow programs that fuck me up when I _just a second ago_ figured out how to fix a bug or implement something.

I also have to wait for pull request reviews so I usually end up with a bunch of stacked PRs that all feature small changes but are dependent upon each other because I needed a change for a different change, never more than 2-level stacks though!

Obviously it's a bit childish to lack professional patience, but it's definitely something that I wanted to rant about and think I should grow in.

My wife is a bigger nerd that me. She just told me Rooster Teeth is shutting down. Who knows shit like that? I haven't looked at anything Rooster Teeth since Red vs Blue.

Earlier conversation with her about something else:
Me: I can't believe how stupid people are. I cannot believe people are stupid enough to...
Her: Hold up. You really need to expand your imagination about how stupid people can actually be.
Me: I am not smart enough to understand how stupid people can be.

Yeah, I think she may be the smart one. She makes up for my weaknesses.

How many of you use the right data structures for the right situations?

As seasoned programmer and mentor Simon Allardice said: "I've met all sorts of programmers, but where the self-taught programmers fell short was knowing when to use the right data structure for the right situation. There are Arrays, ArrayLists, Sets, HashSets, singly linked Lists, doubly linked Lists, Stacks, Queues, Red-Black trees, Binary trees,.. and what the novice programmer does wrong is only use ArrayList for everything".

Most uni students don't have this problem though, for Data Structures is freshman year material. It's dry, complicated and a difficult to pass course, but it's crucial as a toolset for the programmer.

What's important is knowing what data structures are good in what situations and knowing their strengths and weaknesses. If you use an ArrayList to traverse and work with millions of records, it will be ten-fold as inefficient as using a Set. And so on, and so on.

Tough one.

One of my biggest weaknesses is that I'm having trouble with positive feedback.

It's kinda self defense because positive feedback usually means that a negative thing will happen.

One of the moments where I feel like a dev hero is when I can just accept the positive feedback.

What is your greatest weakness?

My greatest weakness is that I don't trust people enough to let them know how the can leverage me by telling them my weaknesses.

IT teach giving a speech that our MS excel exams are shit and we have no logic and that we suck at math. I mean, yeah it's true that I suck at math and I've never used excel before coz I never had to but ffs I code during nights and I love it, also there are so many fields, saying that you'll be just a part-time waiter... If you have the attitude to solve a problem that you care enough about you'll get there eventually. Sucking at something doesn't mean you suck at everything, everyone has their strengths and weaknesses.

Focus on your strengths and not your weaknesses. Oh and wear one of those Polo Pullovers, that way you'll say "Hire me, because I'm that cool kinda sexy but douchey as fuck developer you guys need in your life". That should get the job done or job gotten.

I don't understand why languages like JavaScript and PHP decided to bolt on typing and object-oriented stuff retroactively. In fact, it actually makes me kind of angry.

The whole point of weakly-typed languages is so that you don't have to worry about the types. Everything that you do to an object is evaluated at runtime. The advantage of this is so you don't have to worry about types which improves speed of development. You do lose the benefits of strongly-typed languages, but I'm assuming everyone who uses a weakly-typed language is ok with that tradeoff, otherwise they would be using a strongly-typed language.

But then they go and add strongly-typed things to weakly-typed languages, like they somehow "discovered" that there are actually benefits to using strongly-typed languages. The thing is that adding this back in just dilutes the weakly-typed nature of the language to the point where you don't really get the benefits of its strongly-typed-ness or its weakly-typed-ness. And don't tell me you can just use either, because if you're working on a project with multiple people you can never really be sure what is going to happen if both the options are there.

I have an idea, how about we let Java be good at what it's good at and let JavaScript be good at what it's good at, and stop trying to make them into the same language. Languages have strengths and weaknesses and that's ok. We just have to learn what they are and when it's good to use certain languages over others.

So I had my first "real" interview today. It was for an internship at a big company and I really wanted that internship. I know I'm more than capable for that position and I made a hell of a good job on the coding challenge they sent (or at least I think so). But I went unprepared for that interview and I think I fucked up.

The guy asked me what were my strengths and weaknesses (of fucking course, cliche question). I had no idea what to answer, I was caught completely off guard. So I said I never quit as a strength and I couldn't think of any weaknesses. It was a very corny response but I didn't mean to say exactly that. I wanted to say that even if something is frustrating and I have to bang my head against the wall for three days, I won't give up on a task. It's basically the same as saying what I said, but it does feel nicer and less corny y'know? And as a weakness I could've said that I didn't have experience working with a team, as I've always worked solo.

I could have been awesome, but I didn't prepare myself for the interview. I really, really wanted that internship since that'd be awesome on my resume, I'd earn some of my own money and I'd learn a whole fucking lot.

Deep down I still have some hope that I'll get an e-mail back and I'll get the position, but I think I won't. This sucks. I am qualified, BUT I DID AN AWFUL JOB ON LETTING THEM KNOW I'M QUALIFIED.

I just wanted it so bad :(

I would get a testing job and thus exploit weaknesses in the ai- created software.

After finding such weaknesses, I would write AI debilitating viruses and WannaCry-like ransomware until I get my job back!

If that doesn't work out, I'd go into linguistics.

I can't help it sounding bitter..
If you work some amount of time in tech it's unavoidable that you automatically pick up skills that help you to deal with a lot of shit. Some stuff you pick up is useful beyond those problems that shouldn't even exist in the first place but lots of things you pick up over time are about fixing or at least somehow dealing or enduring stuff that shouldn't be like that in the first place.
Fine. Let's be honest, it's just reality that this is quite helpful.

But why are there, especially in the frontend, so many devs, that confuse this with progress or actual advancement in their craft. It's not. It's something that's probably useful but you get that for free once you manage to somehow get into the industry. Those skills accumulate over time, no matter what, as long as you manage to somehow constantly keep a job.
But improving in the craft you chose isn't about somehow being able to deal with things despite everything. That's fine but I feel like the huge costs of keeping things going despite some all the atrocities that arose form not even considering there could be anything to improve on as soon as your code runs. If you receive critic in a code review, the first thing coming back is some lame excuse or even a counter attack, when you just should say thank you and if you don't agree at all, maybe you need to invest more time to understand and if there's some critic that's actually not useful or base don wrong assumptions, still keep in mind it's coming from somebody that invested time to read your code gather some thoughts about it and write them down for you review. So be aware of the investment behind every review of your code.
Especially for the frontend getting something to run is a incredibly low bar and not at all where you can tell yourself you did code.
Some hard truth from frontend developer to frontend developer:
Everybody with two months of experience is able to build mostly anything expected on the job. No matter if junior or senior.
So why aren't you looking for ways to find where your code is isn't as good as it could be.

Whatever money you earn on top of your junior colleagues should make you feel obligated to understand that you need to invest time and the necessary humbleness and awareness of your own weaknesses or knowledge gaps.
Looking at code, that compiles, runs and even provides the complete functionality of the user story and still feeling the needs do be stuff you don't know how to do it at the moment.

I feel like we've gotten to a point, where there are so few skilled developer, that have worked at a place that told them certain things matter a lot Whatever makes a Senior a Senior is to a big part about the questions you ask yourself about the code you wrote if if's running without any problems at all.
It's quite easy to implement whatever functionality for everybody across all experience levels but one of your most important responsibilities. Wherever you are considered/payed above junior level, the work that makes you a senior is about learning where you have been wrong looking back at your code matters (like everything).

Sorry but I just didn't finde a way to write this down in a more positive and optimistic manner.

And while it might be easy to think I'm just enjoying to attack (former) colleaues thing that makes me sad the most is that this is not only about us, it's also about the countless juniors, that struggle to get a food in the door.
To me it's not about talent nor do I believe that people wouldn't be able to change.
Sometimes I'm incredibly disappointed in many frontend colleagues. It's not about your skill or anything. It's a matter of having the right attitude.
It's about Looking for things you need to work in (in your code). And investing time while always staying humble enough to learn and iterate on things. It's about looking at you
Ar code and looking for things you didn't solve properly.

Never forget, whenever there's a job listing that's fording those crazy amount of work experience in years, or somebody giving up after repeatedly getting rejected it might also be on the code you write and the attitude that 's keeping you looking for things that show how awesome you are instead of investing work into understanding where you lack certain skills, invest into getting to know about the things you currently don't know yet.
If you, like me, work in a European country and gathered some years of industry experience in your CV you will be payed a good amount of money compared to many hard working professions in other industries. And don't forget, you're also getting payed significantly more than the colleagues that just started at their first job.
No reason to feel guilty but maybe you should feel like forcing yourself to look for whatever aspect of your work is the weakest.

There's so many colleagues, especially in the frontend that just suck while they could be better just by gaining awareness that there code isn't perfect.

Is Lua worth learning?
What can be achieved easily with it? What are it's strengths and weaknesses?

Laptop battery! CURSES!! My one of many weaknesses in coding on the go!!

Part of my remote work is to have a daily call reporting in on what I have done yesterday and what I am about to today. My colleague calls me for it. She's hired as a tech support and is suddenly assigned to take note and report on my work activities to our boss. Several times, I caught her pretending to know what I'm talking about like with Puppet configurations, Firewall diagnosis packets, ActiveMQ, Regex, etc. Most of the time, I just let it go as its not my job to validate her knowledge on these different but many services. Just do the call, get the report in, carry on. How difficult was that?

Yesterday, our call was left sour because I somehow blew up. I think I've reached my patience with this woman's assumptions to how these services work. Now I feel guilty for yelling at a lady but goddamn she stoopid for fibbing through my ear. Somebody help! What do I do?

If I report to our boss about her technical incompetence (politely), she might get sacked. She's a good tech support as long as she still has her trusty manuals by her, she can fix specific problems. But when it comes to unknown tech to her, she assumed she knew.

If I tell her about her weaknesses, however constructive I can get and as politely as I can get, all the while complimenting something about her, showing her how to improve herself, maybe she'll do better not to ask silly questions like buying a Puppet certificate? At least getting rid of ignorance would definitely help but not sure how she would take it. The worst thing I would imagine is her backfiring and yelling at me and then we ended up fighting.

If I kept quiet and tuck it all into a can, it will eventually implode as we go on.

This is not about her gender. I don't see her as a woman. I see her as a tech support engineer who should know her stuff.

- Never lie, if you get the job and they find out you lied on something you have a problem
- Never say "oh this company is too good it will never accept me with my grades", Usually bigger companies have an assessment center where you can show that you are good for this job
- If they ask you for weaknesses try to pick some that can also be seen as strengths

!rant

So I'm gonna attend my first interview tomorrow. Just wanted to know what you all usually answer for the question "what are your weaknesses?". I know there are multiple results on Google for this but I wanted to devs' approach to this