- you don't like math
- you don't like study
- you don't read documentation
- you throw out the manual
- you like to punch a clock
- you dislike books and reading
- you don't ever work more than 8 hours
- you can't tolerate the occasional weekend work day
- you fold under pressure
- you aren't good at crunch time
- you can't do on-call without committing seppuku
- you don't have attention to detail
- you aren't interested in technology
- you're not good at explaining things
- you can't deal with change
- you're not excited by the prospect of extreme variety
- you don't have the ability to focus
- you can't deal with ego without resorting to violence
- you can't deal with someone calling your baby ugly
- you can't discriminate between fact and opinion

And many, many more

I really like the attention to detail Microsoft has put in their websites, they've replicated every aspect of Windows.
Not only the loading animations, the style of the UI, but also the random freezes and crashes.

I often want to scream at co-workers because of their lack of attention to details.

I believe attention to detail is important for software engineers.

I tell my junior developers that "it works" isn't enough, you need to make sure it works as perfectly as possible and paying attention to detail helps with that.

So today I got an email about a job opportunity. The email was in romainian. This is the exact translation and bear in mind that in romanian as in every other language (I guess) alot of english phrases sound very cringy. This is the email:

We need a fearless hero for the IT realm!
X company, a thriving insurance community, is looking for a real hero of software development that can make code using the .NET mystical hammer that can only be lifted by a worthy, deserving and responsible warrior.

You can't fly? Can't shoot lasers? You are not wasting your night time by looking at the moon on tall blocks wearing a cape? Then you could be the hero we need.

Do not worry, the position does not imply superhuman strength :)) However, it requires intellectual strength and attention to detail. You can even use your powers from a comfortable chair in a welcoming team full of other heroes ready to help you. We won't leave you alone, after all even Batman has Robin :))

I have attached all the information you need. Only The Chosen One can open the document so you will know immediately if you are right. :))

If you want to be responsible with your strength, then I'm waiting for your updated English resume with all your heroic deeds in the past.

Remember, not all heroes wear capes!

... WHAT THE FUCK IS .NET MYSTICAL HAMMER??? AND WHO THE FUCK USES ":))" IN AN EMAIL??

I work for a web agency.
Over the last 18 months a company asked us about 5 different quotes for rather minimal changes to their website.
While being minimal changes, estimating costs for them still requires several hours of work for research, meetings, correspondance and writing the damn things. They never even gave us a response (neither positive nor negative), except once where they told us that they wouldn't pay for project management because their instructions are so clear that PM isn't necessary.

As a response to the last one, after several months, they send us a 10 pages long pdf with requirements for a new website (or a "restyle" like they call it, even if it has absolutely nothing in common with the current one).
We inform them that we can't permit ourselves to continue studying new solutions for free and therefore tell them that a detailed offer would cost them something like 300$, and that amount would then be discounted from the eventually accepted job. We also roughly estimate a price range of about 15k - 20k for the new website.

