Me and commitments

I'm gonna be honest with you guys.

I need a friend. A real friend. And I'm looking for one (or many) among you.

Is any of you interested in being my friend?

I know, it sounds weird. My inner self bully is bringing to mind many adjectives for saying that: faggot, weak, snowflake, gay, pussy, clingy, demanding.

I know. But I'm at the edge of 30 and I think it's better if I cut the shit and just be very clear about the type of friend I'm looking for.

I need people that will be there when the shit gets tough.

I can joke with you,
I can laugh my ass off with you,
I can passionately argue about what's the better programming language.

But most importantly, I can be there when you're depressed, when you want to punch your boss in the face, when you're griefing a loved one that is gone.

And that exactly what I'm looking in a friend.

I used to have friends in life, but a variety of circumstances caused some distance: commitments, personality changes, physical distance, or just a feeling that they don't give two shits about me.

Am I the perfect friend? Not at all. I have a temper and am quite opinionated about my tools, but most of the times I try to be a not-asshole.

I might get angry and be very honest when I don't like something, but it would be very weird for me to turn my back on a friend.

It is impossible for someone to be friends with and to like everyone. But the least I can do is just give anyone a chance.

I think friendships are just things that take time and grow if there is enough care put into them.

Here's my discord chirptune#1829, so if you add me, please let me know your username here.

I think it'd be cool to have like a brotherhood on discord or slack of people looking out for each other (jesus christ, that sounds corny as fuck)

Not to rob people from devrant, I just think that the board style can't fulfill deeper social needs imo, that's all.

My teams current process is:

1) Asked by product to create “T-Shirt size” estimates, also known as a WAG (wild ass guess). The process is the mental equivalent of throwing darts while blindfolded, after being spun around in a circle and pointed in the wrong direction.

2) Product make firm commitments to upper management based off these. Ensuring them that all these features will make it out in Q2.

3) 4 days before Q2 starts, product ask engineering to figure out the real estimates based off no concrete information what so ever.

4) 4 Weeks into Q2, product provide the missing information.

5) Engineering inform product that the estimates are out by a factor of 1.5 - 3 times the original estimates.

6) Product sends angry email to upper management that through not fault of product, engineering are unable to meet the deadlines.

7) Everyone shout and complain until 1 week before Q3, then see point 1.

Following this process, you and your team can be just as delightful as me.

That’s the practiseSafeHex guarantee!

We had to review a design document written by our partners, and have it approved by end of Dec.
While I was reading it, I noticed that we committed to a module I wasn't familiar with. I asked the other two lab mates, and they had a surprised Pikachu face.
So we called the boss to discuss this. And it dawned on him that we committed to a task that was assigned 20 months of work, but nobody started working on it. And considering Holidays and other commitments, we had like 3 months to do it from scratch and deliver.
My advisor panicked, and his first response was to assign this task to me.
I politely declined, and after digging in my email box, found that he actually assigned the task to someone else. So I showed it to him.
Thinking I would save him after he treated me badly for nearly 2 years was hilarious. For a better manager, I would have definitely agreed to assist. But as it is now? I'll be eating cookies while I'm watching the project burn.

Dear fellow mate,

I can't reject your request to leave. You have your right to request casual/medical or any suitable form of leave. It's up to the HR to do their calculation and process your leaves.

All I can do is tell you the overview of our team's tasks status. And status of tasks assigned to you. Then tasks status of possible colleagues who can cover your position.

The reason I shared those with you is that you act like you have no knowledge about them.

That's all I have for you. Decide on your own what to do. But consider with this new information.

Regards,
Cursee

Just need to get this off my chest. Started a new job 3 weeks ago at a company that has been around ~18 years, it is only recently that they have started to grow more rapidly. I was brought in under the guise that they wanted to embrace change and better practices and so said I was up for the challenge.

In my 2nd week I was asked to produce a document on tackling the technical debt and an approach to software development in the future for 3 consultants who were coming in to review the development practices of the company on behalf of the private equity firm who has taken a major stake in the company. I wrote the document trying to be factual about the current state and where I wanted to go, key points being:

