EPTAt work I would be totally at loss without stash, rebase, checkouts (of single files and to different branches), cherry-picking and the like.
The Big Programming Thread - Page 955
| Forum Index > General Forum |
Thread Rules 1. This is not a "do my homework for me" thread. If you have specific questions, ask, but don't post an assignment or homework problem and expect an exact solution. 2. No recruiting for your cockamamie projects (you won't replace facebook with 3 dudes you found on the internet and $20) 3. If you can't articulate why a language is bad, don't start slinging shit about it. Just remember that nothing is worse than making CSS IE6 compatible. 4. Use [code] tags to format code blocks. | ||
|
Manit0u
Poland17448 Posts
At work I would be totally at loss without stash, rebase, checkouts (of single files and to different branches), cherry-picking and the like. | ||
|
Lmui
Canada6215 Posts
Repositories that scale to thousands of users. Branches for different release streams ex. Nightly, Weekstone, RC, Stable and various patches/releases on those codelines. There's dozens of other reasons to have a good working knowledge of VCS Something that works when you have 4 people working on a project for a month doesn't necessarily scale when done for hundreds of people working across multiple timezones around the world. Also, being able to back out changes as well - recent example from work was someone used a third-party library with a license that legal team said we couldn't use - we could easily remove all the content used in that workstream. | ||
|
WarSame
Canada1950 Posts
On April 12 2018 09:08 berated- wrote: Ideal is a bit weird, as deployment is so culture related that it's hard to say... Our company is using it as this.. I don't use docker in my development environment except to run databases. It's too much of a pain to try to get in and out of the container or mapping mounts for my liking. However, running the database in a docker container so it can be local is fantastic (especially considering they have a sql server on linux image). If you had a large toolchain that is needed for a dev environment I can see how it's attractive to want to use docker for dev though. One of the strongest selling points of docker is that it gives you the ability to move the exact container between different environments. The container you built in your ci loop, is the container that goes to dev, qa, prod. Not that your setup doesn't work with rebuilding the container, but, trying to extract your configuration out of the build and then pushing the container through the deployment phases just means you're probably more likely to make sure that what you tested in the environment was correct. This is used pretty often with CI/CD. If you're using deploy branches and actually rebuilding you may not get as much advantage at of this. We also use docker as a part of our gitlab ci loop. When the gitlab pipeline kicks off it spins up a docker builder that has our tools on it to build our applications. It can link in databases, or even selenium servers to run your automated tests against, or any external service that you might have depended on a vm or dedicated server for. Kubernetes and swarm come in for orchestration -- if you are using microservices and need to get each of the different containers communicating with each other, these tools make it a lot easier to pop up a set of microservices that comprise a full application. Our main website could end up using anywhere from 6-10 services that make up the one app. Trying to "deploy" the entire thing manually is a lot of effort where as those tools make the whole thing a lot easier. Kubernetes can also do a ton of stuff with controlled rollouts and versioning and ingress controllers and a whole bunch of stuff that I don't even fully understand... Docker is really cool, but, the entire community is still pretty young and things are changing very rapidly. It's definitely buzzwordish but unless you are deploying quite a few application instances it's a lot of overhead for not a ton of gain... except for running your databases in dev on your machine, that's a life saver. Thank you for the response. I think given what you and others have said I will keep my Docker usage very simply and start using things like Swarm or Kubernetes when that becomes necessary. I wanted to provide a good DevOps foundation for my project(and to learn this stuff), but it seems there is more to learn than I can justify with my time. | ||
|
Deleted User 3420
24492 Posts
do any of you pay for private accounts? | ||
tofucake
Hyrule19158 Posts
| ||
|
emperorchampion
Canada9496 Posts
On April 14 2018 00:00 travis wrote: thanks for all the replies! do any of you pay for private accounts? As a student you can get a lot of free benefits from github (including free private repos). | ||
|
Manit0u
Poland17448 Posts
On April 14 2018 00:24 tofucake wrote: I don't. If I want to keep something private I put it on BitBucket. +1 | ||
|
Excludos
Norway8192 Posts
+2. Bitbucket works really nice for private projects (We use Bitbucket for all work related stuff), and it can be integrated with a lot of other stuff. Github should be filled with personal projects for future employers to have a look at tho. | ||
|
sc-darkness
856 Posts
I see that std::string is somehow magically "UTF-8 ready" on Linux. On the contrary, Windows prefers std::wstring for unicode. Yet, std::wstring is 4 bytes on Linux and only 2 bytes on Windows. How does that make std::wstring less desirable on Linux? Why? Clearly wstring is larger so it could hold more characters? And why is this fucked up on an OS level? I just don't understand all this mess. Link: https://stackoverflow.com/questions/402283/stdwstring-vs-stdstring?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa Edit: Are we meant to use these now? 3) UTF-8 encoded string literal. The type of a u8"..." string literal is const char[]. 4) UTF-16 encoded string literal. The type of a u"..." string literal is const char16_t[]. 5) UTF-32 encoded string literal. The type of a U"..." string literal is const char32_t[]. | ||
|
Excludos
Norway8192 Posts
The gist of it is: Windows doesn't have unicode in std::String, but Linux does. wstring doubles the size so you can fit in more characters, but on Linux it already has all the characters, making it larger for literally no reason. That said the 2/4 bytes as mentioned in the stackoverflow post should definitively be wrong, as 4 bytes is the required minimum for full unicode, while 2 bytes will only give you ascii. So those numbers are probably for string, and not wstring. edit: should also mention that wstring will still work on Linux, and size doesn't really matter that much these days unless you're programming for a potato. So if you're making a program which is suppose to compile on both windows and linux, then you'll want to use wstring (or, like I said: Literally anything else) | ||
|
nunez
Norway4003 Posts
a glass bowl is an abysmal implementation of fruit salad. one of the many reasons is that it doesn't contain pieces of fruit. you need to like put it them in there yourself. | ||
|
Excludos
Norway8192 Posts
On April 19 2018 04:08 nunez wrote: you guys very confused. i suggest getting comfortable with the concept of a class template, and then return to trying to understand what std::string and std::wstring is. they are totally independent of any semantic attached to their data. a glass bowl is an abysmal implementation of fruit salad. one of the many reasons is that it doesn't contain pieces of fruit. you need to like put it them in there yourself. This is so unreasonably unhelpful for anything that was ever stated I wonder why you even bothered. It's so vague I can't even fathom who you're answering or what about. | ||
|
nunez
Norway4003 Posts
| ||
|
sc-darkness
856 Posts
On April 19 2018 04:12 Excludos wrote: This is so unreasonably unhelpful for anything that was ever stated I wonder why you even bothered. It's so vague I can't even fathom who you're answering or what about. He refers to this popular idea of treating std::string like a dummy container of characters (very much like binary serialisation where you have to know how to treat data?). It's usually recommended to treat it as UTF-8, then you convert it to wide strings when you deal with Windows API. You have to do conversions in both directions. Also, if you need string manipulation (string.find, string.at, etc), then wide strings are preferable. He said it in an asshole-ish way, but I'm not surprised considering what kind of horrifying C++ code he posted here in the past. I'd definitely avoid his code style, but it seems he isn't good at explaining concepts either. Edit: I re-read post about wstring and string on Windows and Linux. It's indeed a very fucked up thing to deal with. We suffer because of backwards compatibility support for code pages on Windows where ANSI string could be interpreted in different ways depending on if you have cyrillic Windows, Asian Windows, western Windows, etc.. Otherwise, std::string would have been fine both on Windows and Linux to deal with UTF-8. Fuck backwards compatibility. Let applications break the hard way so they are encouraged to switch to Unicode instead. | ||
|
WarSame
Canada1950 Posts
Android reference for KeyGuardManager Sample Activity How? It needs user input, right? How do you test that? | ||
|
Silvanel
Poland4733 Posts
If You want to test with real user input You are doing functional and/or component tests, not unit test. I know its not really helpful but as a tester i like to be precise with a vocabulary. | ||
|
Artesimo
Germany564 Posts
 And yes, thats a quote which I got in response to me trying to convince someone how fun Mockito is for (java) testing. | ||
