sirkarthik

Leveraging LSP is one of those most overlooked thingy in using AI coding tools like Claude Code (CC).

The most expensive component of the AI-SDLC isn't the intelligence—it’s the context.

Unlike its counter-parts like Python, Javascript or Ruby programming languages and it's ecosystem that keep evolving at frantic pace, Java and ecosystem doesn't and hasn't changed dramatically. What is more worrisome is that most of the Java teams haven't caught up with its own contemporary toolset. This post is a list of tools that I think your teams should be using for profit from developer's productivity.

There are startups that live by word of mouth or email communication for anything and everything without any automated notifications of any kind, even today. And then there are many companies that has got annoyingly big and loud notifications, making its team mute it altogether, thus resorting to acting on event based on word of mouth (command from leadership). The later though jazzy, only increased overhead cost of tools than any productivity on ground.

If you can relate to this and are looking for a systematic approach to lean and manageable notification practices that enhances transparency, and accountability, do read further.

Some of recent early Engineering Management retirees of hot tech companies wrote about their opinion of early growth in Engineering Managemnet citing their own career example and that of others in their company. While I respect their opinion and their company, I would like to believe that exceptions don't make a good rule. I am not sure how this worked for them ad other folks in their company. This post conveys by sample set questions to give a taste on the sheer number of things to experience and have an informed opnion about before taking that giant leap into Engineering management. What is your take on this topic based on your experience?

Fair enough reason for you to try WSL on Windows. So you can switch between your coding and gaming in a jiffy.

This is where WSL shines and as the blog post says how you can get the best of both worlds ;)

oh-my-zsh comes with minimal set of default plugins. The others you can add. Check out oh-my-zsh github page for themes and plugins. I guess the comment in your plugin configuration section will also warn you about adding too many plugins having performance impact.

Yeah its a trade-off between performance and convenience. One should know when to stop and how to slim down based on the usage. Often installing too many plugins when not using them is something that I have witnessed often with curious developers. While the real reason is installing too many plugins, the blame is on zsh ;)

Used figuratively in the sense of https://history.nebraska.gov/publications/kool-aid.

We are today living in a world where for every proverb there is an anti :P

I have been working for a month this way and it has been smooth so far.

It used to be so but is so much better and stable these days. For every such issue that I have faced, I have put it as ProTips in one blog post, esp. for my own reference, as much as for others going through similar experience. Follow it all, and you too should fall in love with the workflow ;)

https://www.koolaid.com/ shows children's products that is a fun mixture of many items. There are also links that share recipes using these terms like https://www.food.com/recipe/absolutely-perfect-kool-aid-3338...

Also as History would have it, this was first coined perhaps in Nebraska, for commercial purpose as put in the article https://history.nebraska.gov/publications/kool-aid.

I think there are many such terms in English that has polar opposite meanings/cannotations/usages. "Swasthik" is supposedly a very pious symbol for the Hindus. Incidentally, the Nazis used a similar or closely resembling symbol but had never called it Swastik/Swastika. And yet the cunning colonial British popularized that as Swastik and the world continues to refer to it so instead of calling it merely Nazi symbol.

AFAIK, historically that hasn't happened. Sales is shit hard. Getting every single client is an art in itself. You got to be a magician to get even 5-10 clients signed-up readily in one go, for a start-up. And by the time you are having "N" paying clients that matches your metric for product-market fitness, you start evolving your architecture to the next level. This is where Product and Engineering sit-together to take that strategic decision on the path forward.

LoL, for the way you finished your point. Good to know your experience :)

Did Amazon mere said, "you are doing it wrong", without an explanation? In retrospective, do you think you could have done better? I'm looking to hear the lessons you learned, so may be, I don't end up making that mistake ;)

Thanks for sharing your experience. Mind sharing the details of the bugs and the middleware you were writing. IS that an open-source library that I can take a peak into?

Isn't that a different tangent? Does it matter, when the SaaS codebase is same for all tenants? If you are dealing with different codebase for different clients, then that is a flawed approach in that it is error prone and not scalable as tenants increase in number.

Thanks for sharing the doc...

The limits on tenants are soft limits and should be extendable by reaching out to them.

I second that..except for the security part though ;)

* AWS (Amazon Web Services) * Python for Data Science * Machine Learning with Python

This one seem to have caught the attention of a lot of readers in Hackernoon on Medium platform. #InterestingRead #ReadIt

I had turned down a lot of job offers till date for one/more of the following reasons:

* Poor work culture

* Lack of opportunities to learn at work

* Not a competitive pay

* Dated tech-stack

* Sensing toxic work atmosphere

* Company ridden with ivy-league grads that it boasts of during the course of interview. Sure-shot path to 2nd grade treatment should you join such place because it's not your knowledge that they see but only your certificates. [Confession: I learned this a hard way :(]

AWS Reference Architecture for Web App hosting (http://media.amazonwebservices.com/architecturecenter/AWS_ac...) shows S3 as being used for static assets and CloudFront to deliver it. Interesting they also show a Web Server under the ELB, making the reader why would one use it, given that S3 is used to store all the static assets.

Best learning comes from experience. The best one could get out of books or video tutorials in the case of learning cloud infrastructure services like AWS is a firm fundamentals of their stack or services. This awareness is what would prove helpful.

There are a ton of things that could be done and a constraints are fast disappearing with change in services or cropping up of new services to meet the requirements.

So cheers, don't you have to worry of knowing things inside out of every available services to boost your confidence. #My2Cents

The issues cited in this post is something that I get to witness even today..

I've witnessed the unfortunate consequences when each of these rules were violated.

I've seen kludgy code when Rules 1 and 2 are violated for instance.

Employing Fancy algorithms to look good among peers, leaving behind buggy and maintainable code.

Rule 5 violation is deceptive. Often one can get it right with right understanding of business use-case.

The worst part is not the violation of these rules but the developer's chest-thumping with pride for writing seemingly intelligent code :-/

Only for team oriented websites that aids real-time communication with notifications like Slack, Trello, etc. For others my typical response is "No thanks!".

Is there any other Vanity Metrics that you think the author has missed? What is your experience?

My primary reason against Tests for CSS, is that CSS is not about business logic. And the other being that the way CSS works is the last run CSS styling over-rides the previous one. Unit-testing eh? The order of CSS styling that is applied depends on the order of inclusion, correct? Now write anaother test for this? All these thoughts, made me laugh at the idea of Testing the CSS back then. All said, I was still curious to know what was the positive/negative experience of those who tried it.

What has been your bad experience that changed your decision of working for a particular startup? It could be that you've discovered this during your interviews with the folks in the company or later when you were actually working.