cutenode / 1x.engineer Goto Github PK

Background: I really love being a 1x.engineer! It's awesome, it's heartwarming and it boosted my confidence.

I decided to re-imagine and remaster the looks of 1x.engineer website. Though that the build system I chose was different and required a build environment, I decided to publish my proposal in another repo, so maybe we could discuss the new design and even merge it with the current repo. 😄

My version repo is under par6n/new-1x.engineer and you can see it deployed on Vercel.

What I offer by this version:

• An option for switching between light mode and dark mode (addresses #126)
• Improved typography (I used Inconsolata to keep loyal to "Fancy mode", though)
• Potential to add cooler things (Initialized the project using Parcel)
• Minified and purged useless CSS rules, thanks to TailwindCSS

Though, I do not intend to belittle the fantastic work of the awesome contributors to this project. 🙏 It's merely a suggestion from a newcomer 1x engineer. 🙂

I think this this similar to docs - some people do, and some don't. What does everyone think?

User story

As a 1xEngineer I would like to signal my 1x-ness to the world in t-shirt form, to normalise 1x > 10x.

Kind regards,
Kathy

I would love to have this document expressed in multiple languages.

Move to a more stable or remove link.

As a 0.1x engineer, I would appreciate a place to point people at to inform them about this underrepresented breed of engineers. https://0.1x.engineer/ would be perfect for that. ;)

Thank you for creating 1x.engineer.

Maybe we can install a let's encrypt (SSL) certificate. My bad it is already installed.

Need to redirect http://1x.engineer to https://1x.engineer.

1x.engineer can always be trusted.

It would be helpful to those who resonate with this project to be able to link to specific versions. That way they can have reviewed what the list says at that time, be able to say so in some public form, "yep, this is me!" and move on without fear that it will change in the future to say something they are against. For example, someone may read the list as it stands today, and then plop the 1x.engineer link somewhere on a public facing social network profile, proclaiming, "yep, this is me!" and then come back several years later and realize there are things they strongly disagree with that have made its way onto the list.

Everyone loves a dark mode. Should persist between themes.

There's a typo on the last line riddicule -> ridicule

&emdhash does not seem to turn into a character.

Also, I think this particular statement defeats the purpose of what you trying to accomplish.

It might be better to say that when a bug happens that the engineer is not belittled, berated, or fired by people who don't really lift a finger to do all the work. Or, something along those lines.

Otherwise, such an engineer should avoid bugs by appropriately planning, documenting, and testing code.

I got kicked off a Google project last fall because GitHub expanded my one-line commit into three lines. Prior to that little GitHub trouble, I really did save the project by throwing away a weekend and fixing a bug that was troubling their deepest pocket customers. I did that earlier in the summer. I worked all weekend OK. I spent a bunch of that time in a coffee shop in Santa Cruz. But, the customer was threatening to end the project the next Tuesday. So, the bug was fixed by Monday.

(I was thinking of fixing the commit message on the next morning - a process that takes about an hour if you don't clone the repository - but, the guy fired off letters to managers with screenshots and everything before I could address it. The guy was out for blood. And, Google managers gave it to him.)

Later, the guys who got ahold of the project changed all the permissions on GitHub to make it difficult to commit changes. They very pointedly reminded me that programming these days is about "getting along with people". But, that seemed to mean that the people had to come from the same town in India and perhaps attended the same school as the guys who took on the task of scolding me and playing around with the permissions. Also, it seemed to mean that all the work went to Bombay and that I was not supposed to do any real work but write their tests and fix up their test harnesses. And, I did that. I even went out of my way to give credit to guys who didn't get their work done to make the tests run on Travis and cover all the code that was supposed to be covered.

(Why not just clone the repository? I did not get time to. Also, I had not gone down the road of the closed of permissions with the repository forking. What if I killed my repository and no longer had permission to clone? I just didn't have that fact handy. But, Bombay guys were certainly the kind of guys who get pleasure in making it so that someone outside of their club would lose their workflow forever.)

Since the guys from Bombay wanted a great work-life balance it meant that if they wrote buggy code at a very slow pace, then that code was good. But, if I busted my butt to write good code, leave in comments, and write tests, then that code was really bad. So, where was my work-life balance?

It all was seasoned by managers, Americans, from Colorado who are the kind of guys who like to do the meetings and make project rules and still have ample time for their ball games. Since they are so cool and have such great work-life balance, they did not have to take time to really understand the project and if the GitHub rules caused some trouble -- well, that was SOME trouble. Truly the Colorado guys were way more into their ball game than into working projects. But, maybe that is a great work-life balance, right?

So, you see I like 1x. But, I don't like it when it means that people can be prejudiced, agist, and lazy. And, then the group of guys can fire people who are too in the way of their great plans, whatever those are. Maybe it's to keep a job while staying drunk or to climb the ladder or be the biggest bigot in the room.

Why the one-line commits? I got from another American, who was fired by the same guys, that it had to do with giving credit to the Bombay guys while masking the work of other people. The managers just look at the commits and see how many and who did them. That is their measure of performance. So, allowing Americans one-line commits that say something wimpy while allowing their Bombay friends many little commits over pointless details all called out in grandiose language fits the bill.

Since I left, I have seen commit messages for changing spaces in log messages. And, I have seen bug reports indicating memory leaks, broken installations, destroyed Docker containers, and more. Also, they wrecked the security mechanisms by exposing keys and secrets all the while saying that they have enhanced security.

So, they have great high paying jobs, great work-life balance. And, now my work-life balance is great, too. I don't have a job and I am on unemployment.

I was thinking there might be a 5x programmer. Something in between the extremes.

But, a lot of 1x stuff is good.

There needs to be something about creating a plan for coding, designing algorithms ahead of coding, etc. I have been forced too many times to just start writing code. Managers think that they are hot-shots and that a programmer's life is something that can be pushed around with trial and error.

First off - love the site!

I noticed the headers (on fancy style) looked a bit blurry in Chrome on macOS, so was going to open a PR just to add -webkit-font-smoothing: none;, then thought about adding it to the body selector instead of h1/h2/etc., but since it's subjective, maybe you like as-is!

Take a look at the below screenshots (probably need to click thru to see the differences clearly) and let me know if you'd like a PR for either of the two changes?

Cheers!

As-is:

-webkit-font-smoothing: none; applied to <body>:

-webkit-font-smoothing: none; applied to <h1>/<h2>:

This is entirely subjective but I find the site's font difficult to read. It seems a bit too wide for comfort.

Might just be me :)

See title

Maybe this is by design - but the black & white mode with the "Press Start 2P" font seems to be would be considered "Simple Style" while the colored background and header text would be considered fancy. If I'm wrong let me know!

When I'm on black & white mode, the button says "switch to simple style", but am I already on simple style? Am I not trying to switch to fancy style?

The website uses an svg as background image, as noticed on other projects with the same feature, it renders slowly on ultrawide monitors (mine is 2650x1080), and makes user experience less useful.

Altough the website doesn't need to be 100% performant since there's no vital app running, I decided to let the feedback registered as an issue if there's interest on people to contribute on a easy problem to fix:

Maybe it's just me, but this comes across as sour grapes. A 10x engineer, if such exist, is ten times more productive than a 1x engineer. By definition.

Nothing else can be said about 10x vs. 1x engineers. All of the qualities you list for the 1x engineer here can apply equally to the 10x engineer, except the 10x engineer is ten times more productive. Again, by definition.

I've met easily a hundred 1x devs in my career, and a great many of them:

• Don't give credit, due or not
• Don't create community or share knowledge (many are trolls)
• Work way too many hours and still only produce 1x or less
• Have no concept of healthy balances of any kind
• Have no arbitrary contribution scores so can't be measured by them, possibly deliberately
• Write unreadable code; hell, write complete garbage code shamelessly
• Almost never read the docs and certainly never write or update them
• Regularly brag about how much they know despite being sublimely ignorant (see Dunning-Kruger)
• Can't be arsed to help teammates or celebrate their "wins"
• Can't be bothered to ask questions
• Snark on code reviews (and are often wrong) and try to avoid them for their own code
• Are passive-aggressive little shits who make everyone around them hate work
• Never admit when they're wrong
• Think that they are 10x engineers

And on and on and on. Everyone has met these coders and simple arithmetic shows that almost all of them are 1x or 1x- coders.

I think that you may be confusing 10x coders (and I doubt that you've ever met even one) with assholes, of which there is a surplus, as this repo shows.

The people I've met who were close to 10x coders have generally been the kindest and most helpful of coworkers, always ready to lend a hand or to mentor others. And guess what! They have the time to do so because they get their work done so quickly and without fuss or excuses.

But as Dunning-Kruger predicted (and didn't go nearly far enough), fools rarely know they are fools and so they trumpet their foolishness as if it were wisdom. It's embarrassing, but what can you do?

Would it be possible to add the 1x programmer meme, namely the dog part, so that when tempted to multiply him/her self by 10, quickly remembers how most of us really feel most of the time? (bipolar)

There is a known bug in the following line:

<li>Writes code that &emdash; gasp &emdash; has bugs</li>

This bug will not be resolved. It wasn't intentional, but due to overwhelming demand (1 tweet) the fix was reverted in 3fac25b.

This issue will remain permanently open and labeled as wontfix.

The last point on the list reads

Has a favorite editor, browser, and operating system, but realizes others do too.

so it feels unnecessary to be very prescriptive regarding how to search for information on the internet in the first point

Searches Google when they're not sure what's up.

One could use duckduckgo, check in a forum or IRC, etc.