Why do some female programmers place emphasis on their gender?

It's always: female programmer... Female web developer... Female android dev... Female Sysadmin... Etc

I mean, you don't see males saying "I'm a male programmer."

Female programmers aren't rare anymore. More and more of them are starting to program, so what's the point of emphasizing your gender?

For some reason, females think it's "special" to be a female programmer.

How does your gender relate to your skill?

Just very diplomatically told the VP of Engineering to kick rocks (fuck off) for calling me at nearly 9pm to talk about project planning for a thing that isn’t even in active development.

Asked point blank if we were dealing with a life or death thing. He said no. I replied “then we can talk about this tomorrow”.

He balks and tries to tell me how important it is.

I cut him off “I wasn’t asking you, I am telling you it’s a quarter to 9 and I’m at a bar. This call is over. We’ll talk tomorrow. Good NIGHT”. With as much aggression and pissed off emphasis as I could muster on the ending.

Stay tuned to find out if I still have a job after this.

There once approached me a client, with a request to be done. Here is a recap, with emphasis on time limits.

C: Ok, so we need this and this thing to be done that and that way...
*short talk about technical side of the project, unimportant to the rant*
C: Can it be done by 25th, this month? (It was 4th of the month)
M: No way, it'll take at least a week more, so realistically I'd say around 7th next month.
C (Had no option but to agree on the date)
*we arrange the price as well (was not a bad one at all)*

So I started working on the thing and one night, about a week or so in, I probably had a cup of tea too much, I suddenly have a breakthrough. I sat behind a computer from 22:00 till 17:00 next day, nonstop. I didn't even eat anything in the meantime. The project was far from done, but I did quite a lot of work. Anyhow, when I have completed the project, not only was I not over the deadline, it was 22nd of the month, so even before the wanted time! When I contacted the client and told him that I am done, he was ... let's just say very happy. The deployment went fine, but when I checked my bank account, for the payment, there was a surprise waiting for me. The number was 25% more than what we have arranged! Me, believing that it was a mistake, immediately messaged him about it and he responded:

No, this is just a small gift for you, because you finished that quickly.

(and not to forget, I have coded things for way less than those 25% and was completely fine with the price, so it was not a small amount)

Senior development manager in my org posted a rant in slack about how all our issues with app development are from

“Constantly moving goalposts from version to version of Xcode”

It took me a few minutes to calm myself down and not reply. So I’ll vent here to myself as a form of therapy instead.

Reality Check:
- You frequently discuss the fact that you don’t like following any of apples standards or app development guidelines. Bit rich to say the goalposts are moving when you have your back to them.

- We have a custom everything (navigation stack handler, table view like control etc). There’s nothing in these that can’t be done with the native ones. All that wasted dev time is on you guys.

- Last week a guy held a session about all the memory leaks he found in these custom libraries/controls. Again, your teams don’t know the basic fundamentals of the language or programming in general really. Not sure how that’s apples fault.

- Your “great emphasis on unit testing” has gotten us 21% coverage on iOS and an Android team recently said to us “yeah looks like the tests won’t compile. Well we haven’t touched them in like a year. Just ignore them”. Stability of the app is definitely on you and the team.

- Having half the app in react-native and half in native (split between objective-c and swift) is making nobodies life easier.

- The company forces us to use a custom built CI/CD solution that regularly runs out of memory, reports false negatives and has no specific mobile features built in. Did apple force this on us too?

- Shut the fuck up

How did I start:

It was 1994. I had been kicked out of school on academic behavior. I was working at as a telemarketer to pay the bills. I got drunk on St. Patrick's day and over slept my shift. My boss was going to fire me but said he wanted to give me a second chance. He asked if I knew anything about computers. I said no. He said if I was willing to learn, our IT guy was burning out and needed help. I said ok. Next thing I know I'm learning how to write SQL and importing data to print call cards. I read the manual for Foxpro and started building small desktop apps as labor saving devices. 6months later in knew more than our IT guy. Later a friend showed me "the Internet". I went back to our IT guy in amazement. He said it was just a fad. He called it the CB Radio of the 90s. Our network we ran was called Lantastic.

