Skip to content
loading...
Discussion
markdown guide
 
 
 
 

The newest MacOS lets you remap capslock to escape, so it'll work like real operating systems.

 

You can do this with karabiner on all OS versions
And even take it to a crazy level with this: github.com/Vonng/Capslock

Best experience I got for me was remapping § (non_us_backslash) to esc with karabiner. The only downside is I sometimes miss the escape key on mechanical keyboards, because I got used to it..
karabiner mapping
Edit: Whoops, just realised this only makes sense for non US layouts (I'm using a Swiss layout). Guess you need your ~ key, this is what my top-left key looks like:
swiss layout

You kinda can. I couldn't get karabiner to work with the latest versions.
It's weird what gets changed in MacOS versions. For every thing they fix they bring in some other unnecessary restriction.

Apple don't use ISO layouts, so their "UK" keyboard is a half US, half UK and half Stargate DHD.

Are you saying Karabiner doesn't work with macOS Catalina? Another reason not to upgrade :D I'm using a fantastic Microsoft Keyboard with Mac and Karabiner is essential :D

I'm not certain if it does now; it didn't when I upgraded.

 

Ditto. Finally I can hit a physical ESC key on my 16" MBP, I'm ok with the TouchBar but they should have put a separate ESC key from the beginning.

 
 

Thanks to that, I can have the thing I missed most on the Mac keyboard
del

 

When you press fn and backspace the same time this works by default

Everyday something new. And I even searched for this, and all my colleagues have Mac and no one told me about this... Anyway I like the touchbar and the fact that it can be configured(via 3rd party apps) in any way you want.

 
 
 

Seriously! That whole bar seems designed to allow me to accidentally click on Siri when I do not want to but have difficulty clicking on a button that I actually want to click.

 

My god, every bloody day. Do you want to use Siri? Noooo!!!

 

You can remove Siri from the touchbar in the system preferences. First thing I did when I got my mbp:D

 

This is a very apt metaphor for the whole Apple ecosystem.

 
 
 

There's a desperate need for developers, but companies aren't investing in onboarding programs to develop new developers into experienced developers. One or two years experience in a poorly organized company makes a new developer marketable to bigger companies, but by then they may have developed poor habits. Why not just recruit new developers and put them under mid-senior devs and develop somebody to take the place of the mid-senior when they bounce after 2.5 years (avg).

 

That is actually something I have been working on. Luckily last year I helped 44 developers land their first jobs in tech. Very passionate about this but the solution to this is a part marketing problem, part risk problem.

It is risky and costs money to train new talent. It is a very high gamble. But it can be done. If I can do it in a city like Memphis,TN it can be done anywhere. Just have to market the hell out of yourself.

 

That's fantastic Danny. I hope some of those 44 will turn around and do the same for others and not just throw up the same barriers and hurdles that they faced themselves.

RE: just have to market the hell out of yourself...truer words have not been uttered.

I will say this. Please do not underestimate how powerful linkedin really is! I have gotten more people jobs just off of linkedin alone than anything else! Hiring managers will be more likely to call you in straight for an interview. most of the people I help just go straight in for an interview as opposed to filling out countless applications.

If you need some advice or help just hit me up and I will see if there are some tips I can give you.

 

but the solution to this is a part marketing problem, part risk problem.

You hit the nail on the head. The current disorganization of what's left of the labor market precludes anything resembling the old-style apprenticeships or getting us their benefits.

Our company has created internal programs specifically to address this huge need. But tying these kinds of activities to revenue, to connect it to value given to the customers, is the real trick.

 

As a junior/mid dev looking for a job, the pain is real. Not all of us want to work at a top 5 or even 10 tech company. I just want to be able to work with a good knowledgeable team where I can learn and contribute.

 

As another jr/mid-level dev, I feel your pain, Glenn!

 

This is a perennial tech problem. The market grows so much that the majority of engineers seem to always be new engineers (< 1/2 years). I don't think this problem will ever truly go away unless the market stops expanding.

 
 

There's an overall tragedy of the commons going on there way beyond onboarding programs or mentorship.

San Jose State University, a paltry few miles from the campus of Cisco, Zoom, and soon Google, barely has funding to keep the lights on for its Computer Science program, and has relatively large class sizes.

These big companies are reluctant to "water the tree that feeds them," for fear that it'll feed someone else instead.

 

Well, not all companies. We have an on-boarding department that lends their people to other teams in the company, until they found their sweet spot and hopefully stick around for longer.

 


I can remember when I first started lurking on dev.to, years ago - this place was a go to site for high quality guides, articles, and really interesting content from people who I came to follow on social media and respect their position within the industry.

I come here every day but now it just feels like dev.to is starting to become "just another" posting ground for anyone with a vague semblance of a question that could have easily been Googled, click-baity "The BEST 10 somethings cos I want to boost my social media follower numbers", and tiny snippetty articles that are only a few small paragraphs at best.

Maybe dev.to isn't the place for me anymore? But I would be interested to see if I am alone in my opinions or whether anyone has felt a change here.

Thanks

 

This is a good rant and part of the reason I became a moderator.

 

I don't think of Dev community as just about great articles or interesting content. For me what makes Dev.to successful is how it connects developers with each other in a way that makes it easy and fun for everyone to share their knowledge, opinions, and experiences.
I agree that there are some articles that need to be more improved, but on the other hand I think that many small articles are still useful and just enough to share ideas or to highlight on interesting new techniques or subjects.
Finally, I hope you change your mind :).

 