We get an email back, from the CEO (until now it was a secretary), with essentially 3 arguments written in condescending form:
1. he brags about his revenue being over 9 billion $$$ a year, and that being a part of a global holding for which "communication is essential" (sic.) means that they need to coordinate and "can't simply accept an offer" [even if it's 400$, for specific change exactly requested by them, I guess...]

2. 15k is too much [... for the website representing this 9 billion dollar holding on the internet, for which the requirements are written in the 10 pages long pdf]

3. He asks for a meeting

We accept the meeting, we go to their office.

When we arrive there, the secretary informs us that the CEO will not participate. So we talk the her and the head of the "Communication Dept" in videoconference.
I explain them that if the sum, which we thought would be appropriate (~15 - 20k), is too high, the Pareto principle would allow us to, theoretically, achieve about 80% of the features and quality for about 20% of the cost. Their genuine response is:
"So your estimate was wrong! You can do it for much less!".
I try to explain them that the most money in a project goes into "attention to detail".
The "Communication Dept." person, who is "doing this job since too much time" (sic.), refuses to believe and insists that "details" don't exist on the web.
I tell her: "In any kind of work, the more effort you put into something, the better it tends to get, with diminishing returns".
She insists: "I don't understand this".

So now I'm here, doing the 6th offer, free of charge, for a 5k website, for a company that generates 9kkk revenue each year, trying to define a "Definition of Done" that works out.

FML I guess.

Sorry for the long post.

Dear Client,

You said it was of paramount importance that this software work flawlessly. I've worked hard to make it so, even when your indecision and lack of attention to detail indicate you don't care as much as you say and have made the project late.

Yesterday when I handed you a step-by-step user acceptance test plan, you delegated it to someone not as familiar with your specific requirements. You said you don't have time for such things.

I will remind you of those words when the project launches and you find something you dislike.

Sincerely,
Me

Most painful code error you've made?

More than I probably care to count.

One in particular where I was asked to integrate our code and converted the wrong value..ex

The correct code was supposed to be ...

var serviceBusMessage = new Message() {ID = dto.InvoiceId ...}

but I wrote ..

var serviceBusMessage = new Message() {ID = dto.OrderId ...}

At the time of the message bus event, the dto.OrderId is zero (it's set after a successful credit card transaction in another process)

Because of a 'true up' job that occurs at EOD, the issue went unnoticed for weeks. One day the credit card system went down and thousands of invoices needed to be re-processed, but seemed to be 'stuck', and 'John' was tasked to investigate, found the issue, and traced back to the code changes.

John: "There is a bug in the event bus, looks like you used the wrong key and all the keys are zero."
Me: "Oh crap, I made that change weeks ago. No one noticed?"
John: "Nah, its not a big deal. The true-up job cleans up anything we missed and in the rare event the credit card system goes down, like now. No worries, I can fix the data and the code."
<about an hour later I'm called into a meeting>
Mgr1: "We're following up on the credit card outage earlier. You made the code changes that prevented the cards from reprocessing?"
Me: "Yes, it was my screw up."
Mgr1: "Why wasn't there a code review? It should have caught this mistake."
Mgr2: "All code that is deployed is reviewed. 'Tom' performed the review."
Mgr1: "Tom, why didn't you catch that mistake."
Tom: "I don't know, that code is over 5 years old written by someone else. I assumed it was correct."
Mgr1: "Aren't there unit tests? Integration tests?"
Tom: "Oh yea, and passed them all. In the scenario, the original developers probably never thought the wrong ID would be passed."
Mgr1: "What are you going to do so this never happens again?"
Tom: "Its an easy addition to the tests. Should only take 5 minutes."
Mgr1: "No, what are *you* going to do so this never happens again?"
Me: "It was my mistake, I need to do a better job in paying attention. I knew what value was supposed to passed, but I screwed up."
Mgr2: "No harm no foul. We didn't lose any money and no customer was negativity affected. Credit card system may go down once, or twice a year? Nothing to lose sleep over. Thanks guys."

A week later Mgr1 fires Tom.

I feel/felt like a total d-bag.

Talking to 'John' later about it, turns out Tom's attention to detail and 'passion' was lacking in other areas. Understandable since he has 2 kids + one with special-needs, and in the middle of a divorce, taking most/all of his vacation+sick time (which 'Mgr1' dislikes people taking more than a few days off, that's another story) and 'Mgr1' didn't like Tom's lack of work ethic (felt he needed to leave his problems at home). The outage and the 'lack of due diligence' was the last straw.

The people. I find devs to be (obvious generalization) prone to: not take criticism, not understand the difference between fact and opinion, not understanding that it is perfectly acceptable to change your point of view when presented with new information that will conflict with what you currently believe in. It is a sausage fest brought to you by eons of very fragile male ego in the making, and many other qualities that were very much diluted in a lot of the other fields I have worked on: from retail (shitfest) to import/export all the way to military (another shitfest, for different and rather dangerous reasons).

I have met some amazing people in the field, don't get me wrong, but the quirkiest of mfkers i have met make me believe that maybe I AM the one that does not belong in the field (top kek).

On a more technical side, basic stuff like reading comprehension, attention to detail, the ability to translate complex problemd to pieces and that interconnect among the themselves, the ability to understand the grand mathematical scheme of things, the ability to be patient and despite what the above generalization would have you believe...the ability to communicate with other humans with tact and understanding as well as a spirit of collaboration, etc etc, are definitive traits to consider if you want a career in software development that leads above just being a code monkey.

Shit like that.

Small company, sole engineer. Non-tech management. Increasingly fancy job titles despite working alone most of the time, with the promise of hiring someone (again) I can actually manage soon.

Backlog of projects/tasks is truly a mindfuck, with new things being added each week. This backlog will never ever get done, and nothing matters anyway because the next idea is "the future", all the time.

While I have influence on some aspects of decision making, it usually ends up being what the boss wants. Actively opposed a project because it's just too big of an undertaking, it was forced through anyway. I'm trying to keep the scope manageable as I'm building it now, and it's hard.

"It's the future, we absolutely have to do this. It will be the biggest thing we've ever done."

Boss's excitement then quickly faded since it's actually in development, now nobody really seems to want to know where it's at, or how it will all work. I need to scope it out, with the knowledge that many decisions boss signed off will be questioned when he actually looks at it. We now have even more "exciting" ideas of utter grandeur. Stuff that I can't even begin to comprehend the complexity of, while struggling to keep a self imposed deadline on the current one.

Every single morning we sit on Zoom for a "valuable" "catch-up". This is absolutely perfect for one thing: Completely destroying whatever drive and focus I have going into the day. Unrelated topics, marketing conversations, even more ideas, ideas for ideas sake, small problems blown out of proportion, the list goes on. I recently argued in detail why it should be scrapped or at least be optional to attend. No luck, it's "valuable".

Today a new idea was announced, and we absolutely have to do it ASAP because it can only be better than the current solution. I raise my concerns, saying it's not as easy as you make it out to be, we should properly think about it. Nope! We'll botch something to prove that it works... So you'll base your decision whether it's good on some half ass botch job that nobody really has the mental capacity to actually pay attention to. What a reliable way to measure!

"Our analytics data isn't useful enough to tell us the impact of things we do. We (you) have to fix this." Over the last 2 or so years, I've been pushing for an overhaul and expansion of our data analysis capabilities for exactly this reason. Integrating different data sources into a unified solution so we can easily see what we're doing, etc. Nope, never happened.

The new project idea which is based on wild assumptions is ALWAYS more important than the groundwork.

Now when I mentioned that this is what I wanted to do all along, it got brushed aside. "We don't need to do anything complicated, just fix this, add that, and it's done. It should be an easy thing to do. This is very important for our decision making." Fine, have it your way.

I'm officially burned out. It's so fucking hard to get myself to focus on my work for more than an hour or two. I started a side project, and even that effort is falling victim to my day-job-induced apathy.

I'm tempted to hand in my resignation without another offer on the table. I just need time to rediscover my passion, and go job hunting from that position, instead of the utter desperation of right now.

If you've read through all this rambling, kudos to you!

How the Common Lisp Community will eventually die soon:

Clojure is the only main Lisp dialect having some sort of heavy presence in today's modern development world. Yes, I am aware of other(if not all) environments in which Lisp or a dialect of it is being used for multiple things, CADLisp, Guile Scheme, Racket, etc etc whatever. I know.

Not only is Clojure present in the JVM(I give 0 fucks about whether you like it or not also) but also has compilation targets for Javascript via Clojurescript. This means that i can effectively target backend server operations, damn near everything inside of the JVM and also the browser.
Yet, there is no real point in using Lisp or Clojure other than for pure academic endeavours, for which it is not even a pure functional programming language, you would be better served learning something else if you want true functional purity. But also because examples for one of the major areas in software development, mainly web, are really lacking, like, lacking bad, as in, so bad most examples are few in between and there is no interest in making it target complete beginners or anything of the like.

But my biggest fucking gripe with Lisp as a whole, specifically Common Lisp, is how monstrously outdated the documentation you can find available for it is.

Say for example, aesthetics, these play a large role, a developer(web mostly) used to the attention to detail placed by the Rails community, the Laravel community, django, etc etc would find on documentation that came straight from the 90s. There is no passion for design, no attention to detail, it makes it look hacky and abandoned. Everything in Lisp looks so severely abandoned for which the most abundant pool of resources are not even made present on a fully general purpose language constrained as a scripting environment for a text editor: Emacs with Emacs Lisp which I reckon is about the most used Lisp dialect in the planet, even more so than Clojure or Common Lisp.

I just want the language to be made popular again y'know? To have a killer app or framework for it much like there is Rails for Ruby, Phoenix for Elixir, etc etc. But unless I get some serious hacking done to bring about the level of maturity of those frameworks(which I won't nor I believe I can) then it will always remain a niche language with funny syntax.