I immediately quit went back to school and changed my major. I have been a full stack Java Web developer will the heavy emphasis on UI since 1999.

Stop teaching java on a fucking notepad.

Also, since I am from India, start teaching and putting more emphasis on python. Also not to mention git without which you cant live.

If not in schools, these should be made compulsory for CS grads in universities.

We were still using python 2.7 waaay into 2020 - It had been heralding the impending doom since 2018 and finally end-of-lifed in 2020.

That's when I finally managed to be the loudest asshole in the room and allocate a team (myself included) to refactor shit up to 3.6 (then somewhat more modern) for a month or so.
COVID the destroyer may have helped by wrecking havoc on our client's demands pipelines.

It was the third week into "the red sprint" when my entire team (myself included) were beheaded out of the company since we had "not delivered ANYTHING in weeks!" (emphasis in the original).
Frankly, being laid off was by a large margin the best thing that company ever did for me.

I heard from a poor schmuck who stayed behind that they were still using the shitty spaghetti code from before our refactoring - in freaking November 2021 - and that our entire last effort was thrown out because "nobody knows how to use it".

There is tech debt and there is tech bankruptcy.
I may have a lot of tech schadenfreude now :)

One time I had this conversation with my then PM:

PM: …so in total we need like 3 extra pages; the leaders profile, event showcase and lastly a contact page.

Me: Sure, already on it.

PM: Make it simple and quick, I told the client the updates would be live in an hour.

Me: Okay.

*{5 microseconds later}*

PM: Also the page headers need to be different from the other pages.

Me: Yes, you told me that earlier.

PM: Okay, just needed to re-emphasis.

*{sad disturbing minutes later}*

PM: I don’t know if deploying on azure would be better than having the website on AWS. The pages seems slow.

Me: Yep.

PM: Or maybe we separate the asset files from the main site using a CDN.

Me: You right.

PM: The other projects on AWS seems to perform better in terms of SEO. Don’t you think?

Me: I think.

*{this dude literally just lent me a jacket and won’t allow me put it on}*

PM: So after we are done with this update we need to inform the client about the benefits of switching servers to AWS. I believe they will agree or won’t they because the event is close by?

Me: {{pointed both hands at my PC hoping they’ll get the message}}

PM: Oh you done?

Me:

I think the hardest thing about being a programmer in college with a security emphasis is when I approach a business for a penetration test or for a vulnerability analysis (your pick) is that they almost always say, "you are pretty young don't you think?"

Ummmm not sure what that has to do with it. If it would make you feel better I have claimed bug bounties from an antivirus company, a bank, several local businesses in my area and I do this for work at my 9-5.

And this week I got this, "I think I would like someone older so we can define the goals better."

Oh so rules of engagement, yeah of course I understand that and that's something we would discuss and draw up a contract for...

"Well we really need someone more skilled."

---- End of story ----

I don't understand, you haven't asked about certifications or schooling and you glanced at my resume for exactly 5 seconds what the hell do you want? Me to double my age over night?

I feel that I should mention my reason for having joined devRant.

Although I often write computer programs, I do not consider myself to be a computer programmer, for the problems which I solve often do not pertain to the method which I use to solve a problem with a computer program. Rather, I am an intelligence analyst, and this has been my title for approximately sixteen (16) years.

I joined devRant not only because I wished to better the computer programs which I write, although this could be better accomplished by again reading the specifications for the programming languages which I use, but also because I wished to join an on-line community of which the members are interesting and competent. As I read threads, I observe that both of these requirements have been matched, with the emphasis being placed on the latter requirement.

I thank the majority of you for maintaining an on-line community which is not (total) crap. Ha.

Some time ago a salesman tried to sell me a super revolutionary solution. He introduced it with "today everyone will tell you that in order to save money you must move your servers and IT infrastructure on the CLOUD (big emphasis on the word) but we offer you a different approach: 'the on premise cloud'"
😶"so, you're basically telling me to replace my local machines with other local machines?"
😎"you don't see the whole picture: It's the cloud but INSIDE your company"

Am I dumb and I didn't see the obvious technology leap he was offering me?

Our prof told us today in a zoom lecture: "Never visit b-ok.org, it is totally illegal", with emphasis on how he would NEVER recommend to visit that website for free education illegally.