I was never super active, but as someone who despises what the modern web has become and works in a niche industry, I basically never find anything interesting here. I've long decided that dev.to is not a place for the kind of technical information that I need/want to consume, which is fine, there are plenty of places that are.

 
 

Interesting thoughts, as a DEV moderator this is something that we're actively trying to tackle. Take a look at the mod page also, you could become one yourself and help us with your insight:

dev.to/community-moderation

Also a thought is that curating your feed, followed and blocked tags can go a long way 😁 (and you can filter by top monthly, etc which is what I often to, which helps filter out some of the noise)

 

how can viewers filter on "experience level of post"? My feed (and random browsing) shows 99% low quality (and low experience level) content.

I'd say also following specific tags will help with this. Some tags are modded, others not as much. That might help.

 

I don't see many questions here, thinking about it. Maybe it's just how I have my feed configured.
I do see a lot of "10 ways to get more successunits" though.

 

Oh yes, this happens as soon as something get's more well known.

The problem isn't new, at first, the internet was full of accurate knowledge shared by a select few. Then everything turned to s**t as everyone had to start writing crappy article to prove that they know something.
Now, every article is being written by someone who has practically no experience in some.

Myself included. I'm writing an article about memory allocation in the human brain right now!!!!

 
 

I really really dislike battle/vs/face-off posts, like Framework X vs Y.

In my experience they are either clickbait or poorly researched.

I'm concerned that newer developers will jump on a hype train, feel like they have to take sides to stay ahead, or be turned off by the (fake) competition amongst peers.

 

Agreed. The only thing I like seeing are comparison posts about older frameworks vs newer (not bleeding edge) frameworks. Those help weigh the pros and cons vs upgrading and also let me know about whats new and should be used in future projects.

 

Yup! Comparison posts can be very helpful. The way Gartner or other businesses rate technologies in an objective way (or attempting to be objective) is good for anyone new to a category of products.

I think what's missing from these battle posts, like you said, are a fair pros/cons list.

You can tell someone doesn't really know or understand a technology if they only have good things to say about it... likewise if they only have bad things to say, it's probably going to be an anecdotal account.

 

That and the rush to adopt insert new library here
But it's so much better than insert library that does the same thing here.