Currently a tightly coupled monolith with little separation of concerns (73 projects in one solution but you have to build two other solutions to get it to build because there are direct references.).

Little to no adherence to SOLID principles.

No automated testing whatsoever.

Libraries all directly referenced using the file system rather than Nuget.

I set out a plan which said we needed to introduce TDD, breaking dependencies, splitting libraries into separate projects with nuget packages. Start adhering to SOLID principles, looking at breaking the project down into smaller services using the strangler pattern etc. After submitting what I had written to be part of a larger document I was told that it had been tweaked as they felt it was too negative. I asked to see the master document and it turns out they had completely excluded it.

I’ve had open and frank discussions with the dev team who to me have espoused that previously they have tried to do better, tackle technical debt etc but have struggled to get management to allow them. All in all a fairly poor culture. They seem almost resigned to their fate.

In my first 2 weeks I was told to get myself acquainted and to settle myself in. I started looking at the code and was quite shocked at how poorly written a lot of it was and in discussions with my manager have been critical of the code base and quite passionate and opinionated about the changes I want to see.

Then on Friday, the end of my third week, I was invited to a meeting for a catch up. The first thing I was told was that they felt I was being too openly critical in the office and whether I was a good fit for the company, essentially a stay or go ultimatum. I’ve asked for the weekend to think about it.

I’ve been a little rocked by it being so quickly asked if I was a good fit for the company and it got my back up. I told them that I was a good fit but for me to stay I want to see a commitment to changes, they told me that they had commitments to deliver new features and that we might be able to do it at some point in the future but for now I just needed to crack on.

Ordinarily I would just walk but I’ve recently started the process to adopt kids and changing jobs right now would blow that out the water. At the same time I’m passionate about what I do and having a high standards, I’m not going to be silenced for being critical but maybe I will try and tackle it in a different way. I think my biggest issue is that my boss who was previously a Senior Developer (my current position) has worked at the company for 12 years and it is his only job, so when I’m being critical it’s most likely criticising code he wrote. I find it hard to have the respect of a boss who I had to teach what a unit test was and how to write one. It makes it hard to preach good standards when by all accounts they don’t see the problems.

Just wondering if anyone has suggestions or experience that might help me tackle this situation?

1. Pre-sales to Client: We can develop 200 APIs with 10 developers in 9 months.

2. Client: Ok! Cool, its a deal.

-- Sprint starts --
3. Actual: We are 6 developers, commited (or sold out) to make 200 APIs in 9 months.

Fucking pre-sales.

It doesn't feel good to be average at everything.

Life is depressing

I can't commit to anything hard enough to become the best.

Programming
Singing
Drawing
Story making
Sports

I'm just average.
I feel bad
I feel like I'm a waste of resources.

I'm tired of ranting.
This life is just tiring.
I don't have the patience

I'm average at commitments.
Time management

I see other people code and sing better than me and feel demotivated

I feel like jumping of a cliff cause no matter what I do, there's someone light years ahead of me.

I'm not even unique
Ultimately that's probably what I want.
To be irreplaceable.

I guess in this struggle to be relevant I'm gonna lose myself and if I do get there, I might not be as happy anyways.

So what's the point to all this

COO overcommited features to our client so now we have to do overtime until June so that we can save his ass.

Its his fault, why the fuck are we responsible for his incompetence.

I am just sick of the things that's been going on.

Joined a mid level startup as full Stack developer working on angular and node js . Code base is too shit and application is full of bugs(100+ tickets are being raised for bugs)

Since the product owner(PO) wants to demo the application he is pushing for bug fixes.

UI code:
1. Application is not handled for responsiveness all these years, it is now being trying to address. Code base is very huge to address though .
2. The common reusable components of UI has business logic inside. Any small change in business logic we are forced to handle in common components which might break up on another components.
3. Styling in 40+ components are made global. Small css change in component A is breaking up in component B due to this
4. No time to refactor.
5. Application not at all tested properly all these years. PO wants a stable build.
6. More importantly most of developers have already left the company and we are left with 2 developers including me.