To be honest I am phasing away my use of Clojure in place of Pharo. I just hate seeing how much the Lisp community does in an effort to keep shit as obscure and far away from the reach of new developers as possible. I also DESPISE reading other Lisp developer's code. Far too fucking dense and clever for anyone other than the original developer to read and add to. The idea that Lisp allows for read only code is far too real man.

Lisp has been DED for a while, and the zombies that remain will soon disappear because the community was too busy playing circle jerks for anything real to be done with it. Even as the original language of AI it has been severely outshined by the likes of Python, R and Scala, shit, even Javascript has more presence in AI than Lisp does now a days.

I think the sleep deprived me is finally cracking under the weight of incompetent assholes.

We just launched a major project in some weird cocktail of Agile slapped with MVP and release to the wild in a waterfall, but it was premature, premature in the sense QA hasn't even finished their side of things, but because some fuck with with "manager" in their title decided they have burnt through the budget with incompetence and scrapped an entire element of the project and outsourced just so they could make a shittier version that doesn't even fucking work.

How hard do you want to fail before you will start listening to the people that now have to work around the fucking clock to clean up this horse shit of a mess.

I'm literally arguing over field mapping with multiple 3rd parties, when the fucking requirements state WTF this is suppose to look like. All because they didn't validate or test their own shit.