Learning a new tool ? Why did you BEGIN your usage of it with ten plugins already installed ? Why can't you take some time to learn how the tool works, get familiar with the command AND THEN use plugins to mitigate some pitfalls that you have experienced and are impeding your work.

Everyone's onboarding should begin with a good read of "The Pragmatic Programmer".

 
 

Too many people confuse an automated build with practicing CI.

 
 

CI refers to Continuous Integration, the practice of everyone pulling and pushing in the same branch in order to ensure that all the code is always integrated into the latest state as explained in these links:
martinfowler.com/articles/continuo...
davefarley.net/?p=247

An automated build is when you use a task runner like Jenkins, Travis or CircleCI to automatically execute all the steps that are needed for your build instead of someone executing those by hand. A good example is ensuring the tests pass and then generating a Docker image and pushing it into the register.

And in summary...

Most people doing CI use builds, but not all people using builds are doing CI.

 
 

I think the fact it's called CI in nomenclature doesn't help 😦

 

The number of devs that are confused by CI/CD nomenclature is too damn high. Can't blame them at all tho. Since the number of references to CI/CD that... are not right... is also too damn high haha

 

Processes are virtual machines. Docker could be replaced with a .service file and Git. Kubernetes is more complicated than the Apollo program but still deploys the same web app we used to deploy before.

Why is everything so complicated for no apparent reason?

 

Why is everything so complicated for no apparent reason?

Talk to some big companies, and I mean big, where bin packing 100 processes onto giant VMs instead of 50 processes can yield enough savings to add multiple elite devs, and you'll start to see why.

That said, there's still no reason for the usability cliff. If I knew more about sociology, I might speculate that this kind of thing is far more ancient than any digital technology, and the complexity used as a way to maintain group boundaries and control of the direction of the technology, au la 2 Chronicles 23:6.

Most of these are drastically over complected, and haven't properly considered too many use cases beyond "we have 5 devs who can work on scaling this full time."

I consider Nomad the exception to this, but I'm bia$ed.

 

Why is everything so complicated for no apparent reason?

basically all modern IT world now

 
 

Have you tried using NixOS to manage systemd services? It's great! Huge fan myself.

 

I have not but it sounds interesting I'll definitely have a look!

Although on the professional side I've totally thrown the towel on having things that make sense and I'm more focused on having people run the bullshit for me. If I can find a simple way of running things in a managed Kubernetes I'll be perfectly happy to let my host run the crazy zoo :)

 

Funny story, I worked at a place that started up and managed docker containers using systemd😂😂

 
 

I have a strong love/hate relationship with many things about web development.

CSS is powerful and fairly good, and I've learned to like it, but I also really hate it:

  • It's super inconsistent.
  • NOTHING works how you would intuitively think it should. Or in other words, if you don't know CSS inside out, it's sometimes really difficult to do what you want and get pixel perfect stuff. Other technologies don't have this problem at all.

Other things have to do with browsers and CSS:

  • SASS has been out since 2006 but we've only recently been able to use things like CSS custom properties and such.
  • New features like flexbox and grid take a long time to be usable in production.

Standards in CSS: For some reason good programming standards like scope and not using globals all over the place are completely ignored in CSS.

No versioning for the web. Yes there are downsides to versioning, but I think the eternal backwards compatibility is very unfortunate because we can never fix design mistakes. Our only options are to only use "higher order languages" that hide those mistakes from us, or completely copy-paste functionality with new syntax and minor changes and just never use the "old way" of doing things.

JavaScript prototype system is bad. I have never, ever, had a use case that required me to use dynamic scoping for this. Having to use hard binding all the time for proper classes has only ever gotten in my way. It should have been completely hidden away in ES6 classes, without having to wait for the class properties proposal which copies functions everywhere.

 

😂 😐

Drivers are psychopaths. (This is from a UK perspective.)

