fadzlan

The point is how should such code grows? If it meant to grow on its own, separately on different requirements, then its not duplication. It's just a code that looks the same, for now.

Everything comes with a price. The Clean Code book basically argue on one side, on what you can gain with such practice. It's not gospel, its something that argue on benefits on certain practice. As a developer, you probably are more privy on what is a better trade off based on your project. Do what make sense.

You may default on writing "messy" code, or writing "clean" code, before you find the middle ground that make sense, and thats okay. Its a journey, not a destination. It takes experience to make a good trade off in your daily coding.

Learn from your mistakes and move on.

> Another point is that you can’t expect to get that caliber of TV for that price without ads.

Just want to understand the argument. Not using any smart tv at the moment, maybe in the future, we'll see.

So we should expect ads on expensive TVs now? USD 1500 is very expensive for me at least. I was expecting something good but cheaper to be subsidized by ads, not the really expensive ones.

What I don't understand from here is that even if MS were to take over, wouldn't they be restricted under the same law?

ie. if its not favorable for MS, maybe they just want to ditch the country too?

The extension by design is made to be optional to use and are not integral (I would argue) to the vanilla experience of VS Code.

That also means that if other people wants to create their own proprietary extensions they can do so. The basic experience of the plain VS Code does not change.

Now one can say indeed that the Remote and also LiveShare is the best extension there of, and since the extension author decides not to share the code, then it stays proprietary. It's just that this time the author is Microsoft itself.

But because the extension itself is not integral to the VS Code itself and merely an extension, there is no stopping anyone to create open source version of the same experience.

However, where I have issues with is that, if you were to base you own editor with VS Codium (the open source, without the telemetry), you still can't use the service that is the extension marketplace for VS Code. Yes, even if it still works, and even if the extension itself is open source. Hence, just because VS Code has a lot of extensions that is open source, does not mean it is readily reusable, because the extension service is off limits.

Of course, one can also publish the same extension in another public directory if they want, but currently there is no such directory exist. And it has to be republished to the new public extension directory.

So yes, VS Code is open source, but the access to the extensions is not currently.

The diagram can be part of documentation of the code in the the same working directory, possibly version controlled.

It is going to be very useful to be able to just edit the diagram within the same editor as the rest of the files in the same working directory. You just double click the file in VS Code, and it opens there.

I am looking forward for the completion of the PNG part so that it is even more seamless.

Being nice is not scalable when you are dealing with potentially the whole world.

It's like any celebrity with a twitter handle, they now have to have template twitter reply or its not acceptable?

It's one thing when you have to deal with the support cases in your company when there is hard limit on how many people will be in touch with you. When you are releasing things to the world, there is no such limit. It can be one, it can be one thousand.

I too would like to have something open source one day, if I have something that I think can benefit people. I may not have time to respond to people, given my life and my health, so because of that I should not contribute? And if I did contribute in such circumstances, it is completely unacceptable?

Copying the comment I made on the site :-

The thing about writing test, either unit test or functional UI test, is repeatability. Back then I had this problem too, to which I had worked on getting a script to drop the database, and recreate it back again, repopulating it with consistent test data.

Then, docker-compose came along. It is so easy right now to just have an environment up and running consistently. And once the test is done, the whole container set of the docker-compose can be easily removed, and created again on a whim.

For most database containers, you can just attach your sql files into the volumes that the database engine reads, and you will have consistent test sets overtime.

This will solve :-

1. Running test again and again, will make certain elements go of page because of pagination. 2. Creating new data with the same data to ensure uniqueness and testing it, can be done, because it will be a clean slate everytime. 3. Previous data causing inconsistent state with the current test

This does not solve every issue with functional UI testing, but in my experience, having consistent data every time is huge! No more second guessing when you write the logic in your test in fear of having existing data or any manual testing data breaking your test.

There is something like this in Malaysia as well, under the previous government. The way that some people deal with this is make everybody admin.

I understand that if the test hits database, then its an integration test.

But what if a whole load of the logics are in stored procedure? Surely those needs test too.

Of course, one can make an argument that depending too much on stored procedures is an anti pattern....

I would agree that going for a vacation to run away from things can make things worse.

However, if one can decide to go for a vacation to get a fresh perspective on the issue, I think that would help. Getting to a place where there are no interruptions expected may help you doing that if that is your intent.

Being in the office may keep you doing the daily firefighting and you may need space to think differently.

My thought exactly. I was like yes of course!

How does he think that desktop app can do many different things?

Now, sandbox is a different issue. But of course, yes it have access to the screen.

If apps on desktop is going to be as restrictive on mobile, why use desktop at all?

Based from what I read of the article, its more about SQL the query language instead of the normal ACID compliant RDBMS over NoSQL databases.

Of course, having a common query language is a big advantage, but NoSQL varies in paradigms and implementation due to the subset of problems they choose to solve, thus having a standard query language does not make sense for NoSQL.

Oh yeah, I have my shortest stint in one of those company.

It was rumored that the company I was working had taken poison pill last time by having the ratio of benched workers and assigned workers to 50%:50%.

Their presence in our country was small, but they have multiple office campuses in India. One campus even have a separate building that if you walk to that building to work, people know you are benched.

Compared to other company that I worked, one of their value proposition is to have resources readily available if you want to start a project today, apart from having a dirt cheap offer. So yeah, benching a lot doesn't come as a surprise to me about those companies.

> If you really, really need to poke holes into your firewall can easily that with ssh to a cheap vm hosted at your trustworthy hoster. If ssh ain't enough, nc and socat are your friends.

Wouldn't that still be the same, considering ngrok is just doing the tunneling. In this case, ngrok is your trusty hoster. You can park your trust into your own VM in Digital Ocean, or you can park it at ngrok.