I am not in a position to switch due to other commitments adds up a lot to frustration

I need some advice here... This will be a long one, please bear with me.

First, some background:
I'm a senior level developer working in a company that primarily doesn't produce software like most fast paced companies. Lots of legacy code, old processes, etc. It's very slow and bureaucratic to say the least, and much of the management and lead engineering talent subscribes to the very old school way of managing projects (commit up front, fixed budget, deliver or else...), but they let us use agile to run our team, so long as we meet our commitments (!!). We are also largely populated by people who aren't really software engineers but who do software work, so being one myself I'm actually a fish out of water... Our lead engineer is one of these people who doesn't understand software engineering and is very types when it comes to managing a project.

That being said, we have this project we've been working for a while and we've been churning on it for the better part of two years - with multiple changes in mediocre contribution to development along the way (mainly due to development talent being hard to secure from other projects). The application hasn't really been given the chance to have its core architecture developed to be really robust and elegant, in favor of "just making things work" in order to satisfy fake deliverables to give the customer.

This has led us to have to settle for a rickety architecture and sloppy technical debt that we can't take the time to properly fix because it doesn't (in the mind of the lead engineer - who isn't a software engineer mind you) deliver visible value. He's constantly changing his mind on what he wants to see working and functional, he zones out during sprint planning, tries to work stories not on the sprint backlog on the side, and doesn't let our product owner do her job. He's holding us to commitments we made in January and he's not listening when the team says we don't think we can deliver on what's left by the end of the year. He thinks it's reasonable to expect us to deliver and he's brushing us off.

We have a functional product now, but it's not very useful yet and still has some usability issues. It's still missing features, which we're being put under pressure to get implemented (even half-assed) by the end of the year.

TL;DR
Should I stand up for what I know is the right way to write software and push for something more stable sometime next year or settle for a "patch job" that we *might* deliver that will most definitely be buggy and be harder to maintain going forward? I feel like I'm fighting an uphill battle in trying to write good quality code in lieu of faster results and I just can't get behind settling for crap just because.

I’ve now worked with three Toptal devs. The first one logged time he didn’t actually work and would edit conversation history to conceal commitments he had made. The second one would disappear for days at a time without notice, and the third is incapable of communicating or working together with team members. She has replaced large portions of our codebases without notice or discussion, and now we have to roll all of it back and convince Toptal to refund the time.

Turns out that toptal’s interview process manages to miss things like honesty/trustworthiness and communication. Be careful hiring from there.

Best way to avoid procrastination : We tend to avoid commitments or to do large tasks as even visualizing them seems tiring and the longer it takes, the vulnerable we are to distractions

So I use this simple trick
I break my task into numerous sub tasks. For example if I need to finish a feature before day end, I would first list down all the cases I can think of in order and write them down using actual pen and paper.
I then start implementing them step by step.
I mark them checked once done.
It gives me a sense of achievement as I see those checks besides the sub tasks and I can also take breaks between steps.

So all it takes is just first five minutes of planning.
I had to do the above procedure, for this post as well.
Hope it helps fellow developers
:)

A manager in the area, in an effort to “encourage” teams to meet their externally generated commitments before imposing mandatory extended hours, posted a chart showing Mt. Everest with weekly goals as stages up the mountain. First team to the top wins a $20 gift card. Looks just like this picture. Results will probably be similar.

I think reactjs is an actual cult. Not like one, not similar to one, but a real actual cult.

They have magical thinking, deny reality, blindly follow whatever new things there is, rationalize insane things, require immense time commitments, have an elitist attitude, it's an actual real life cult.

The interview I was so nervous about apparently went well. It’s a small ad company.

I was offered a month long “work trial” period.

Problem is I was caught off guard with discussing compensation & what I agreed to is less than half what the average dev makes in my state.
Like barely above min wage

I feel much less excited about this but this would be my first job in a loooong time.