Roads are for PEOPLE. Driving is a PRIVILEGE. If I'm cycling, using the full width of the lane I'm in, because for some UKNOWABLE reason there are potholes all over the roads so I'm trying not to fall into them, and you think you need to overtake me, use the full width of the road, like you would for a car. There's no need to toot your horn. EITHER it's safe for you to pass, so you don't need to warn me of your presence, OR it's not safe, so slow the [] down.

I've had drivers try to run me off the road. Someone tried to argue that maybe they didn't realise. DIDN'T REALISE? THAT'S WORSE YOU BUFFOON! If they didn't realise, then they are not safe to drive. Someone hit me once (very slowly, but none-the-less) while I was waiting at a junction, in broad daylight, and do you know his excuse? "Oh, sorry, I wasn't looking". DRIVERS are PSYCHOPATHS!

It does not make sense to me why people seem to accept driving as []ing inevitable. Commuters can [] off. Work from home, move closer to your job, get a job closer to where you live, GET THE []ING BUS. "Oh but public transport is terrible" drivers snivel. TELL YOUR LOCAL COUNCIL, don't endanger my life for your convenience.

I'm not completely without sympathy. I understand that some people have mobility issues, so a car really is essential, but the rest of you []s are damaging, polluting and generally dangerous.

 

I feel the same when walking to work and cyclists hammer down the pavement through the pedestrians. I've had a cyclist dismount and shout at me for being on the pavement telling me that the law here means I had to get out of his way.

Or when they jump red lights. Or when they cycle at night without head protection or lights.

Maybe it's not drivers you're thinking of, maybe it's whoever is in the dominant position at the time. People, eh.

 
 

I wasted eleven years coding, for fun, thinking that it was me, thinking that I loved it and now as I'm 3/4 to getting a bachelor's and have a job in programming I realize I hated it all along. But it wasn't the degree or job that made me hate it, that just accelerated my search to find out why I'm doing it to begin with, and I realized it's just not what I convinced myself it was.

 

To me that sounds like a burn out, not a wasted time. As you said it yourself, you enjoyed those 11 years coding on your own terms. Perhaps take a break from professional programming, so that you can find the old joy for coding again?

 

It was never really a burn out from professional programming. I don't have anything to say that is completely concrete, but I can elaborate the situation.

I believe I've crunched and been pretty critical on my experience in programming. It's been pretty casual and programming alone wasn't necessarily where I got my enjoyment from. For a healthy part of my time developing I was basically just perfecting my experience in one ide and one language that I could pretty much do everything I wanted to without much much frustration. I was invested in the mostly friction free experience and being able to create fun experiences and the fact that I could do everything mostly rapidly really fueled my prototyping/never finish a project habit. But I could see that I was making things all the time and get results quickly without much hassle. One day it just stopped working for me and I decided I will try to find a similar experience somewhere else. On that journey I found some small successes and something I was pretty proud of and made a cool thing out of but there were limitations with the entire toolkit in using it for everything. But it was a fun experience just playing around with tech and made me feel productive. It sparked my interest in learning dev environments, plenty of tools, several languages, and multiple ides and development stuff.

But I will attribute most of that to my behaviour and personality in searching for something that's novel and interesting instead of actual usefulness - which I found to be very limiting. Fast forward through all of my experience and looking back I know what I enjoyed and that I didn't enjoy. I enjoyed just messing around with cool language features and the search to find the perfect toolset.

I don't necessarily regret finding cool technologies, but I do regret a lot of the time wasted because of it. I didn't learn a lot of meaningful concepts and I was never disciplined enough to stay with anything. But I also wasn't convinced there was really anything worth committing too. And looking back after several years of tinkering, exploring, and learning - barely any of it was useful for where I'm most likely to enjoy the actual work I do that's meaningful. So it's very easy for me to look back and be cynical and angry about where I've wandered in programming because I was totally misguided and unplanned about all of it. Now I'm stuck thinking I'm supposed to be graduating and having some job in programming just because what I used to do required extensive logic - but what I was really invested in for the most part was just the fun of seeing cool and novel language features or being able to knockout a quick product prototype and satisfy a plethora of ideas.