|
Excludos
Norway8192 Posts
On April 20 2018 23:32 Artesimo wrote: Testing is for people who code too weak so they have to check if it works anyways And yes, thats a quote which I got in response to me trying to convince someone how fun Mockito is for (java) testing. Or the quote my boss gave me when I told him we desperately needed to implement some unit testing in our consistently breaking system. "You should have just made it better to begin with" and "We don't have time to do testing right now, the system needs to work first". The irony of the last statement was lost on him. On a completely different topic: I'm starting in a new job next week xD | ||
|
Manit0u
Poland17448 Posts
Their API is behaving really weird recently. We have everything configured, region set to 'eu-central-1', endpoints are correct, buckets are fine, presigned urls are generated properly etc. The problem arises when you try and call ".exists?" method on the AWS object. It returns AWS::S3::BadRequest error every time. I've managed to capture and fully analyze one such exception - its stack trace was useless and it had no message, instead it had this huge context object attached, which had a ton of other object inside. Anyway, I've managed to get down to the requests and responses that this API is sending behind the scenes (it's Amazon's library, not our own) and it appears that request headers refer to credentials as being on 'us-east-1'. I've checked and nowehere in our entire system do we mention 'us-east-1' region for S3... Any idea what could be going on here? Looks like some stupid defaults but I see no reason for them to be set since we explicitly set all the variables in AWS config... I remember that they mentioned something about newer version of their API requiring region and endpoint to be set, but we did that already. | ||
|
sc-darkness
856 Posts
It's really annoying that there is no standard UTF variant to use. Windows prefers UTF-16, while Linux and maybe HTTP prefer UTF-8. Edit: CreateFileA doesn't seem to work with UTF-8 then. | ||
| ||
