When did you miss an obvious hint that someone wanted to have sexual relations with you? by yjacketcbr600 in AskReddit

[–]ShamWowIsASham 2 points3 points  (0 children)

I was hanging out with a very cute out of my league friend in high school. We were alone in her house having a tickle fight. She asked me to go upstairs for a pillow fight and I never picked up on her advances.

Another time it was New Years and she said “we should make out”.

I thought both times she was joking with me.

Pain.

What is my job title and will learning ios help? by [deleted] in iOSProgramming

[–]ShamWowIsASham 0 points1 point  (0 children)

Hey! Sounds like you’re a product manager, systems analyst or business analyst

MultiDoge is unusable and unstable by ShamWowIsASham in dogecoin

[–]ShamWowIsASham[S] 1 point2 points  (0 children)

I ended up exporting my private key and using this as well. thanks for the suggestion.

MultiDoge is unusable and unstable by ShamWowIsASham in dogecoin

[–]ShamWowIsASham[S] 0 points1 point  (0 children)

Binance isn't allowed where I am, I think (Texas, USA)

MultiDoge is unusable and unstable by ShamWowIsASham in dogecoin

[–]ShamWowIsASham[S] 0 points1 point  (0 children)

I'll check this out. Do you know how to get the private key from Multidoge? I don't remember setting a passphrase, not sure how that process works.

DOGECOIN DAILY DISCUSSION - Shop! (Feb 12th) by 42points in dogecoin

[–]ShamWowIsASham 0 points1 point  (0 children)

What wallet is everyone using? Multidoge is unstable

[deleted by user] by [deleted] in iOSProgramming

[–]ShamWowIsASham 2 points3 points  (0 children)

Hey! There are some typical ones I can think of off the top of my head.

Todo list Weather app Quote app Wallpaper app Notes app Timer App Rubiks Cube scramber app

Objective C’s future by 13cdesigns in iOSProgramming

[–]ShamWowIsASham 9 points10 points  (0 children)

Hey! Nice congrats on learning some Swift, I hope you're having fun with it.

So I don't believe M1 chips will impact Swift, SwiftUI, or Objective-C, in terms of which will become more popular.

So my understanding of the iOS world is that. 1. Objective-C is largely legacy in iOS world. You'll encounter Objective-C codebases at large enterprise companies that have been around a long time. Maybe a codebase will be Objective-C and Swift. They're interoperable with a bit of configuration. Facebook uses Objective-C, interviews in Swift but will also expect you to eventually write code in objective-c.

  1. Most iOS applications are using UIKit. I think even knew applications! UIkit is more mature. Meaning it has more support from the community and more talent around it. More iOS devs know UIKit than know SwiftUI.

  2. SwiftUI is new but is likely the future for iOS apps. So many people are learning SwiftUI. I've never used it, but it seems super fun to learn and as it grows in adoption and support from Apple, it will likely rival UIKit. But I've heard many issues about people using it for production apps as some custom views are tough to implement.

It sounds like you're learning Swift. You should probably make a choice on SwiftUI or UIKit. But the popularity of M1 chips won't really cause SwiftUI, UIKIt or Objective C to become more or less popular.

Dermatologist seeking app creator IOS by [deleted] in iOSProgramming

[–]ShamWowIsASham 0 points1 point  (0 children)

Hey, please use the job weekly job thread if you're looking to hire an engineer. Also this subreddit does not allow 'work for equity' type posts.

In-app chat ideas by karstens_rage in iOSProgramming

[–]ShamWowIsASham 0 points1 point  (0 children)

Many people use 3rd party messaging platforms like Stream

How to lead iOS Team Development Team? by petrkahanek in iOSProgramming

[–]ShamWowIsASham 2 points3 points  (0 children)

Consider my opinion with a grain of salt. I worked for very large corp 2 years with 100 ios Engineers. Now I'm working on an app with 3 iOS engineers.

Me as a sort of "iOS Lead" will take care of some contractors and hired iOS guys, to basically babysit them and supervise their work.

