fadzlan
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.
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.
ie. if its not favorable for MS, maybe they just want to ditch the country too?
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.
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.
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?
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.
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....
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.
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?
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.
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.
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.
Would save some money too.
Does AGPL prevents some company creating Github like services for Pijul?
MySQL handles it differently than Postgres, and gives them better performance for their purpose (based on their experience/test). They were explaining it in the parlance of the terms that MySQL and Postgres. If those are buzzwords, then MySQL and Postgres are both created using buzzwords?
Their explanation is not perfect (for me, why do their datamodel needs massive updates?). But I wouldn't write it off as buzzwords and dismissing Postgres because of data corruption. There are a lot of other things they were trying to explain there.
If you use this on other people's content, that doesn't really make any sense. Audio is not tech, its highly personal and you can't plagiarize the whole thing and claim it your own when the dude in question doesn't sound you at all. And unlike video which might present various things, podcast mostly centers on the presenter itself.
In other words, it kinda defeats the purpose to use this tool as a plagiarism tool since most podcast is created to create a following, around the presenter's voice.
Turns out that I was not typing on the keyboard, but was pounding on it. Later when I change the nature of my keystroke to be more mild, it starts getting better.
Not sure if this will be relevant to you, but its worth a try.
Amazon staff can think this is not serious as its sound, this is just a drop in the ocean for the company.
It maybe easy to fix, but if its not communicated properly, it can go both ways for the customer, so yes, it can be serious, unless Amazon confirms that its not.
Since the site does not hold the copyright (and rightly so), the site owner does not have the rights to say what can be done with the data. That belongs to the users that generates it.
In that case, how do we know if all the individual users consent to the scraping? If you scrape 10,000 data, and one user complains, would you be in trouble? And does the user has the right to know who are accessing the data outside of the normal use (since if they don't know, they can't object)?
This is more like leaving the world?
As much as they can read the traffic, they can't spoofed the identity. Not without having their own root cert on the customer side.
I had a case where we had our own internal framework. Its okay. But the team turnover is quite bad to an already tight deadline that I had to re-explain everything every time a new dev comes in. That framework has no routing(its basically for multipage app) and guess what, if someone decide that they need routing, that guy is going to create his own, and there might be two of these guys, so then we have two ways of doing routing then.
And given the fact that this team has high turn over and tight deadline, I don't think you can say that it'd make a cohesive team, and the communication channel that everyone has is already overloaded (loads of meetings).
Sure, that may be a bad project to begin with, but that would be a different story.
In this case, at least for me, using a standard framework would be no brainer.
As for preferring library over frameworks, sure why not. There are tons of reason to be able to do things other than the way that is described by a framework, but when you start to have teams bigger than 20, of different time zones, with varying skill level (important point here), having a prescribed way to do things may not be such a bad thing. There will be time to break the rules of the framework, but hopefully your choice of framework is good enough that it should only be less than 10% of the case.
To this, I can say that despite the failing of AngularJS, some teams just cannot live without it. Its very prescriptive to the point that people who a very good at Javascript may find it repulsive. But those prescription are just too robust for some team to abandon it and go for a more performant framework.
And there is a lot of companies that can't hire Google level developers. These people may not know Javascript enough, but are okay as long as there are good prescriptive example of how to do things. They should still aspire to be good at Javascript (or any language at that...), but sometimes that seems to be too much to expect for the portion of them. Sure, this is not ideal, but you have to remember, there are a lot of places in the world that IT is a cost center.