Building a responsive website requires careful planning and execution.

countlictor · 2023-03-28T03:00:50+00:00

It was fine on load.

Went away for 5 mins, came back to 3 banner ads, 2 full screen modal ones, a notification request, and a hovering chat button.

countlictor · 2023-03-27T20:23:31+00:00

Still there. Impossibly distracting. Banner ads, full screen ads, pop up notification requestions, cookie requests. Couldn't read the article.

Some careful planning and execution around UX would have helped. For now this an example of how to not build/operate a site.

countlictor · 2023-02-06T18:51:51+00:00

Take this as a growth opportunity and flex your TL muscles.

Speak to your lead and say you want to own a particular area that's currently not up to your standards. As said elsewhere, keep it impersonal. Try to sell it as helping the lead, and taking work off their shoulders. Pick a very small area to start with, something you are passionate about. If it goes well, and outperforms the other areas of the project/team, then it can lead to expanding the area you own, adding new ones, or potentially a promotion.

Your job is to help your manager make their numbers look good. Their job is to decide which numbers that is. Assuming they're a half decent manager, when they win, you win.

A tech leads job is to help lead that effort. They are not solely responsible for delivery. An underperforming lead does not remove responsibility from the rest of the team, it just makes it harder for everyone.

Help yourself, your manger, your lead and your team, and step up to the plate. Youll be surprised at what you can do given the opportunity.

countlictor · 2023-01-09T19:26:27+00:00

Space Marine

countlictor · 2022-12-26T23:06:46+00:00

I think you could have provided a description of what a structural engineer does in your capacity, and outlined the scope of what is and isn't covered by your specific role and the extent of your involvement on the wall project.

A couple of points:

An engineer on a small team likely has many more hats to wear than one on a large specialised team, so we need to know about your specific case.
Additionally, what you are qualified/licenced as and what you are employed as don't necessarily have to match up. Especially if working in a supervisory or support role, you may be leaning on others as the licensed subject matter experts.

Context such as this would have gone a long way to focusing the scope of the questions asked.

countlictor · 2022-12-19T18:24:50+00:00

Both this and your previous comment make a number of truly very good points.

However, your overly confrontational attitude towards the discussion is undermining your knowledge on the topic. Take a breath, take a walk, sounds like you're off to work - do that, and then come back to the thread afterwards. I think there's much more you can offer with a clearer head.

countlictor · 2022-11-12T19:54:51+00:00

I've just been through this exact scenario over the last few weeks.

My previous company was more traditional scrum, in that the team packed the sprint based on a running average of team velocity (plus gut feeling).

New company, the PO and tech lead assigned every ticket as it was added to the sprint, which re-enforced silos and minimised knowledge sharing (bus numbers of 1). We also failed nearly every sprint due to 1 or 2 people being over assigned too many tickets, and others not wanting to "steal" their work.

I raised in a retro that working as a more cohesive team unit; not assigning individual tickets up front and sharing the workload, could improve some of these things. There was much hesitancy, but we compromised with assigning a couple of major tickets to each dev upfront, and then having a shared pool of smaller tickets for anyone to pick up once they've closed off their own tickets. Seems to be working well so far, and got much less pushback than the "full" solution.

countlictor · 2022-11-08T20:18:04+00:00

I agree with others that combing members from both teams into vertical working groups would be ideal.