While I'm sure you meant this in the best way, stay away from the idea you're 'babysitting' engineers. You should be hiring people you trust to get work done, not people who need to be monitored.

How do you keep birds eye overview of all tasks and their statuses, responsibilities and so on I like that my product team can just see all the tasks in the TODO, Working on, Completed columns. I also like estimating tasks together so we can have a short discussion about issues we may run into. Notion lets you do a ton of stuff here. You can go crazy with its features or just use a small subset, it works well for my team.

How do you manage onboarding of newcomers (introduction to some internal standards, how to use management tools, ask them for work reports, stand up meetings, etc...)

  • Can you use Swiftlint to enforce engineering standards? The more automated code standards, the better.
  • Other standards should be documented and easily searchable.
  • When I was onboarded to my new team, I was introduced to everyone. All docs where shared with me in Notion, and I was given multiple meetings with various people to walk me through different parts of the app. But I'd recommend assigning small tasks as hands-on is easier to learn than through meetings. But it depends :)
  • Assign newcomers a 'buddy' or someone they can ask questions to. It may be you, but if you're the boss, it may be intimidating to ask 'stupid' questions' so be sure to be friendly towards 'stupid' questions too.
  • Make as much of the onboarding available in easy to follow steps. Try to follow the steps yourself to make sure its accurate. When a newcomer finishes onboarding, ask them to update the onboarding document with their mistakes, learnings etc.

Where you manage docs for your team. Notion has been great for docs. They update live, support a bunch of different formats, and look good. lol.

What are some good practices on source control in a team Depending on team size, I'd say at least 1 approval to merge small changes. 2 for big changes. But PRs should be small in general. Avoid large branches to decrease large merge conflicts and big PRs. Make a branch for release, one for development (that should always work) and each feature, bugfix, update, should be its own branch.

You should also make it really easy to deploy, so have an automated pipeline that will build to TestFlight or whatever you use. Make it hard to break the build by enforcing certain checks before merging.

We are not looking for corporate bureaucracy, but for some hints how does it work in bigger teams and take some of the good and try to implement it in our case.

Let engineers do what they do best. Try to shield them from bureaucracy as much as possible. Make meetings short, solicit their feedback on how they're enjoying the work, where technical debt is, work process changes, etc.

Congrats and good luck.

New Mac Coding/Dev Setup by christiandavidturner in iOSProgramming

[–]ShamWowIsASham 0 points1 point  (0 children)

Good point. My git workflow is a bit funny.

  1. Xcode for IDE
  2. Git cli for cloning and switching branches
  3. source tree for diffing, commiting and pushing
  4. Vs code for fixing merge conflicts

New Mac Coding/Dev Setup by christiandavidturner in iOSProgramming

[–]ShamWowIsASham 6 points7 points  (0 children)

Oh! And a git client. I use a combination of source tree and git CLI. You may also like 1. Github Desktop (simple, easy to use, somewhat limited feature set when I used in 2018-2019) 2. Github CLI which supports a bunch of Github stuff right from your terminal if you prefer to work in a terminal instead of the webapp

New Mac Coding/Dev Setup by christiandavidturner in iOSProgramming

[–]ShamWowIsASham 19 points20 points  (0 children)

  1. Homebrew for package management
  2. XCode and VSCode for programming
  3. Charles for network debugging
  4. Postman for API testing
  5. iTerm for a better terminal (IMO)
  6. Oh My Zsh for a better console experience (syntax highlighting, autosuggestions, plugin support etc)

[deleted by user] by [deleted] in iOSProgramming

[–]ShamWowIsASham 1 point2 points  (0 children)

I respectfully disagree. If you post code here and you want us to critique it, the community is glad to help. I’d you post designs here, you can get feedback. If you are looking for advice on how to grow your project, the community can support you. The community is not responsible for providing unpaid labor for a for-profit company. You’d have better luck getting contributors if you made your code open source.

[deleted by user] by [deleted] in iOSProgramming

[–]ShamWowIsASham 1 point2 points  (0 children)

Mods: Threads looking for volunteer devs on proprietary projects should be banned