I’m not sure how to feel but I think I have to at least try, but I feel taken advantage of already!
Is that bad? What would you guys do? How would you approach this before sending any signed commitments back?

Ugh!!!!!

(Questions below.) At this point I probably just whine about job search in IT w/o much commitment. It's because I don't learn stuff from interviews and have no willingness to prepare for primitive questions from HR's book. You know, stuff like: "What was your experience on previous jobs and why you quited them?" and "What are your advantages and cons?"
Even though I see them a bit discriminatory. I barely find words and make them audible alrite, and so rush to the stack questions. I answer 50% of them in average, 20% ideally. As a result, I get no conclusive offer. Fair... probably not. Doesn't matter.

All of a sudden, idea chimed in to make a personal website with all of the frequent questions answered in advance. At last, I've got some time to make the decent replacement of the CV into a landing page that communicates my professional and emotional ability to headhunters.

TL;DR: I wanna make my personal website portfolio and I need your word about the following.
1) Can I make up for the absence of my own live projects with OSS commitments or other smooth talk?
2) Is there a merit in answering the common interview questions right off the bat in written form?
3) So, I already prepared 4 conclusive theses with thoughtput choice of words, that I wanna place as a grid in first scrolling section. I call it "Principles", but perhaps there is a synonym to this one or it's good as it is?
4) I don't want to represent myself as a blunt set of "features". How do I transite into explaining the usage of my stack in these circumstances? Less text better, right?

It was the worst local Hackathon. It's not even a Hackathon either, where the whole event spanned over 2 months.

It was a group entry with me and 4 teammates. Each of them did contribute:

Guy A: criticizes what is built and designed
Guy B: offered financial tips on how to make this thing feasible
Guy C: did UI but in graphics. No CSS file, just bits of graphical elements.
Guy D: family commitments

And then there's me, writing documentation, built the entire project, wiki, drove the project, prepared the presentation slides, tests the framework, unit tests, stuck with stupid problems like SSL, localhost, Google Maps Key and the likes.

And we didn't even win, let alone launch this thing, whatever it is, to anywhere. Never doing group projects again.

I'm flying solo for now

I told PM that a feature is only ready on Thursday. He goes and tells Tuesday to the business owner. Comes to me and says make it happen. Nope, sorry. Not going to happen.
Non-tech people should not make commitments. I long for the day their jobs become obsolete.

Question: is it common for lead software engineers to mostly do paperwork or is that just a quick of my current program?

Where I work it is very common for those titled "software leads" to be almost completely hands off the software. They deal in hiring, fielding user comments and commitments, and scheduling. I would like to be a lead but I was always under the assumption that dev leads had more of a design and/or architect role. Sort of a big picture thing rather than middle management which is what this feels like.

Estimates.. First, part of the team makes "high-level" estimates which are based on informal, incomplete, still-evolving specs and an unstable back-end. The project people report the estimates to the client and elevate the status of these inaccurate estimates to that of commitments.

Then, before the "sprint", we review our initial estimates *ahum commitments* in greater (technical) detail. Because there are still a lot of unknowns, we tend to estimate more buffer here (back-end is often not ready, always ping-pong between project people and dev-team about unclear specs, more work than originally expected, and often late modifications to the original spec).