So I can honestly still say there's a lot I hate about programming when it comes down to what I with was possible and more convenient and realizing how much time I've wasted looking for such a perfect solution and now understanding that I need come back to basically a limited few tools that actually do what I want.

Programming is fine, learning new languages is fine, but there's a very very strict focus and use for programming in terms of application I will ever really enjoy and only one is productive for me.

I'm also just as easily upset not realizing earlier where to have put most of my energy with all this but everything is clearer in retrospect and I try to find the positives in where I've spent my time. At least I understand my position now and can readjust how I spend my time programming and actually enjoying some of it. But that spark which originally got me in probably won't ever be the same, but it doesn't mean I can't enjoy it at least a little now.

edit-

Also, I just wanted to explain that there's a lot about programming in general that frustrates me and makes me dislike it. I've read way into it, but lots of the smaller picture stuff has really gotten to me. It's all of the small details about what makes development so meticulous that's really a burning factor for why I don't enjoy programming by itself. Making and working on projects as they get bigger or on certain deadlines kills the joy of experimentation and making code nicer. Working with bad code is a chore. Figuring out deceptive bugs and database related stuff is a major pain-point. But also just trying refactor code bases, grow code bases, all of the theory in software development about scalable and good looking code bases - there's just too much that goes into development to really capture it all. So programming can be enjoyable to me. But the entire process in the end is more of a pain to the art for me than anything. Porting code, protecting code, optimizations, refactoring, all of it are a part you can't get away from at some point and those are the things I hate. The limited subset of programming have a much smaller audience to get hold of, or no audience at all -- essentially the equivalence of doodling in code but the kinds of doodle's only the creator can look at and enjoy... not typically something or a skill you would be able to sell unless you made it your goal. So yeah, coding as a past-time and for the sake of "doodling" is where I'll say I enjoy it. Not even necessarily "making cool things or things at all", but just being able to see something come together and call it good.

But hey, there will always come a time where I can take a doodle and turn it into something more valuable if I find the effort worth it. But that hasn't been my goal or intentions until recently. Which I plan on making more of a conscious effort since the reality of wanting to find some meaning in my work beyond a doodle needs to be realized.

 

Lot's of people start coding because they go study it, only to find out that coding isn't fun. It's always frustrating. That's why there are so many broken Mac keyboards out there!!

 

This is all I see today, its pathetic

The worst part is when you call out the BS in the comments and get a warning from the Dev.to moderation team because you're not being nice to the author or respecting their right to shitpost.

It's like Medium but without a paywall and people are extra sensitive about authors' feelings.

Yes. You can get around it by browsing incognito, though.

Huh. I've never hit it. All I ever get is the "Pardon the interruption, but we've seen you before. Get an account." screen that can be closed.

 

How some companies expect you to jump through hoops and do interview processes set up like google/facebook/etc with the complexity on par with those companies but don't offer salary/benefits packages equal to them.

Also, online tests that have nothing to do with the functions within the company. It's better to set up tests that are part of what we'll be doing everyday.