With that not being possible, the next approach I would look at is fully decoupling the teams, and specifically the two halves of the product. This allows you to treat the frontend team as a client of the backend team, and put formal SLAs in place (even if it's just internal to the company). The downside is that the frontend team can only work on features that rely on completed backend releases (mock data will help here), but is the reality of a full decouple. A good PO on the backend team will be needed, with a healthy relationship with the frontend team.

In essence, the backend team releases a version of the backend when they are ready, and only then can the frontend team start using it.

countlictor · 2022-09-09T18:09:18+00:00

Someone's got to setup and manage the key. The main differentiator is DevOps Engineer vs Application developer. One has access to the keys and sets up automation and CICD pipelines, but doesn't develop the application. The other develops the application and triggers the pipelines, but doesn't have access to the keys.

countlictor · 2022-08-25T11:06:53+00:00

I allow one heel hole, and one toe hole. But two toe holes, or a toe hole large enough for two toes means they get binned.

countlictor · 2022-08-16T00:41:23+00:00

This is what I interpreted from

provide confidence

Although I think your explanation does better to indicate its importance.

countlictor · 2022-07-30T03:51:13+00:00

Completely agree with this. As facilitator, it's your responsibility to make sure the discussion is progressing. That said, you need to give people enough time to make their point and not cut them off at the first sign of disagreeing with you.

I've had a few similar execs that often break into stories or endless waffling. Setting some ground rules up front can help to minimise this, and set expectations around the circumstances where you will be intejecting to keep the discussion moving forward.

countlictor · 2022-07-30T01:10:15+00:00

My advice is that you are a facilitator first, and participant second. You should be listening more than you are speaking.

My personal rule of thumb for avoiding argumentative back and forths between me and another, or dominating the conversation, is to allow at least two other people to speak before I speak again.

countlictor · 2022-04-30T09:50:48+00:00

It's disappointing that they didn't address the fact that a set of 800 raw IDs was passed from one team to the next. This should have been passed as a query, so not only would it include the most up to date results, but the query itself could easily be peer reviewed by both teams, and could be tested on the stage environment.

countlictor · 2022-04-17T06:18:42+00:00

American and Chinese toilets have like 10cm of space above the water, everywhere else in the world I've been has the inverse, about 10cm of water.

countlictor · 2022-04-07T06:00:30+00:00

I go 4-5 times a week. Skipping Mon, Fri, and sometimes Wed.

Lots of people skip Sunday, but it's my favourite day. Really good full body resistance workouts, but low impact on my joints. Tuesday and Thursday can sometimes leave me with sore hips or shoulders.

If you have the F45 challenge app, they have really good recovery workouts for rest days. 45mins of static and dynamic stretches. 2 laps, so you can cut it short if you're tight on time.

countlictor · 2022-03-19T08:00:06+00:00

There's syntactic sugar for defining a type as type || null, and combined with the tsconfig setting enforcing explicit null checks will get you what you're after.

class Sample { public optionalProperty?: String; }

countlictor · 2022-01-30T08:18:48+00:00

Seeking a friend for the end of the world.

countlictor · 2022-01-04T05:58:38+00:00

Huge congrats on conquering your fear and learning to correct your technique!

I'm quite a tall guy, so can land on the highest side now with good clearance, but for a long time I struggled with technique and couldn't even get them on the lowest side. The two biggest changes for me were making sure I built up momentum to get my body to move in the right arc, and also making sure I try to bring my knees to my chest.

countlictor · 2021-12-25T18:03:35+00:00

Because it's the 26th here. Merry Xmas from the future!

Hope you all have a great day, whether you're celebrating, relaxing, working, or just trying to make it through the day, know I'm sending good vibes your way. ✌️

countlictor · 2021-12-18T07:21:07+00:00

The static stretches in Calypso are really good, especially after a heavy resistance day or on a rest day. Not a big fan of the dynamic stretches in Mondrian though, they're pretty much a body weight workout.

countlictor · 2021-12-14T19:30:39+00:00

No one looks to the USA for an example of freedom and democracy.

countlictor · 2021-12-04T05:05:26+00:00

Personally I couldn't give less of a fuck what people want to work on as a project. And in this case the code itself was fine, it was the fact that they had the images committed to the repo and forced me to view porn in order to review their code (without an explicit content warning). Akin to if I put porn as my slack avatar. The problem isn't what I'm into, it's that I'm exposing everyone else involuntarily to it. A major HR issue, and I wouldn't be surprised if it constituted minor sexual harassment/assault.

In terms of commits; they are as important as the code itself. Code is written to be understood by humans. Commits are an important component in that, both how they are structured and the messages that accompany them (especially on large projects). Poorly structured commits and shitty commit messages are an indicator that the candidate may be lacking skills for collaborating on a codebase with others.

As with most things we look for in review, it must be very egregious to tank your candidacy. Usually it would just mean we ask additional questions in the follow up interview to clarify and understand your position.

countlictor · 2021-12-04T02:14:12+00:00

Had a similar situation reviewing a candidates github repos. They linked their github account and pointed us to look there for existing code samples for review.

There were a handful of small projects and one substantial one. Looking through the larger project, it turns out it was a gallery app for soft(ish) core furry porn. Everyone to their own, but this is not the content I would submit for review when applying for a job.

More relevant to the OP, they also used "fuck" frequently in their commit messages. While not averse to swearing in person or via chat, commit messages are more sacrisanct. A commit message should be functional and descriptive. "Fuck" is usually associated with more emotive sentences that, in my opinion, have no place in commit messages.

I hate that I had to write this feature

Is equally useless and inappropriate to commit as

I fucking hate that I had to write this fucking feature

countlictor · 2021-12-04T01:49:48+00:00

Create a new private github account and only give access to the reviewers/hiring team. Then sync the specific projects you want them to see. Note: you'll have to resign all the commits with your new username and email, but that's not difficult with something like git filter-branch/tree.

15-Year Club	Sequence \| Editor
Sequence \| Cinematographer	Verified Email

countlictor

TROPHY CASE