When an estimate becomes more than 50% extra time at the "refinement", we are told: "sorry, we gotta do it in less" and when it doesn't work out, we're kindly asked to spend part of our weekend catching up at 100% pay rate (legally it's 150-200%).

FUCK THIS SHIT

*quotes used abundantly because these terms belong to "agile/scrum" terminology but we're only pretending

!rant but tips

TL;DR consistent commitments form a habit.

I didn't write any code or do any major tasks past 5 days. Rest at home 2 days and went to short trip for remaining. Answered a few business calls. Made few important calls. Didn't bring my laptop with me and used my gf's one for less than 2 hours. (Majority of that 2 hours was spent on changing her W10 Japanese display language into English.)

This morning I found it hard to gain the productivity and concentration I had past few months. I thought I have lost it and got back to my old lazy 🐒 self.

Couldn't able to touch, well didn't have the mood to touch to be precise, my major tasks. I did my best to sit at my desk and finish minor small tasks that I can find the whole morning. That's the best I could do and probably the wise one I did.

After lunch time around 2pm, I gained my concentration back. I worked on my major tasks till 7pm. And now going home happy.

So my "productivity-is-a-lot-like-intercourse" analogy belief became stronger. As long as I commit to my desk and keep my work routine, I won't be losing my concentration and productivity for a long period.

Deadlines and commitments at a startup company are similar to when Road Runner chases Coyote off a cliff , and he suddenly realizes there is no longer a cliff below him to stand on. Frantically, he tries to build one before he falls. He still falls, but in our startup we somehow magically walk on air everyday.

Anyone ever get cold called through LinkedIn? I had a guy contact me asking could we have coffee. Did some research on him and he seems a pretty successful guy. I was curious so I responded with a time and date.

Met him and he explained his business, what he was doing and what he was looking for. It was a senior position but would involve alot of backend work and team leading. Lots of long hours.. i was very interested but due to other commitments I couldn't take it further, so I politely declined.

Fast forward to 6 months later, he comes back to see if my situation has changed. It has. He says the company is being bought out and being funded for 3 years, he is in the middle of negotiations and its almost done. we begin negotiations and I agree a nice package with benefits. He seems delighted. I am happy.

Nearly 4 weeks later, 3 unanswered messages and an unreturned missed call, I am like wtf!!!

I thought I posted about this awhile back but I didn't. I'm glad since the story is so much better now.
6 weeks ago: Told I'm going to be on a super fun JAMStack build with lots of sexy animations. Sweet, this will be a fun build!

5 weeks ago: Find out what the timeline on this incredibly ambitious project is. I start raising flags cause everything needs to go PERFECT for this to not blow up and/or turn in to a dumpster fire.

4 weeks ago: Project "kicks off" with a meeting with the client. We find out that they've decided to do another round of revisions on their design comps, but we have what we need for sprint 1. We provide a list of all the assets/information we still need for sprint 1 success.

3 weeks ago: Still waiting on some assets for sprint one, but we're fumbling our way through. Still waiting on the PM to get around to doing their PM job and building out our backlog / gathering requirements for us.

2 weeks ago: Sprint 1's end date comes and goes. Still need assets from the client, I've personally asked them for the same asset 3 different times. Sprint 1 gets extended 1 week.

1 week ago: We deliver sprint 1 page templates, minus the resources we're still waiting for. Get chewed out by the client regarding the pages not looking like their comps (Yeah, no shit sherlock, you never sent us the assets)

This week: Working on Sprint 2 commitments. We have 2x as many page templates to deliver, per developer, as we had the first sprint. Still waiting on Sprint 1 assets. Don't have Sprint 2 assets. Wait, what about the global styles? They still haven't sent those to us yet either.

Requirements? Guess I'll spend valuable dev time tracking those down for myself.

Client? Well, they're pissed off we haven't hit our commitments yet.

Oh well, at least we have a pimple faced, fresh out of college, CS major, with no real development experience rolling on to this cesspool of a project.

Other devs? Well, we're out of fucks to give. Lets just watch this thing burn.

Oh, I forgot to add, we have 17 page templates to deliever between today (2/27) and 3/18. #NoFuckingWay

Remember that git commits are just like commitments in a relationship.

Make them small and avoid the big ones.

Just wanna rant about something in general..

I'm quite serious about time commitments. I can't stand people who change their words at the last minute because all these weeks they were just fuckng around not preparing and doing that had to be done.

For fucks fake, we have been discussing every intricate details of things that had to be done!!

And even worse, they expect you to bear the consequence and delay all your plans for their convenience..

:/

The existence of my pm. He is extremely good at lose, unrealistic commitments and not giving a shit about the devs.

Here's hoping the interview goes well and I get to resign with grievance.

OO tip: Couple your objects like a reluctant partner - no commitments.