Finally, I need a haircut but everything is closed :(

 

Recruitment processes at some companies are terrible. Then they wonder why the same position stays open for years. They claim a lack of developers out there.
BS. You just don't know a good one when it smacks you in the face!

PS. Not only my own experience here, I've been researching this.

 
 

I hate that many developers are talking about Clean Code, clear naming etc. and when it comes to executing some practices and principles they fail.

Like: "Hey you should change this. It makes the code complicated, please rename X or change structure to Y" -> "I will do later". When later starts?

Why do so many believe that "working code" is enough. I'm working with a 4y old React App and it has some much outdated stuff and still when a new PR comes in and I see wrong patterns used, tight-coupling, hearing "we do it later in a tech debt sprint" it's super hard to response calmly.

So: "Later equals never". And I hate to hear "later" too often...

 

People who call themselves developers but can't show a portfolio. There are a lot of these people in my country. If I had the change, i would like to meet them in person and ask them to print hello world on a piece of paper.

 

All my work belongs to my employer, so I'd have to hustle on my own time to get a portfolio up. My own rant would be that it's not a reasonable expectation that everyone should code in their spare time.

 
 

I can't show a portfolio. If you asked me to print hello world on a piece of paper I'd open a text editor, type "hello world" and hit print.

 

Ahah before DEV I had zero publicly available code to show so I think this is pretty common for backend developers. There's no code or apps you can show.

 

Don't worry everyone, it's just from where I'm from.

I have a group of over 1000 freelancers and about 15% say they're devs but can't show a portfolio or a past work that they've done.

No Pun Intended.

 

It drives me crazy when people bash and complain about free/open-source frameworks. There were recent posts deriding Material Design and those that use it, but it has many open-source implementations that are free to use and Google isn't mandating it. The same derision was true with bootstrap for many years.

It takes a lot of effort and time to support these frameworks and make them freely available for developers. It is up to everyone if they want to use them and in many cases, they are far better than what individual developers could/would design themselves.

 

I know the article your talking about. I have used vuetify (md component framework for Vue) a few times. It's invaluable for someone like me who had zero eye for design. I really appreciate all the hard work on things like this. I just don't get the hate.

 

Babel is too difficult to configure to be so popular. I wanted to try configuring it from the docs on a new project. Had issues with class syntax, private member variables, then async/await. Cryptic errors that give no hint at the actual problem, a couple hours of googling. No success.

Finally I just scrapped it and rewrote the whole thing in typescript. Setup and refactoring still took less some than trying to trouble shoot Babel.

Good tools should simplify your workflow, not frustrate it ( and me ). When there are tools whose only function is to wrap your tool to make configuration easier, your tool is too difficult to configure.

All that said, I really appreciate that Babel exists. I'll continue to use it in projects where the cli does the setup for me. /rant

 

Women developers not being treated seriously. The field is already bad enough for them as it is. My graduating class saw many girls changing majors from CS/ Applied Computational Math majors. At work, women were mostly in non-technical positions and even the ones in software teams were mostly expected to be good at design and aesthetics.

The ones who did survive the entire brutal ecosystem from day 0 way back in Uni all the way to being a mature developers capable of building mission critical systems would still not easily get opportunities to lead their teams as the architect/senior devs. It was easier for a new guy like me to surpass them as opposed to other guy tech dinosaurs at work. It was not the case everywhere I worked though and I certainly don't want to point out which ones were different. Some teams just were total sausage fests. As is the norm.

After having left full time employment, I was recently talking to a female friend who is an Ionic dev but always interested in reading/learning other tech stacks. She is also not finding a level playing field because of gender biases and is likely to be relegated as a UI developer as opposed to other more technical things she is passionate about. Best thing possible would be her getting promoted to a semi-technical project manager instead of a technical lead despite her years of experience.

 

Lol. Tech in general can get me going on a good rant.

 
 

The control button placement on a ThinkPad laptop. It has happened to me a million times that I wanted to press control but ended up pressing the fn key on a ThinkPad. It's an abomination. Especially since ThinkPad has one of the best keyboards on a laptop

 

Code worship is the greatest mistake in the software industry.

 

The interview process for developers is so unbelievably broken.

What does being able to implement a binary search tree under time pressure (while someone is watching you!) prove in relation to what you're actually going to be doing day-to-day in a development role?

I started applying to new jobs a few months ago because of various issues at my current company but ended up getting rejected by all the companies I applied to (or they went into a hiring freeze due to COVID-19). I don't typically get impostor syndrome, but only getting a bunch of rejections seems to be the one trigger for me.

As many problems as I have with my current employer, I am aware that I am extremely fortunate to still have a job in the current state of the world.

 

The amount of tools and tech that are “necessary” to produce software “cloud natively” is absurdly overwhelming and unmanageable.

Counterpoint: learning to use all of those tools is very fun, but that is not an excuse.

 

Others also have mentioned, content quality on dev.to is really really degraded over the time. There are more posts written by wanna-be-coders (who uses no-code/low-code tools to build projects) rather than "experienced" programmers. And when you put a question in front of those wanna-be-coders they can't answer with confidence, why? because they followed another tutorial to write this tutorial.

I was happy when I found out about this dedicated platform for devs because medium was too generic but now I regret that. Let's put it this way, dev.to instead of becoming more like reddit became like Quora.
Maybe listen more to users instead of investors.

 

In Germany Covid-19 went off the grid, when a bunch of 50 idiots celebrated carnival sitting at a table passing a carrot from mouth to mouth. A couple of these 50 had the virus without knowing. Because carnival is such a big thing in the region. Infection numbers fired up.

And now i can't play football anymore. What is the right thing to do, given that my oldest team-mate is 72 and a bunch of us have pre-existing conditions already.

How should I relief my stress from programming all day?

 

The inability for a lot of developers, both fresh out of college and with years of experience, being completely unwilling to challenge their preexisting beliefs about this field and try something new with an open mind.

 

Sitting almost 24/7 since the quarentine begun at my country, I can't enjoy playing at my PC at this moment, rather prefer going to listen music at the rooftop. I need being outside

I'm mad because I always enjoy playing games but since i'm almost sitting coding im tired of being here 😢

 
 

Nothing to do with coding.

But South African taxis, even in times of lock down, where you're not supposed to travel.
You're only allowed one person in a car over here, but I saw 5 taxis drive passed my house, fully loaded to capacity of 18 people, all basically sitting on top of one another.
What the hell is Corona anyways, is like a funny tasting beer right.

Mind blown at people's stupidity.

 

A recent one: dev.to/coreyoconnor/request-per-se...

A bit of a short rant, and not presented clearly. But seeing teams focus myopically on requests/sec is definitely grinding my gears :D Only a little bit tho, it's still good fun.

 

Nothing actually I've been enjoying staying at home.

 

Do not hire "lead" developers, call them part of "leadership", require them to come to all "leadership meetings", but then also not let them lead in any way OR listen to any advice they have given and then hold them accountable as "lead" when it fails.

Why hire a "lead" if you just wanted a code monkey to scapegoat AHHHH

 

I won't, because I do not resort to physical violence, especially in the case that the person that will be hurt, is the one asking for it, if there is something you need to say, consider getting a therapist.

 
 
 

When vocalizing URLs: NEVER say "backslash". IT'S A FORWARD SLASH, PEOPLE!

 

I will never understand where this comes from. Like, who was the first person to say "backslash" and what did they think a forward slash looked like!?

 

When a job application requires your resume, then asks you to enter the same information (education, skills, etc) in a separate form even though that info can be found on your resume. 😕

 
 

"Why You Should Learn insert completely new framework/library/language/whatever in 2020"

Mate, I just started to learn React ;-;

 

world moves so fast that my job that I devote all my time for that will be useless in 30 years

 

Do you want a problem solver on the computer or a super magician (reading a book) in the white board test?

 

Was about to buy a MacBook Pro 16 and with all this global financial crisis my country’s money went bananas.
Now all the money I saved for 2 years worth nothing.

 

I keep forgetting that katex division tags are supposed to be like \frac{number}{another number}

 
 
 
 

The EARNIT ACT! Can we talk about it already!?

Classic DEV Post from Jul 27 '19

If You Don't Know, Now You Know - GitHub Is Restricting Access For Users From Iran And A Few Other Embargoed Countries

Please help our cause against modern-day discrimination

Ben Halpern profile image
A Canadian software developer who thinks he’s funny. He/Him.