I guess he is totally against the idea of pirating educational material

I think Clean Code: A Handbook of Agile Software Craftsmanship by Robert Martin should be a must to read.
In school no teacher puts emphasis on code quality.
They should learn how to name variables and functions the right way at an early stage in order to better perfect their craft :)

Hmm, there doesn't seem to be enough emphasis here.

I'm taking a unit at my university called 'simulation and modeling'. Today was the first class and the professor was talking about random number generators.

Professor: Every language has a function to generate...Every good(emphasis on good) language has a function to generate a random number... Oh well even php does...

😂😂😂😂I'm already in love with the unit...

The most unproductive meeting was definitely a day long meeting about “inclusiveness” with an emphasis on toxic masculinity. It was all the dev teams for a whole day which was ballpark 40-60 devs total. Most of us were like, “We have never even had a woman on our teams to alienate.” Eventually a dev hiring manager allowed the three female devs to leave half way through because they were being repeatedly singled out by the HR lady running the meeting.

The rest of us sat through another half day of the HR lady telling us on how bad we are because we are men.

I am back with some more emotional shit.

So tomorrow is my last working day at my second employer where essentially I'll just walk into the 10 seater serviced office to drop my laptop in a cupboard because no one else is here.

So today, an hour ago, they had a virtual farewell for me and everyone spoke of me highly with specific examples.

Well that's not what this post is about, but the emphasis is that I am still in dual mind of whether I made the right decision to quit my second employer so soon (in just 10 months)?

If I had stayed for two months more:
1. I'd gotten a hike this week
2. More RSUs in that hike along with cash
3. Joining RSUs would have vested for the cliff period of 1 year
4. Tenure would be at least a year
5. Would have found a better job with higher pay (on the new hiked salary).

I surprisingly got the grip of the product and that's when I decided to quit.

The reason I quit is I wanted to optimise for WLB and timezone with better team culture.

While the next job is surely a company I wanted for a long time and that too in B2C space, I really lost my affection for that role and that's where it came to me upfront and I rejected them initially before picking up the offer again.

My second employer is a very global and one of the largest brands. Really wanted to stick around and never got to enjoy the benefits which others did.

Only time can tell, because when I chased something I never got it, when I stopped, it came to me.

And what I am chasing now is something I am unable to achieve.

Why is life so fucked. Seems like I am about to lose one of my biggest and only life and career dream.

Maybe I fucked up this decision. Maybe not. Only time can tell.

I had this weird dream(emphasis on dream)

I was in a resort in bali waiting for my drinks and this cute girl comes over to my table.

Me : omg finally i can get a girlfriend
Me : hello beautiful
Her : hey i have this problem with my website *shows the messed up site with no divisions/containers * "can you fix this?"
Me : okay ;_;

PS : i started learning css, html and 2 other web technologies a week ago, and this is already happening to me, should i quit?

The emphasis on "team" to the exclusion of the individual (thanks in no small part to Scrum) is destroying the software developer career. It's a pendulum. There are always team/company goals AND personal goals. However, these days, the rhetoric is ALL about the team: everybody on a team has the same title, get rid of people who don't conform to some "collaborative", "open space", "colocated" ideal, etc. OKRs are entirely about giving everybody the exact same goals. I remember sitting down with managers throughout my career to talk about where I want to be in a year. What skills I wanted to explore. There were no guarantees, but the generally accepted idea was that nurturing the employee helped retain the employee. Now, there is only the idea that every developer should have the same "T-shaped" skillset, that all team members are the same, that all teams are interchangeable, that all developers are nameless cogs. It is demoralizing. If I were to give any advice to those looking to enter the industry as a developer right now, it would be "Don't". Because you will be told that being a "hero" is a bad thing. In what other industry does management tell its producers that they don't want people to go "above and beyond", and that if they do, they won't get credit for it because the credit always belongs to everybody.

When you are reading job requirements for a dev job and they put a shit ton emphasis on MS Office. I remember a phone interview where they asked skill level for Word, Excel and Outlook.

So friend told me I should make a Patreon and make it *serious*

emphasis in SERIOUS

I think his definition of serious is different from mine :3c