Why is EVERY FUCKING cock head in this industry a waste of space and cash! Is it really to much to ask for 1 fucking project to fucking go live that actually fucking works where I don't need to work 2 weeks straight (including weekends) after going live just to be sure that what shit does hit the fan isn't going to create a SEV 1 issue...

Sorry, I'm pissed at the incompetence of others I need to deal with on a daily basis. It's not like this field is insanely hard. A little attention to detail and self validation, verification goes a long way. But clearly that's a rarity.

Once this shit is stable and actually works, I'll be pulling out the mop to clean up half this shit just so it actually works.

Oof, I'm getting to old for this bullshit.

"I really like looking at design and thinking: that attention to detail must have taken absolutely ages." - Si Scott

Monday morning client meetings are usually a pain. If they're not delayed once, they're delayed twice, and they go on for hours, taking up the entire morning for everyone on the project.

To make today even better, it was about an hour of our client ripping into us developers on the project, and the application we're making, to shreds, saying that we have a lack of attention to detail and are working well.
(not bearing in mind, we're building a hybrid application, so it's a glorified web page and we can't test on every android phone, or iOS device and any combination of keyboards for those in between, and every problem comes with its own quirks when you're forcing things with html, js and angularjs).

I feel back for the pm, she had literally 5 more hours of salty, salty calls with our other poc about the issues raised and how we could go about fixing all these minor issues, since they know the solution to them, despite having little to zero technical knowledge.

Just another day in the office I guess.

Just realized that the scroll position indicator dances when scrolling through a long list of comments 😄, and I think that's beautiful

I just need to vent about how frustrating and terrible Windows is.

It almost seems like consistentsy and attention to detail are completely foreign concepts to Microsoft. Everything from simple text selection (WHY DOES A DOUBLE CLICK INCLUDE THE TRAILING SPACE) to using advanced software feels like a chore.

Any sympathizers here? What problems do you need to vent about when trying to navigate your OS?

FWI I'm not a Mac or Linux user, so I have the joy of using Windows at home. I wish I could switch, but I prefer full access to my Steam library so I'm stuck with this option.

Reasons to NOT be a dev sounds rather negative so I'd like to propose 3 things that you need to BE a dev as to frame it in a positive light:

- When a problem peaks your interest you want to solve it, you may even be obsessed by it.
- You enjoy learning, not necessarily enjoy school, just enjoy learning new things (even better if it's by your own means)
- Failure may get you down, but you learn and don't give up until you have exhausted all paths to success.

You may need other skills like math, logic and reasoning abilities, being able to handle deadlines, attention to detail, and cope with stress. I've seen people being crap at all of those and if they have the former 3 they, in time, will hone the others enough to make them a productive dev.

No need to be a 9-9-6 code monkey willing to be squeezed by Big Corp for massive profits and a low salary or a 1337 purist coder that only focuses on the crafting side of developing software. That may make you a great coder but not a well rounded developer or individual. Remember, you program machines but you are NOT one.

Halt and Catch Fire is having another great season. Lived those days and it is so true. CompuServe, Compaq, Commodore, 5 1/4", Tandy 1000, Byte Mag, Atari, The Well... The tech you see is really 1985ish. Attention to detail is appreciated by long time technologists.

H&CF is about building a tech business and much applies to today's startups. That two brilliant tech women are leading the charge adds to it. All the characters are great Cameron, Gordon, Donna, the devs at Mutiny and Joe channeling Jobs (in my opinion) is spot on.

Any H&CF fans have an opinion?

Emily Chang cameo on Silicon Valley just added to the authenticity of the show and attention to detail. She was giving a report on background TV in a short scene.

She does a great job on Studio 1.0. She has interviewed many tech and CEO's. Last weekend interview with Arianna Huffington was surprisingly valuable in the advice it gave to young startup CEO's.

TIL that in iOS, when you select text with double tap, it usually selects one word, but if that word is a part of a full name, it will select the full name. For example, tapping on “react” in “react sucks” will only select “react”, but tapping on “Howard” in “Howard Lovecraft” will select the entire thing.

Now that’s attention to detail. Android will never get this kind of care, pixel or not.

So attention to detail as a programmer translates well to other projects like assembling this chandelier for my brother.

Proofread the shit out of everything in your application, and then get a friend to double-check it. Especially if you've listed "good attention to detail" as one of your attributes. ;)

The ability to communicate clearly and politely can be as important as coding skills.

This sums up the education system where I live...

(SAS is for viewing grade marks online)

Was told at work today that I don’t follow directions closely enough and the lack of attention to detail in my work is a problem.

I remember being this way since my first elementary school teacher pointed it out to me. I’ve always been this way. It’s how my brain is wired. No matter how hard I try, I always miss something. Especially when it is a really complex set of tasks. I’ve literally got the results of a cognitive test I took in college documenting and quantifying my working memory deficits.

You think you’ll change that now, after more than four decades of me being like this, with a performance review? Good fucking luck!

Perfectionism... I often refactor my code because I always see something that could be "done better" in my own work, which can slow me down if I'm not paying attention to my main task.
If I could stop time I would perfect my code all day, but that isn't realistic. 😂

Doesn't apply to dev work only, I've had to learn the art of not giving a shit about every single detail in many other disciplines. I just love getting things done really well.

Already languishing custom software project on a test system automatically emails hundreds of expired users asking them to renew via the test system because I wasn't paying attention to the fact that a developer had added a cron job? Sure. Bring on the suck. Because I have nothing better to do than clean up after myself and my lack of attention to detail.

Spent half a day working on some code to add some functionality. Ran into some binary assumptions and found workarounds. Got everything implemented and close to start testing things. Not a lot of code, but a lot of places that needed careful attention to detail. Started looking at the final code needed for initializing things. Found that all the code I wrote would not be needed if I just initialize some things differently. Realized I don't need all this code. The code is literally redundant.

git checkout <changed files>

Okay, now I understand the code better. I am ahead because I am not maintaining code I don't need. Half a day of reading the code helps me understand everything that is there.

Life is good. 😀

I'm building a script parser to make mods for a game I like. The first step is to write an importer.

The documentation is nonexistent and I'm delving into byte manipulation, which I'm not familiar with - at all. I'm porting existing code from Java to C#, and everything is similar but different enough that I can't always just to a 1:1 transfer.

I get everything working, cleaned up and split into classes so I can write the exporter.

I do an import and the file won't parse. I try all previously know working files and still no good. I clean, rebuild, clean rebuild, run, debug, restart my computer, clear my cache, clean, rebuild. No good.

IT WAS WORKING 5 MINUTES AGO

Proceed to revert to every version from the last hour. No dice.

I was in the wrong folder the whole time.

Navigate to the proper folder, open the filename I know to be good and bingo, works like a charm.

The same project caused me headaches because I had a "== -1", when it should have been "== 1". Between my inexperience with byte manipulation and my untreated astigmatism, I was nearly sent to the shadow realm fixing that.

Burr puzzles, I love the way they challenge me, they also improve focus and helps with attention to detail. Great tool for ADHD.

It's not an exactly habit, it's a error that I sometimes do. Type 'funtion' when I defining a function. Then the console logs an error and I cannot identify what and where is the error in the code. After search 1/2 hour, I realize, and then I feel a pathetic dev :'v