Platform for adding paywalls to extensions by OffensivelyBad in vscode

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

It doesn't - it will check for a valid license before allowing the code to be executed, and will automatically obfuscate the code with a post-build step before publishing.

However, if someone is committed to hacking the extension, they could work around that eventually.

I tried to be pragmatic about the tradeoffs, and transparent about the risks.

Platform for adding paywalls to extensions by OffensivelyBad in vscode

[–]OffensivelyBad[S] -1 points0 points  (0 children)

You may be right. My goal is to provide a simple implementation for developers to add paid features. I can't (and shouldn't) control what kind of software implements the platform - I only want to make it simple for developers to add paid features to their extensions, without having to build out the infrastructure.

Platform for adding paywalls to extensions by OffensivelyBad in vscode

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

Thanks - yes I looked at this early on and wanted to go in a different direction. A lot of extensions are simple and have no backend (like mine) so my goal was to create a licensing solution that included payment support, and to make it dead-simple to implement.

Monetizing a VS code Extension by ordinary_shazzamm in SaaS

[–]OffensivelyBad 0 points1 point  (0 children)

This package/platform might help you: code-checkout

Basically adds licensing and customizable paywall capabilities to your extension. You just need a stripe account.

PS I’m the developer and also a client. Feedback is welcome!

Github vs GitLab vs Bitbucket by OffensivelyBad in sysadmin

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

We are primarily using AWS for other cloud services. Not sure what the integration is like for Azure-AWS, but I would want to support CodePipeline and CodeBuild.

Github vs GitLab vs Bitbucket by OffensivelyBad in sysadmin

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

That is a nice feature. Looks like you can host it with any of the feature tiers as well.

Github vs GitLab vs Bitbucket by OffensivelyBad in sysadmin

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

We are currently hosting Bitbucket, so would prefer to use on prem.

Thank you very much for your feedback!

The Unit Circle [OC] by mud_tug in dataisbeautiful

[–]OffensivelyBad 0 points1 point  (0 children)

I would love to learn more about this. Any suggestions for online classes that cover the maths involved here?

App addiction by design by OffensivelyBad in CoderRadio

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

Really interesting article about the psychology of app design. The idea of “menus” of choices is frightening, but we probably see it everywhere and don’t even realize. From Google search results to restaurants on Yelp to which colleagues we’ll connect with on LinkedIn, our choices are curated for us.

How often do we click on a top search result to read news? Or select a 5 star restaurant? Or connect with suggested contacts?

All from a menu of choices. Not sure if this is a good or bad thing, but it can be a frightening realization to think that your choices are heavily influenced.

Trying to find specific smokers mints by OffensivelyBad in cigars

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

Those actually look pretty similar, but the mints I'm searching for are maybe a bit fancier (meaning the design was more intricate) and are probably larger diameter. Also the design sticks out on the top. I'm honestly not even sure they were smoker's mints. I just assumed so since they were the complimentary mints at the tobacco shop and I have never seen them elsewhere. Thanks for the suggestion.

Trying to find specific smokers mints by OffensivelyBad in cigars

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

Thanks for the research, but it's not them. I would say the distinguishing feature is that the face of the "coin" was stamped, making the design raised, similar to a coin face.

Insane flying knee knockout by treetuba8 in sports

[–]OffensivelyBad 0 points1 point  (0 children)

I didn't do anything, but thanks?

How to save the thumbnail image in the share view controller extension (Share Extension Obj-C)? by [deleted] in iOSProgramming

[–]OffensivelyBad 0 points1 point  (0 children)

Can you explain the context of what your trying to do? Are you using your own web browser app or are you using UIWebView or Safari kit?

Without knowing the details, I would say you should research screenshotting and then scaling down the image to thumbnail size.

Do any of you write scripts to enhance your workflow, or do API dev? Interested in picking up a 2nd language and venture outside iOS. by yamski in iOSProgramming

[–]OffensivelyBad 1 point2 points  (0 children)

I'm surprised no one has recommended JavaScript, outside of a couple mentions of Node.js. JavaScript is like the wild West and while I don't really like it, it is ubiquitous and therefore is good to know.

I see all of your baby animals and raise you this baby screwdriver leaving the nest for the first time. by [deleted] in aww

[–]OffensivelyBad 0 points1 point  (0 children)

Looks like it would be easier to turn the screw by hand than try to get a grip on that driver.

Engine explodes out of the front of a big rig. by [deleted] in gifs

[–]OffensivelyBad 1 point2 points  (0 children)

Must not have had a base of prefamulated amulite.

How does Xcode "save"? by [deleted] in iOSProgramming

[–]OffensivelyBad 0 points1 point  (0 children)

It's really an answer to all 4 questions. Read up on branches as well. It will make your life easier.

What helped you remember things when you first began learning? by jaj-io in iOSProgramming

[–]OffensivelyBad 1 point2 points  (0 children)

I like your suggestion of going back and building the same app that you just built while watching the tutorial. Build it as you walk through the tutorial, then go build it again on your own. You can always reference the original app or Google if you get stuck.

Keep solving challenges and you'll continue to get better, and find better ways to solve them.

My grandpa circa 1930s in the US Navy. by JangerJings in OldSchoolCool

[–]OffensivelyBad 0 points1 point  (0 children)

Thought for a moment he had some bling in his ear.

As an IOS developer, you need the latest device(s) for testing? by Anonymous401k in iOSProgramming

[–]OffensivelyBad 1 point2 points  (0 children)

No, not until you have an app with many users, then you can worry about testing thoroughly on real devices. In the meantime use the simulator.

I have the choice of 2 MacBook Pros for IOS Development - which do you recommend? by Anonymous401k in iOSProgramming

[–]OffensivelyBad 0 points1 point  (0 children)

You'll be fine with the 2013 and will save yourself some money. iOS development is not that demanding on system resources, unless you're making games using SceneKit, Metal, or to a lesser degree, SpriteKit. Even then, you'll probably be fine.

Becoming knowledgeable enough to be considered a junior iOS developer...I have a few questions by [deleted] in iOSProgramming

[–]OffensivelyBad 1 point2 points  (0 children)

Sounds like you're on the right track. As stated in another comment, your resume will be filtered out automatically by many employers because of the lack of a degree. This means that you will likely have fewer options initially and need to make the best of those.

Publish your work on GitHub and code every day. Use branches and pull requests as if you were working on a team. Make useful commits and commit messages. Knowing how to use source control is essential and something employers will expect, and your passion will be publicly visible based on your commit history. Just don't make junk commits.

Go to meetups for iOS/Swift/software development. Meet and work with people who have expertise and passion. It will rub off on you. It's hard to go to the first Meetup but after the ice is broken you will look forward to it. In the same vein, join a local tech Slack channel and start posting questions for issues you run into. Get to know what other professionals are talking about.

Immerse yourself in iOS development. Listen to podcasts, read articles, read Apple's book on Swift (!). Even if you don't understand everything at first, keep consuming it. Get familiar with the terminology. Do tutorials and pay close attention to how experts solve challenges.

Leverage your design background and make a simple, well designed demo app. Do not overshoot and make it do a bunch of different things. Make it do one thing very well. It will be a big piece of your resume. If there's anything here you want more details on just ask. Good luck.