My 15 year old son witnessed our two male dogs licking each other's privates. My son, in some sort of shock, starts walking around the house saying "My dog is a homo sex you awl!" repeatedly (emphasis on how the syllables sounded).

I stopped him and said, "We need to talk about the birds and the birds."

The saddest and funniest side of our industry is (atleast in India): someone works hard and makes it to the best colleges, do great projects on AI, ML; get a good score on Leetcode, codechef; gets a job in FAANG-like companies...

Changes colors in CSS and texts in HTML.

And, why is there so much emphasis on Data Structures and Algorithms? I mean, a little bit is fine, but why get obsessed with it when you never write algorithms in production code?

Now, don't tell me that, we use libraries and we should know what we are doing, no, we don't use algorithms even in libraries.

Now, before you tell me that MySQL uses B-tree for maintaining indexes, you really don't need to solve tricky questions to be able to understand how a B-tree works.

It's just absurd.

I know how to little bit on how design scalable systems.
I know how to write good code that is both modular and extensible.
I know how to mentor interns and turn them into employees.
I know how to mentor junior engineers (freshers) and help them get started.
Heck I can even invert a binary tree.

But some FAANG company would reject me because I cannot solve a very tricky dynamic programming question.

Fail fast. But also... someone in a different area screwed up really bad.... so everyone can now enjoy this turning kit on productivity called a change freeze... it may be lasting for months... also... we're going to be putting a higher emphasis on productivity. So do more, but also, don't. Because we're freaking idiots.

Are most jobs and roles even requiring much computer science anymore? Seems like there's more of an emphasis on the tools versus the science when it comes to being qualified for a role and actually performing.

Started taking an Angular 5 tutorial to see how things were going in the world of Angular JS. I got to say, I am impressed. It makes me think of React in a lot of ways, but with a heavy emphasis on separation of concerns. Particularly suited for those that do not like to mix views with logic. I am liking it and going at it with an open mind although React is still my preferred option. One thing that irritates me is the ammount of "plz sir, can you give code for <insert complex and heavy app that people just do not give for free>".....so annoying.

On another note, I like how Angular brings in the concept of di among other things to the table, what I am trying to get is the feeling of writing 2 apps, there is one thing to have MVC on the background, the other is to have it in the frontend! Oh well, Angular (first edition) was fun and I know it decently well, time to get cracking on more code!!

Some of you know I'm an amateur programmer (ok, you all do). But recently I decided I'm gonna go for a career in it.

I thought projects to demo what I know were important, but everything I've seen so far says otherwise. Seems like the most important thing to hiring managers is knowing how to solve small, arbitrary problems. Specifics can be learned and a lot of 'requirements' are actually optional to scare off wannabes and tryhards looking for a sweet paycheck.

So I've gone back, dusted off all the areas where I'm rusty (curse you regex!), and am relearning, properly. Flash cards and all. Getting the essentials committed to memory, instead of fumbling through, and having to look at docs every five minutes to remember how to do something because I switch languages, frameworks, and tooling so often. Really committing toward one set of technologies and drilling the fundamentals.

Would you say this is the correct approach to gaining a position in 2020, for a junior dev?
I know for a long time, 'entry level' positions didn't really exist, but from what I'm hearing around the net, thats changing.

Heres what I'm learning (or relearning since I've used em only occasionally):

* Git (small personal projects, only used it a few times)
* SQL
* Backend (Flask, Django)
* Frontend (React)
* Testing with Cypress or Jest

Any of you have further recommendations?

Gulp? Grunt? Are these considered 'matter of course' (simply expected), or learn-as-you for a beginner like myself?

Is knowing the agile 'manifesto' (whatever that means) by heart really considered a big deal?

What about the basics of BDD and XP?

Is knowing how to properly write user-stories worth a damn or considered a waste of time to managers?

Am I going to be tested on obscure minutiae like little-used yarn/npm commands?

Would it be considered a bonus to have all the various HTTP codes memorized? I mean thats probably a great idea, but is that an absolute requirement for newbies, or something you learn as you practice?

During interviews, is there an emphasis on speed or correctness? I'm nitpicky, like to write cleanly commented code, and prefer to have documentation open at all times.
Am I going to, eh, 'lose points' for relying on documentation during an interview?

I'm an average programmer on my good days, and the only thing I really have going for me is a *weird* combination of ADD and autism-like focus that basically neutralize each other. The only other skill I have is talking at people's own level to gauge what they need and understand. Unfortunately, and contrary to the grifter persona I present for lulz, I hate selling, let alone grifting.
Otherwise I would have enjoyed telemarketing way more and wouldn't even be asking this question. But thankfully I escaped that hell and am now here, asking for your timeless nuggets of bitter wisdom.

What are truly *entry level* web developers *expected* to know, *right out the gate*, obviously besides the language they're using?

Also, what is the language they use to program websites? It's like java right? I need to know. I'm in an interview RIGHT now and they left me alone with a PC for 30 minutes. I've been surfing pornhub for the last 25 minutes. I figure the answer should take about 5 minutes, could you help me out and copypasta it?

Okay, okay, I'm kidding, I couldn't help myself. The rest of the questions are serious and I'd love to know what your opinions are on what is important for web developers in 2020, especially entry level developers.

Hey everyone. Not sure if we're allowed to do this or not. If not, whoops sorry. Anyway, I'm Vylcas. New to DevRant and developing things as a whole. Currently know html, css, and python. Trying to get better and figure out which direction to go. Hope DevRant has some chill people for something with an emphasis on ranting. Really excited to start using this app to see whats out there. Guess thats all. Have a nice day!

Bugs everywhere
Bugs everywhere
Bugs everywhere

Bugs everywhere
Bugs everywhere
Bugs everywhere

Bugs everywhere
Bugs everywhere
Bugs everywhere

I typed all 9 lines without copying them to put an emphasis on HOW MANY DAMN BUGS THERE ARE in every damn program

Not so much a problem with the way CS is taught, but I think it's a problem that a lot of people put emphasis ONLY on programming (and maybe data structures and algorithms) and ignore things like Computer Architecture or Theory of Computation.

Most of the CS syllabi I've seen are built very well, but many students (and some teachers) seem to ignore a bunch of subjects because they don't contribute to making them "hireable".

When people put more emphasis on SQL than a back-end programming language while mentioning their skills, it is obvious that they did a couple of tutorials of just SQL and never really tried to actually use it.
One guy had the misconception that you just replace the name of the text file with the SQL file in PHP require() to supposedly store the data in a db instead of a file.

Alright got an idea I have for my game engine that I'd love some input on...

So the engine has emphasis on user made content and openness to that content (EG. open source dev tools and no licencing of art) but I also want to try and build a basic ecosystem with the engine and one way I'm doing it is with cross game mods (Take a mod from one game and drop it in another and it just works... Famous last words) but something I want to try is a companion app for the engine itself...

So it'll have a custom written save system baked in engine to make progress saving and the like simpler for the end user, thinking about building an app for smart watches and phones that would connect to the engine and actually back up and sync local saves to the app and vice versa as long as they have a connection (Hotspot your phone, bluetooth or wifi) but allow you to manage some data within the app by building a basic API to let devs show the user information about the save and the game by adding description, thumbnails to distinguish games and the like...

Just want opinions if it may be a good idea to invest some time into and if anyone has idea's that could make it better.

What are the rules in a general work environment if a developer gets slightly violent?
(Emphasis on "slightly")

What happens to that developer in such case?

Anyone else think the emphasis on scaling is misplaced?

I think we can have more innovative products that solve real problems in specific ways if people focused on solving specific problems rather than targeting wider audience in attempt to sell to as many as possible.

!rant

I just made my API in my laravel and I understand how it works! It may seem like not a lot, but I got from far.

Just came two years ago in this industry as I worked as a customer service agent for a hostingcompany. I entered a whole new area what I immediatly got into at the time. Mind I already was studying Biomedical labresearch at the same time and was the IT guy in the family. Well, think back then I was just googling and fixing shit most of the time.

I was 21 at the time and began to learn everything I could learn in my position and soon it was not enough and wanted to learn more by working parttime(study already asks a lot of time). I soon applied as Junior System Engineer within the same company without prior education and got the job! And I'm back feeling I entered a new area where you feel you can do so much by just learning how it works. Now I want to learn to develop in PHP so I may make another step further.

Not a rant, but I want to share my experience as labrat starting to someting programming(did some bio-informatics, which was really interesting but with less emphasis on programming but more on data analysis). Still got a gigantic of list I want to learn from languages and frameworks to orchestration systems.

There's a big emphasis in our community on long nights and working all hours. Don't feel like less of a developer; if you need sleep go to sleep.

Take a shower, eat something, take care of yourself. Your bugs will still be there.

When Do You Stop Taking Responsibility?

Let me clarify by describing four scenarios in which you are tasked with some software development. It could be a large or small task. The fourth scenario is the one I'm interested in. The first three are just for contrast.

1. You either decide how to implement the requirements, or you're given directions or constraints you agree with. (If you hadn't been given those specific directions you probably would have done the same thing anyway.) **You feel accountable for the outcome**, such as whether it works correctly or is delivered on time. And, of course, the team feels collectively accountable. (We could call this the "happy path.")

2. You would prefer to do the work one way, but you're instructed to do it a different way, either by a manager, team lead, or team consensus. You disagree with the approach, but you're not a stubborn know-it-all. You understand that their way is valid, or you don't fully understand it but you trust that someone else does. You're probably going to learn something. **You feel accountable for the outcome** in a normal, non-blaming sort of way.

3. You're instructed to do something so horribly wrong that it's guaranteed to fail badly. You're in a position to refuse or push back, and you do.

4. You're given instructions that you know are bad, you raise your objections, and then you follow them anyway. It could be a really awful technical approach, use of copy-pasted code, the wrong tools, wrong library, no unit testing, or anything similar. The negative consequences you expect could include technical failure, technical debt, or significant delays. **You do not feel accountable for the outcome.** If it doesn't work, takes too long, or the users hate it, you expect the individual(s) who gave you instructions to take full responsibility. It's not that you want to point fingers, but you will if it comes to that.

---

That fourth scenario could provoke all sorts of reactions. I'm interested in it for what you might call research purposes.

The final outcome is irrelevant. If it failed, whether someone else ultimately took responsibility or you were blamed is irrelevant. That it is the opposite of team accountability is obvious and also irrelevant.

Here is the question (finally!)

Have you experienced scenario number four, in which you develop software (big as an application, small as a class or method) in a way you believe to be so incorrect that it will have consequences, because someone required you to do so, and you complied *with the expectation that they, not you, would be accountable for the outcome?*

Emphasis is not on the outcome or who was held accountable, but on whether you *felt* accountable when you developed the software.

If you just want to answer yes or no, or "yes, several times," that's great. If you'd like to describe the scenario with any amount of detail, that's great too. If it's something you'd rather not share publicly you can contact me privately - my profile name at gmail.com.

The point is not judgment. I'll go first. My answer is yes, I have experienced scenario #4. For example, I've been told to copy/paste/edit code which I know will be incomprehensible, unmaintainable, buggy, and give future developers nightmares. I've had to build features I know users will hate. Sometimes I've been wrong. I usually raised objections or shared concerns with the team. Sometimes the environment made that impractical. If the problems persisted I looked for other work. But the point is that sometimes I did what I was told, and I felt that if it went horribly wrong I could say, "Yes, I understand, but this was not my decision." *I did not feel accountable.*.

I plan on writing more about this, but I'd like to start by gathering some perspective and understanding beyond just my own experience.

Thanks

Let's say we want to host a small-medium project currently running on shared hosting (ehm) in cloud. What do you recommend? Amazon or DigitalOcean or something else? Our requirements are: availability > price, a good price/performance ratio, EU servers with possible North America expansion. Emphasis on availabity.

I think a simple 4-8 core server is going to be enough for now as our app is not resource heavy, but we may need to expand in the future.

Suddenly, I find myself in a crossroad situation. I have been offered a position which would align perfectly with my career path aspirations (cloud solutions architect) with double the pay to my current salary. If only those were the only variables in this equation, taking the offer would be a no-brainer. Alas, it is never that simple (unless all you care about are pay and career path, of course)…

So, let’s break it down to pros and cons of jumping ship, shall we?

Pros:
- double pay compared to current salary
- aligns with my career aspiration
- part of a team of cloud solutions architects (mentorship opportunities)
- varying projects (position is at a consultancy firm)
- shares of the company come with the position ($$$ if it grows)
- possibility to influence strategic decisions
- no more 2h+ commutes

Cons:
- it’s a consultancy startup (emphasis on both consultancy and startup)
- 100% wfh
- would mean losing my current team where we are well and truly glued together and have such great vibes (and I value this, very very highly - this really is the main con)
- would mean losing my current work environment, where we have a gym and sauna at the office etc all kinds of stuff that support my athletic lifestyle
- would mean I don’t have as many opportunities to visit my parents anymore (since they live close to my current office but not close to me)
- at my current position I have super interesting projects both ongoing and in the horizon for a long time to come
- would mean eating my words (see previous point, and the fact I’ve said to my TM ”I can see myself staying as long as this job offers me opportunities to keep learning skills that are meaningful to me”), and I value my integrity
- would mean leaving my colleagues in quite a hairy spot, effectively betraying them in my mind (when our lead dev jumped ship a few years ago, he left us in quite a limbo and hands full of shit we didn’t know what to do about… I don’t wish that situation for anyone)

So, to sum it up, my reasons to stay are more those of moral integrity and convenience, well as the will to see the wheels I got rolling to the end, whereas my reasons to go are more personal finances and career oriented. A difficult decision. What to do?

at last comfortable sleep ! ish. big emphasis on the ish part. sadly the best i've had in days.

I want to share one of my recent interview experience..

so first round was telephonic and technical guy seems cool as he did not emphasis on syntax, function name etc.. but just took the info of my tech on which I am working on and discuss some approaches to find a solution towards the problem.. ( I guess thats pretty well for experienced dev)

Second round was assignment and its a hell of assignment :( atleast for me.. Like I work in CI 3 and I did assignment on CI 4. almost everything is changes in CI 4 ( I mean its structure writing the way of routes,models and controllers).. But I took the challenge personally and finished 95% of assignment ..

Overall this interview experience was pleasant one.. :)

With liquor, a spreadsheet, and a pad of paper/pen...

Emphasis on the liquor...

I hate web dev. I said it. When you build a simple website with clean, consistent business and display logic and your boss asks you to make exceptions for every goddamn record. Maybe it's how the type is rendered. Maybe something needs emphasis. Maybe the designer doesn't like how a specific record word-breaks, so you have to write logic to handle that. It's always SOME annoying little detail that takes hours and hours, complicates logic and won't even be noticed.

I just never expected to run into people who don't have shit better to do then literally the same shit and cyberstalking people they don't even know trying to act like they give a damn for personal amusement or just lurking in the same places waiting to spring up and say the same thing or just whatever the hell this crap is when the person they're doing this too doesn't really have anything of interest other than precisely what i've indicated, that or try to be nosy and be amateur intelligence people trying to gather information over what a person is thinking regarding the activities of certain garbage in his environment :P emphasis on amateur.

My coding style is mostly influenced by good old personal preference, but also because of a certain internship where there was a lot of gain to be had by making everything as reusable and testable as possible.
I guess you could say my motto is usability, readability and flexibility:
I like tidy, reusable code with an emphasis on keeping code readable. I've always liked modular things I guess...
And I despise two things: curly brackets on the next line and spaces for indentation... But way worse is having no brackets at all (looking at you Python): it's clearer to have lower-level code inside some sort of "container" markers i.e. brackets (also gives more IDE functionality like color-coding hierarchically).
Indentation should always be tabs so anyone can have their own width of indentation set through their IDE, making it way more accessible to fellow colleagues!
And I also like having parameterized code over hard-coded functions: way more flexible.

I never did get that break I wanted. Though, I did get off incident tickets.
Has been replaced with project after project though, with the emphasis being on "getting it over the wall", so as you can imagine. There is a pile of tech debt that's just being ignored. It'll blow up in production one day.

It's not all doom and gloom though. I've gotten the opportunity to write a few things, from scratch that are separate from the rest of our products. Nothing nicer than a clean slate, not built upon a steaming pile.