I started as a graphic designer and moved towards web dev. Definitely something done with a vector graphics editor, like Illustrator, or Sketch, etc. I’ve even seen some amazing parallax done with them. firewatch parallax
Set up your Raspberry Pi and router and your entire home network will be ad-free. No need to tamper with individual devices, no iPhone jail-breaking etc.
I made an Android app using modern web technologies (ES6+, Webpack, React) and bunded it using PhoneGap. It's a companion guide for a game (Stardew Valley). It's quite simple, and a bit niche, but if you play the game it's genuinely useful.
After Google's cut it is currently bringing in about £300 per month, so after tax that's about £200. I'm pretty pleased with that to be honest.
Also, PhoneGap is awesome - I've really enjoyed using it. I've set up a template that makes it really easy to get started quickly, which includes PhoneGap, the Webpack / React / etc. stack that I prefer to use, some scripts, and a React-focussed Material UI framework. Feel free to check it out if you're interested in using PhoneGap to create Android apps.
I built a product to track web site changes. Built it 10+ years ago in Perl (yikes)! It grew very very (very) slowly w/ only minimal upkeep, and only recently have I started focusing on it full time. It eventually grew to where it supports me fulltime.
I recently built another vertical-specific version 100% on Node.js Lambda functions w/ a React front-end. I control all infrastructure using CloudFormation. It's a pretty sweet setup. Cool beans.
Yep, you can watch the network tab in dev tools to see it making calls to get a json file like this:
The response is a data object containing markdown that gets rendered out as the content so there's virtually no delay when navigating between pages on their site. Definitely a nice way to reduce your perceived load times.
> What drives me crazy is that ever since my first job I've realized that as a developer, I usually average about two or three hours a day of productive coding. When I had a summer internship at Microsoft, a fellow intern told me he was actually only going into work from 12 to 5 every day. Five hours, minus lunch, and his team loved him because he still managed to get a lot more done than average. I've found the same thing to be true. I feel a little bit guilty when I see how hard everybody else seems to be working, and I get about two or three quality hours in a day, and still I've always been one of the most productive members of the team. That's probably why when Peopleware and XP insist on eliminating overtime and working strictly 40 hour weeks, they do so secure in the knowledge that this won't reduce a team's output.
http://codepen.io/anon/pen/ZQvOWK
.modal { position:absolute; left:50%; top:50%; width:50%; height:50%; transform: translate(-50%,-50%); background:#ccc; }
Depending on what you're trying to do, sometimes transform:translate();
can be amazing.
I've worked in SEO since 2005, I work solely in development now but for 12 years that was my career focus
Whatever you read/do make sure it's up to date
Tactics that used to work in SEO 5 years ago can get you penalized and worse ranking in the search results
Use google's lighthouse tool to see what google wants you to improve on the website...doing so isn't easy depending on the age of the websites stack
Regardless of the above, you aren't likely to drastically improve rankings for a client without link building, content creation, and an overall website hierarchy to point google to your most important pages
Not a bad choice depending on your type of implementation. You can opt to only import/include the CSS which you're using, rather than the whole package. https://getbootstrap.com/docs/5.0/customize/optimize/
If you don't know about it yet, let me introduce you to a webdev's best friend... press F12 and use the dev tools to point to the element and see how they did it.
Then go into the head section within the dev tools, and open their css and js files, and look for elements with the same classes and/or ids. You can also see the css files used in the dev tools next to the element in cases of multiple css files and needing to figure out where that style is applied.
You can then use a free code playground like JSFiddle.net (which I prefer) or CodePen.io and use what you find to try and replicate it or change it to your needs.
It's really a great way to learn.
You can even link the jsfiddle or codepen page you are working on, as well as an image (like you used here in this post) or a website where it's located, and ask in forums like here for help in getting your code where it needs to be.
Your solution is not optimal, it uses 100% of my chromes thread on a 4.2GHz CPU and has like 2 FPS when scrolling. I think you have to come up with another solution because this is going to consume a lot of battery on mobile/tablet devices.
From WebKit Wiki: > Sometimes it's tempting to use webkit's drawing features, like -webkit-gradient, when it's not actually necessary - maintaining images and dealing with Photoshop and drawing tools can be a hassle. However, using CSS for those tasks moves that hassle from the designer's computer to the target's CPU. Gradients, shadows, and other decorations in CSS should be used only when necessary (e.g. when the shape is dynamic based on the content) - otherwise, static images are always faster. On very low-end platforms, it's even advised to use static images for some of the text if possible.
EDIT: To add more value to my response, could you perhaps instead dynamically add the blurred overlay to an image using something like ImageMagick or if your images are static, just add the blur directly onto the image?
Nah, they ~~moved~~ are in the process of moving to gcloud now https://about.gitlab.com/2018/04/05/gke-gitlab-integration/
> We’re already in the process of migrating GitLab.com to Google Cloud Platform. For us, the primary reason to migrate was because it has the most mature Kubernetes platform.
Had they stayed with Azure, the irony would had been so good though
https://www.digitalocean.com/community/tutorials/new-droplet-plans-frequently-asked-questions > In order to decrease impact on existing applications and workflows, these plans are being introduced as completely new plans. This means there is no impact to your current Droplet and these changes will only impact newly created Droplets.
So the pricing changes aren't automatically applied to existing droplets. But you should be able to resize an existing droplet into one of the new plans to get the discount/upgrade.
Coming from Atom, I was looking for an extension for highlighting changed and new git files in the explorer to no avail, and then today they included it in the update. Very cool.
Author of ga-lite here. Thank you for mentioning this, worked hard to get it done :)
P.S. My blog post about the subject scores 100/100 on Google pagespeed:
If you don’t like working slightly against the current and learning PHP (v7 is wonderful), then Jeffrey Way’s Laracasts is an incredible resource for full stack development using Laravel and Vuejs. Even as I’ve become quite competent, I still find myself going back frequently to soak up whatever knowledge Jeffrey feels he needs to pass on.
Remember: There really aren’t any bad languages anymore, just bad programmers. PHP is very forgiving for newcomers so don’t feel like you’re learning a bad language or that just because you aren’t on the Node bandwagon, that you are learning an inferior language. PHP still powers the majority of the internet and will for a long time to come.
Actually, one should also consider using a CDN and possibly not pre-processing the files that could be hosted from a CDN. Even if you don't want to use a CDN, you can still get some of the benefit with etagging. The reason for this is that most browsers and ISPs will have the larger frameworks like jquery cached already (ex: https://developers.google.com/speed/libraries/devguide, or http://cdnjs.com/). By pre-processing the files and creating 1 monolithic JS file, you are most likely creating a unique file that is guaranteed not to be cached for any unique visitor. This means that every unique visitor has to download the entire monolithic file. If you're using jquery, backbone, underscore, jqueryui etc... on a single site, things can add up quickly. Almost everyone has at least some of these cached from one of the larger CDNs these days.
Versioning plays a role here as well. With a single js file, you'll need to reprocess the entire file every time anything is updated. This means that all users will have to download the entire js file again whenever any change is made. By utilizing etagging and keeping the files separate, the client will only download the files that have changed since the last visit (same goes for their isp if it caches, and it's isp and so on). This is very important on mobile where the network operators do a ton to reduce the traffic as much as possible.
As a side note, another common fallacy is that you should always compress your images for mobile. It turns out that this isn't always the case as many times, the mobile isp already does compression and caching. By doing this yourself, you could actually make the file that's sent to the client larger or of poorer quality than what would normally be sent.
It's not as if IE7 isn't a browser and has no HTML and CSS support. You should be able to answer your own question as a web developer. The answer is "don't use features IE7 doesn't support."
http://caniuse.com should help you if you aren't sure.
/u/WrasslorMonkey posted some good information. However, I think using the various tools to "make IE7 support new stuff" could lead you down a path of sorrow and headache. If IE7 can't do something natively, I'd tell your supervisor that it isn't supported or will blow the budget up.
Interesting given Gitlab's recent "Masterplan" post - https://about.gitlab.com/direction/#scope
I love the competition between these two. Gitlab is wonderful for my personal projects but Github obviously has the community aspect to it.
Excited for the Github projects, no longer need 3rd party plugins for it thankfully.
The big thing to remember with reading technical books ... you are not meant to read them like a novel. Often you will have to read sections multiple times until things click. It is not an all or nothing process either. You will pick up knowledge in bits here and there and it will build up with experience.
You might need to take a break and visit a chapter later and some books will literally take months if not years to get through. This is the same whether you are a beginner or an expert.
Take heart from a quote in Code Complete: "You're already learning more than most people in the software industry because one book is more than most programmers read each year (DeMarco and Lister 1999)"
So to answer your question, yes you have every chance of becoming an expert if you persist and take things 1 day at a time. If something doesn't make sense, Google for a tutorial or alternative explanation and bit by bit the pieces will start clicking together.
CodePen link: https://codepen.io/Tepec/pen/aKNeeN
Also, small note: I added a small JS function to enable "swiping left/right" through panels on touch-enabled devices, and some dirty code to enable keyboard arrow navigation as well.
Top tip! As somebody who doesn't use anything Apple, I use a combo of Midori (WebKit-based browser for Linux) and also Appetize.io (has iPhone device testing capabilities) for seeing if my projects actually work on the excuse of a browser. Both are free (sign up for Appetize.io account to bypass 1 min limit) and save you from having to buy a Mac!
> ES2015 and custom elements are now supported in most major release channels
I haven't been keeping up with custom elements, so forgive me if I'm wrong on this.
CanIUse lists custom element support at 50% of users in the USA, with only Chrome and Opera offering full support. IE obviously offers no support and never will, Edge offers no support, and Firefox only supports through changing a configuration value.
Does the author mean "supported with a polyfill"?
.io originates from the British Indian Ocean Territory. It's popular because it's shorter then a 3 letter TLD and because of I/O which is technical, hence the reason why many tech companys/startups go for an .io domain. (Read more about .io being popular)
In the beginning there weren't so much TLD's as there are now (27 pages full of TLD's). It used to be linked to a country and only restricted to those living/doing business in that country.
AFAIK the USA decided to divide it further, .com for commercial, .net was associated with everything network related (ISP's), .org for organisations (non-profit) but these guidelines were never enforced so everyone started using them whenever they liked. I guess today it doesn't really matter anymore if you have a .com or a .net that much.
My answer to OP's question: The difference between having a .net or .com is far less then having a .co.uk or .net/.com. I would go with the .net or try something creative with another TLD (see link above for the possibilities) but be aware, these aren't really common and I guess a normal user could get confused (it all depends on the target audience). ex.: Youtube uses the Belgian tld .be for some links so they have youtu.be as a shorter url.
As of now, this seems to be an experiment enabled by default for a subset of Chrome Canary users.
Thankfully, Paul Irish writes on Twitter:
> this is terrible. From what I can tell only 6 people have been involved in this so far. Going to do my best to stop it.
Experiment or not, Google needs to whacked over the head fast and hard. They need a message that it is not okay to break the most fundamental ingredient of the web, just so they can increase their search volume a bit more.
As zaroth wrote on HN:
> Google heard of this thing called a 'Uniform Resource Locator', and thought, "Hey, that's us!"
https://moz.com/beginners-guide-to-seo
Sign up for the free trial, you'll learn loads if you put the time in. No need to subscribe to their services after unless you want to dig deeper - but it's a good start
As /u/pdr1017 said, you could also try this with SVG and a drop shadow filter.
Like in this (quick) example (try ~~it on desktop~~ to move the button around).
> then I'm left hanging for weeks or months before a decision is made whether or not to move forward
This is completely broken.
In terms of the git part of it, what you can do is create your feature branch, work on it, and occasionally rebase it on the master to bring it back up to speed with the rest of the codebase.
For Firefox users: the Firefox developer tools also have an excellent grid inspector that is very helpful in understanding CSS Grid.
> ~~Two of~~ my favorite regex tools: >
https://stackoverflow.com/questions/tagged/regex
I've tried learning regex a million times and I always forget it all within a week. Only thing I can ever remember is the simple s/replace_this/with_this/g
:(
Added Vue to my largish scale application a couple months ago. Been using 2.0 since rc6, and have no complaints. I love Vue. If you have been looking for a JS Framework to get into out of the thousands, definitely give Vue a look. The guide at vuejs.org/guide is great first place to start.
Personally, I think $70 is pretty reasonable for Sublime Text. I mean think about it, has it saved you roughly an hours worth of time total across all the times you've used it?
But if you don't think it's worth it you could:
• Use something else like Atom or Brackets
• Revert from your Time Machine back up (and if you don't have a backup system in place, you should re-evaluate your life choices)
I've been in a somewhat similar situation. First off, tell your boss that the deadlines aren't happening. They're trying to get all three points of the project management triangle, and it's not going to work. They need to compromise on something. While they're figuring that out, let's get to work.
Step one, if you haven't done this already, is to check everything into version control. You can't do anything about the past, but you can fix the future.
Working Effectively with Legacy Code is a well-reviewed book. Maybe you'll find it more useful than I did - ask your boss to buy it for you. My summary of it is:
You need a working test environment. The one the customer calls production is ideal (for you), but if that's not going to work, you need something as close to it as possible. It is management's job to solve this problem for you so you can do your job. Tell them that you're working with the 4-hr feedback window, and the more time they take to fix that, the longer this is going to take.
You mention that there's no documentation, and that you've read thousands of lines of code but still don't understand how it's pieced together. As you read the code, write the documentation. Be as extensive as you can. This is also a good time to write tests that verify the behavior you think is supposed to happen. And don't just read a file at a time, top to bottom - approach it always with a purpose, eg "how does this page get generated?". This will help you understand the flow, because you'll be tracing it repeatedly, so you'll start to see patterns in how it's all put together.
May the Force be with you.
Like most web designers and developers, I strongly recommend people never use GoDaddy!
There are tonnes more problems with GoDaddy not mentioned here, but... http://www.wikiwand.com/en/Go_Daddy#/Controversies
I use BrowserStack. They run virtual machines for you and transmit a video to you, screenshare-style. You can even route your local environment to their service.
Sure you setup your own virtual machines for somewhat better performance, but emulating the thousands of possible combinations of browser versions and OS versions isn't practical.
Vue is totally worth learning because there's less to learn than the alternatives.
Angular has an ocean of modules, declarations, providers, services etc. that suit itself better to enterprise systems interfaces. React is pretty simple on its face but gets kinda ridiculous once you realize project structure, class conventions, store/context APIs, are all over the place and everybody's "best practices" are so different that reading others' JSX becomes a game of sudoku. IMO, Vue minimizes all of this by drawing lines in the sand like where you should write markup vs computation.
BTW, if you don't wan't to download the dependencies, lemme also rep codesandbox for having the best prototyping experience on the block.
$2.12
I don't know what I was expecting, but I wasn't expecting that.
I use AWS for all the images on my website, because after doing some testing there was a notable difference in speed. I used the free tier for one year, then on November 1st, I started having to pay. I didn't really pay attention to the billing amounts in the past because I wasn't paying but I was expecting a much higher price.
Also notable, this is the biggest month I've in the history of my website, I hit the front page of Hacker News 3 or 4 times, and the front page of Lifehacker and Adafruit industries blog. Most of my days were around 5k uniques, with spikes up to 20k with the plugs from the big sites.
All I can say about this is if you're thinking of using S3 for your CDN to make your website faster and save hard drive space, don't let monetary cost be an obstacle. This is a hell of a bargain, that's why I'm sharing it today.
Digitalocean had a pretty good article about the history of Apache and Nginx, as well as some considerations to take that helped me when I was starting out. Link
PostgreSQL has phpPgAdmin: http://phppgadmin.sourceforge.net/doku.php?id=start
It also has a native Gui client: http://www.pgadmin.org/
PostgreSQL is the single most reliable piece of software I have ever used. I have used it as the back-end for my projects for over ten years. I have pounded it pretty hard, and have yet to be disappointed.
Edit: I have put it in situations where you would THINK data should get messed up, yet it never did. I have filled up drives, lost power, screwed up mount points etc. etc., and have never had anything -- ANYTHING -- get corrupted. This is in stark contrast to the other databases I have used.
This is the exercise mate. :) Try to make what OP did here using this API.
​
Want to make it a bit harder? Use localStorage to store the cities for future uses.
Even harder? Use Google Maps API to show your search locations and maybe Autocomplete for the search input
Realistically in terms of layout, it could be easily done using good ol divs. I had a brief moment during a break to try something for ya - bit loosey goosey but you could give something like this a shot (codepen). Without more info on what you're specifically trying to do I can't say anything more though, from what it sounds like you're probably looking for some kind of custom modal here. In regards to the images, you could easily set a background image in the divs, or offset things appropriately if you'd need icons or something along those lines here.
Note that there's a little more to this commit message than meets the eye:
>When and if WebKit implements Shadow DOM, we won't use these vestiges of the old code. Note that this checkin (and the earlier actual removal of the old implementation) are not a commentary on our long-term plans to support it or not. > > The checkin message is a series of inside jokes, which I see have confused many people. You can just interpret this as "remove some remnants of dead code, also I am a bit of a jokester". (Where "I" is the author of the patch, not me.)
(source)
Almost all your keyboard shortcuts are the same. Just swap out Cmd (⌘) for Ctrl. So, Copy is ⌘+C
and Past is ⌘+V
.
Most applications have their settings under Preferences and can be found by clicking the name of the app in the Menu Bar. A semi-universal shortcut is ⌘+,
.
The Menu Bar is the thing at the top of your screen. Think of it like the System Tray in Windows.
Your function key may not work as expected. You can alter their behavior under System Preferences -> Keyboard
. Same goes for most everything.
You'll probably miss window snapping. Install Spectacle. There might be others but that's what I use. Honestly, there is a little app for just about anything you need. And not just in the App Store. Most of the stuff I use is now from there.
iTerm2 is a ballin' replacement for the built in Terminal app. Install Homebrew. It's your package manager for system applications.
Learn to love Spaces. There are the bee's knees.
The best piece of advice I can give you is to drop the bullshit and learn the new tool your new job has given you. You're in good company. 80% of my company (software dev) uses a Mac. It's really developer friendly. Tons of open source stuff. Native terminal too.
Anyway - you'll totally be fine. Don't fight it. If you do you will hate it because it is not your native OS. Learn to accomplish the same things in ways that work for the OS. Or perhaps revisit your workflow. There might be better options.
I checked your domain's reputation on https://mxtoolbox.com (use the blacklist checker) and it comes up clean. The XYZ review process looks simple enough so just provide them with the results of your checks?
I guess it doesn't. However, there are other ways to determine whether you should preload content. Say if the click rate for that link is 95% or if the link is to the next part of a tutorial, then it's probably worth doing. Basically predicting what the user is going to do. You do have to watch out that the content you're loading isn't too big though, as mobile users don't want to waste their data.
Edit: I was wrong. reactjs.org uses Gatsby which apparently preloads anything that's in the viewport
Just got started! It looks like the 800+ hours is only necessary if you want to partner directly with a non-profit. There are solo projects you can tackle immediately upon joining – go to the "Map" link in the navigation and you can get to them.
Edit: also, holy shit – to whoever said that this site is only good if you're a beginner programmer: yes, there are a lot of tutorials for brand new programmers. But the projects? Oh my god, man.
For instance, "Build a Rougelike Dungeon Crawler in React." A project for which they tell you to "recreate the functionality of this CodePen." You can use whatever libraries or APIs you want, and you can design the game however you want – just keep the functionality the same.
Then, they provide you a Help chatroom on gitter to talk to the other students working on projects, and then let you get on with it. No further instructions, no more tutorials. "Build it."
This site is EXACTLY what I was looking for. THANK YOU
Try running any Google site through PageSpeed Insights, their own pages got abysmal scores across the board last I checked. Event their simple text based support pages.
Google is king at "do as I say not as I do" when it comes to web development. They are a total mess. They don't even use the same date format standards between Google Analytics and Google Search Console. Their documentation is often out of date as they make live functionality changes prior to updating their own documentation. They are, in general, simply too big and frankly too addicted to Agile style project management to run efficiently.
"<strong>Unused variable detection</strong>" is actually a pretty neat function. Up to this day this could be done only with some TypeScript extension and now integrated.
It'd also be cool to implement "Unreachable code detection" for a code that will never, under any circumstances, be reached. Something like this:
if(something) return true; else return false; i++; // this will never be reached so it's a garbage eating up precious kilobytes on my network
I don't believe you have to "open source" for Github Pages. You should be able to host a project with any license. For it to be free (including the account) then the code will have to be public, but not open source.
Let's Encrypt would be the same - https://letsencrypt.org/docs/certificate-compatibility/
But 30% users with WinXP... It really must be weird niche. XP doesn't even hit 2% on any of my sites, and great majority of them are on SP3.
https://isitblockedinrussia.com/?host=https%3A%2F%2Fapollopushserver.xyz%2Fapi%2Factive_products
The IP (range) of your (Digital Ocean) server appears to be blocked in Russia/UAE.
git makes a lot more sense when you see it in a GUI, when you can visualize and see the branches
try https://www.sourcetreeapp.com/
git made a lot more sense to me after this. then learn the CLI and it's way easier
His latest update to 3 was the 5th of May:
http://www.sublimetext.com/3dev
There is an explanation for the downtime here:
https://www.sublimetext.com/forum/viewtopic.php?f=2&t=15477&start=50#p58951
(bottom post, "kari", starting with: "From the Sublime office:...")
Good. I wonder, though, what happened to the objections they had about this having a negative impact on performance?
Edit: Ah, I just had to click through to the original announcement:
> Pointer Events as currently defined requires a hit-test on every pointermove (as is the case for mousemove, but not touchmove). This imposes a performance cost on the engine which the major native mobile platforms and browsers don’t have. I intend to work with the PEWG to identify some (probably breaking) API changes to allow us to avoid this cost for touch by default. This will be challenging to do without substantial compat pain, but I’m optimistic some solution can be reached to enable us to support Pointer Events without committing to this performance constraint.
Let's hope this will pressure Apple to support this web standard as well.
Edit: For those interested, see the original announcement that they weren't going to support it.
What a bunch of crap. For folks who are unitiatited, OP has drank a lot of Apple kool-aid and is just parroting the company's lines.
https://httptoolkit.tech/blog/safari-is-killing-the-web/
​
Here are some interesting bits.
>More specifically, Safari's approach isn't protecting the web from bloat & evil Google influence, because:
>
>- Most features that Safari hasn't implemented have no hint of security, privacy or performance concerns, and they've been implemented in every other browser already.
>
>- The largest Safari complaint is unrelated to experimental features from the Chrome team: it's the showstopping bugs in implemented features, made worse by Safari's slow release cycle.
>
>- Refusing to engage with the contentious API proposals for real use cases doesn't actually protect the web anyway - it just pushes web developers and users into the arms of Chromium.
Just wanted to mention that I stumbled upon another option recently: Supabase. It's basically Firebase, but open source if you care about that. The other thing that makes it different is it uses Postgres, so if you're a fan of relational DBs (Firebase uses Cloud Firestore, a NoSQL/non-relational DB), it's an option worth considering. If you don't care though, Firebase is much more mature & has a lot more functionality than Supabase.
Things that helped me:
GSAP is a sophisticated and established animation library. You can do a lot more with GSAP than you can with Anime, and Greensock is a better performing library as well.
Anime.js is the young upstart. It's a small library (~6kb) and it's got some talented devs behind it. Very promising future. That being said, GSAP is the industry standard and has a much bigger community and documentation base. I typically find myself reaching for GSAP.
Thimble is great for simple and fast prototyping etc. Used it a few years ago. Best thing is that you don't have to make all of your stuff public without paying money but some cool features are missing.
If you introduce them to React in 8th grade, show them https://codesandbox.io/!
It's not impossible (although 10-20k in your first year might be a bit of a stretch), its just that you've got to become proficient in so many different concepts and technologies.
If you're going to also design websites:
Basics for development:
Advanced functionality and deployment:
Then you'll also need to understand at least the basics of:
Anyone can make a pretty decent website using WIX/SquaredSpace/etc these days. This means that most business who go to a professional web designer/developer are looking for something that these DIY sites don't provide.
As you can see it takes a lot to create a sellable product these days and its only getting more difficult by the day. Don't let this discourage you though, just be sure to manage your expectations as it takes a lot of time and effort to start something from 0.
I suggest you get going with the basics of programming on https://www.freecodecamp.org/. In the meantime read up on the other items from the lists above and find tutorials on YouTube (don't buy any books, they're usually horribly outdated within a year of release).
You can also use fetch_all.
As for why - what if your table had millions of records? Or each row had a 16 MB blob. Most database engines in any language will return a cursor which you must iterate to yield results.
All of php string manipulation functions assume that all characters are 1 byte long. So functions like strlen will lie to you and substr will cut characters in half.
You have to use mulitibyte functions instead.
I posted this to /r/programming the other day and figured I would share it with the awesome /r/webdev community as well since there are many web development components.
>After Lastpass got acquired by LogMeIn last year I decided to start looking elsewhere. Being a software developer myself, I turned toward open source solutions but it immediately became apparent that nothing existed that was as convenient and as user friendly as Lastpass. I also realized that everyone seemed to charge money for these closed-source solutions (and rightfully so I suppose, a password manager is essential!). > >bitwarden was born from this search and I have been developing on it every night since. This week marks the complete 1.0.0 release of bitwarden! There are apps for iOS and Android on the stores, browser extensions for Chrome, Firefox, and Opera, and a convenient website vault. It's free, open source, and cross platform. > >Feel free to let me know any feedback that you may have or if you are interested in contributing in any way. You can check out the main product website at https://bitwarden.com/
http://developer.mozilla.org/ is your best reference.
Avoid any articles written by Microsoft.
Javascript: The Good Parts is not a teaching book. It's for those who know the language. Instead get "The Definitive Guide".
Put it in the <head> section and add the "defer" attribute.
https://developers.google.com/web/tools/lighthouse/audits/blocking-resources
I'm using a 13" non-retina MBP right now. I swapped out the mechanical drive for an SSD and installed 16GB of RAM and the thing's a webdev beast now.
EDIT: I'm surprised at the number of people installing servers directly on their Macs in this thread. Don't do that. Use a virtual machine - ideally with Vagrant and a provisioner so you can easily reproduce your dev environment. There are tons of pre-configured provisioner scripts out there for whatever sort of environment you'll be setting up if you don't want to spend time learning how to do it yourself.
Your dev environment should always be as close to your production environment as possible. Don't litter your dev machine with random versions of web servers, various databases, scripting languages, etc.
hyperpolyglot does seem like a good resource, but devhints appears to be far more relevant for web developers, e.g. includes ES6 syntax, react/enzyme/sass cheatsheets, repo more recently and frequently updated.
While not a cheatsheet, and just as flashy, devdocs.io was top of HackerNews yesterday - I could see myself using that over devhints due to the large collection of API docs, customizability (i.e. disabling docs for languages/libraries I don't use), and the ability to download docs for offline viewing.
Hello sir. Have you heard of our lord and saviour Version Control Systems?
Here's a tutorial for git and github:
https://www.youtube.com/watch?v=0fKg7e37bQE
Git is a command-line version control software. There are also graphical interfaces available such as git kraken
Github is the main remote repository that people use, however it is heavily geared towards open-source, with private repositories being a paid feature. You can use Bitbucket instead if you want free private repos.
I'd look into Wordpress with the BuddyPress plugin. Free, easy to set up, tons of themes for it, and tons of developers familiar with it in case you need a hand or want to give it to someone else to manage later.
Well that's annoying too, but im referring specifically to how vendors don't push updates for correct consistent implementations as they should.
An example would be flexbox.
Previously the only way people positioned elements on a page was using css positioning / floats (everyone remembers clearfixing the crap out of things right).
Flexbox was a long time coming, yet before the spec was fully ratified several browser versions were released supporting draft spec 2012 version.
Now several years later we currently have the situation we're facing now, where those same browser versions that implemented the draft spec either :
http://caniuse.com/#search=flexbox
Despite all of this devs are supposed to be the ones who write workarounds for this and are expected to provide comprehensive backwards compatibility / Xplatform support with extra CSS bloat and hacky workarounds and yet still achieve great performance for SEO, etc?
Bullshit.
Granted this is less significant for browsers that have a consistent release / update cycle to use a linux term "rolling release" type browsers, install once, keep upgrading because as you can see from the FF / chrome examples there have been many versions between now and back then bugfixed with full feature support thus providing backwards compatibility is not as difficult.
However it's highly relevant when discussing browsers that do not follow this release model or are less frequently updated (IE, Safari, Android browser).
It should be the vendors responsibility to recompile / patch and force upgrade their older versions of browsers so devs can write the CSS once. Not just declare the browser end-of-life and expect devs to provide 5 different browser prefixes and then still have to consider how the same syntax may or may not break in different versions of browsers.
> Benefits of including node_modules
in git:
>
> Reproducible builds. Guarantee that if you clone the repo on two machines, you’ll get the exact same code.
Worth mentioning that dependencies that are built using Native abstractions for Node.js (Node-API is the preferred way though) will, in fact, not work on two different machines unless they use the same OS, the same CPU arch and the same Node.js version. So yeah, I'd advise against sharing node_modules
.
If it's about a full-text search, then Sphinx is my go-to choice: small & native, super-fast, does only one thing — builds text indices and looks through them. Has a SQL-like query language, allows additional (non-searcheable) data in index, supports fuzzy search and suggestions. Worth a shot.
This is a setting in the web server. In Apache, for example, it's the DirectoryIndex directive: http://httpd.apache.org/docs/current/mod/mod_dir.html
By default, that is set to index.html. You could change it to whatever file you choose - index.php, script.cgi, or even bite.me.
It's useful to have a DirectoryIndex so that if someone doesn't explicitly choose a file (no one ever does when going to a web URL), it chooses the default file to display.
> Even though I still think it's a bad site overall, at least they are (sometimes) receptive to suggestions.
That vulnerability has been there for almost <em>eight years</em>. I reported it to them more than once and so did other people. I think "sometimes receptive" is vastly overstating how much they give a shit about fucking over newbies.
And like bravadomizzou said, you can't just wrap it in mysql_real_escape_string and be secure. That code is still a security hole waiting to happen.
The things people hate about PHP have been documented extensively. But as for alternatives, checkout Hack, built by Facebook. It's derived from PHP, but with some major improvements:
Data types
Hack allows data types to be declared. Not only does this help prevent bugs, but I'm far more productive with this because the autocomplete feature in my text editor becomes a lot more useful, because the text editor knows what data type is in each variable and can offer better suggestions for autocomplete.
Collections
One of my biggest gripes with PHP is how arrays are done. In PHP, an array can be a list of values like this: array('red', 'green', 'blue'); or a list of key/value pairs, like this: array('foo'=> 'bar', 'baz'=> 'blah');
That makes it confusing later in your code when you see an array. What format is the array? In Hack, there are different types of collections for each format. You get Vectors, which are like the first example, and Maps, which are like the second example, and they are typed to contain specific data types. You know exactly how to handle each one, because you know the structure and data types of the data it contains. Also cool is the ability to make the Map/vector immutable. So if the values aren't supposed to change, you can make it immutable to prevent accidental changes to the values.
Async
Most non-trivial web apps involve some third party API calls. These are time consuming requests over the network. Hack can do this asynchronously. That is, it can fire off the request, move on and do other things while it waits for the response, then catch the result.
Those are just some of the highlights. PHP7 is a major improvement, but still lacks some things I like about Hack.
The builtin CI service is really handy imo.
This has nothing to do with the quality of the product they offer, but I really appreciate the (seemingly) open culture in the company. They open sourced their employee handbook which gives you insight into what they think is important.
^^^imnotashill
Looks good! However, it seems like it falls apart if you give the background a color, and you'd kind of expect the "notch" to inherit the background color as well
https://codepen.io/anon/pen/oMRGOe
edit: seems like something like this https://codepen.io/anon/pen/Yjbrme (edited slightly from /u/Dutch_Mountain) works well!
Yeh I can relate, FWIW it does get easier with practice. But 100% agree that we’ve sort created as many problems as we’ve solved with modern JS.
there is a pushback happening with some newer frameworks like Astro.build trying to simplify things.
For React, if you haven’t tried Next.js, definitely give it a go, plenty of helpful documentation that could smooth things out for you.
I've been trying to up my CSS game lately and have been going through this starting with day 1 and trying to recreate each image without looking at the code.
If I'm stuck I'll go through and see how he did something and there have been a couple of times I've used more JS than I'd like to, but it's taught me a ton so far and I'm only about 15 'days' in.
just fyi, plain old ES + JSDoc comments (where required) gets you typing support in VS Code. You can also `npm i` typings for external libraries and still get the intellisense in vs code. I'm also pretty addicted to TS but one of the es6 projects I work on actually isn't so bad once we realized how much typing support we could get with just vs code and javascript. more info: https://code.visualstudio.com/docs/languages/javascript
First, having the new gTLDs take off would be a huge benefit to the OP and to us all. Why?
That said, here are my 2 cents. The reason trust is an issue is because spammers and phishers were known to take advantage of the cheap gTLDs (.biz) and country code TLDs (.tv, .us). It's a "once burned, twice shy" historical mistrust.
However, a bigger problem than trust is that the common public lacks awareness of new .gTLDs, and businesses/individuals don't know how to brand themselves for them yet. For example, the company Customer.io doesn't brand themselves as "Customer". They brand themselves as Customer.io. The full advertised name includes the ".io".
So, if I was a lawyer, I could create the domain punkrawk.attorney. However, I would have to find a way to brand myself with the attorney gTLD. Until there's a tipping point in new gTLD awareness, this will continue to be a problem, and .com will continue to be king.
https://www.netlify.com is another good option, free if you stay under 100GB of monthly traffic. It's very similar to GitHub pages (deploy vi push, custom domain, built-in CDN), but you can push your static files into it from GitHub, Gitlab, BitBucket, or simply uploading manually. They also have an optional one-click Let's Encrypt cert.
Here- https://angular.io/
It's just Angular now. The semantic versioning number is 4. It's informally called Angular 2 because it is the second generation of the framework. The previous generation is now referred to as AngularJs.
My favorite book like that: 24 hour course to master C++
Edit: to be fair the book doesn’t say “master”, but it is on the sixth edition.
WELCOME BACK to my channel and today we're, uhm, gonna learn... learn how to write HTML. If you like what you watch today and would like to be notified of, uh, future videos, please subscribe to my points below, like my video points below, and tell me what you think in the comments points below. As always thanks for tuning in. And if you want to watch more videos about programming, check out my channel below and if you like what you see here and would like to buy me coffee giggles then please consider donating through paypal or contributing through patreon! And before we begin, a quick word from our sponsor, NORDVPN pause looks for script. looks seriously at camera NordVPN is a PRIVACY-CENTRIC service that hides your online activity from strangers. It's especially helpful when you're at Starbucks doing your work that you want everyone to see you doing instead of just doing it at home where no one sees you. it also helps you get around content restrictions based on your uh geography, yeah, cause that aint cool. feel free to check out the link in the description for 5% off your first month. this video is also brought to you by dollar shave club, squarespace and wix. finally i'd like to thank my sponsors, MrYolo69, kodingiskewl, and Michael Smith for making me $15 richer per month. Thanks a bunch guys and without further ado, let's jump right in!
"Clean Code", "Structure and interpretation of computer programs", "The Pragmatic Programmer", "Design Patterns" and "Programming Pearls". These books are language agnostic and I believe that buying a book for learning a specific language is a waste of money. You will find the listed books in many top lists, so I'm not the only one who recommends them. :)
I can't remember where I saw it, but it was for a startup that was a private photo sharing service. So you'd create a group, share photos and only people in that group could interact and share their own stuff. Maybe somebody familiar with the app could point you to their blog?
Actually, found it: https://medium.com/on-coding/the-unexpected-costs-of-third-party-login-cda41c087653
Yup! Me and my cousin have been living from curiouscat.me ads for 8 months now. I barely make the minimum wage in my country, but since I'm 20 it's just enough for now
It started as a small fun project in April 2016. Since the whole point of the site is sharing it, we gained a lot of users really quick.
From the Raspberry pi FAQ:
>This means that graphics capabilities are roughly equivalent to the original Xbox’s level of performance. Overall real world performance is something like a 300MHz Pentium 2, only with much, much swankier graphics.
Yeoman for generating the skeleton file/folder structure of a new site.
We built our own generator, so we're able to when we need to build a new site, run one command:
yo foundation-site
Then it will ask a couple questions of what we want to include into the site, such as which Carousel, Header/Footer types, etc. Once all the questions are answered, it will create all the files and folders for the new site.
Go with a framework that you are comfortable with, Bootstrap or Foundation or another, each has their positive and negatives. It will save you alot of headaches.
Use a package manager, Bower and/or NPM, I've personally switched to only NPM, I used to use a combination of both, but just didn't need both now.
Use a builder, such as GruntJS or GulpJS for automating tasks
As for the CMS and what not, that all depends on the client and what's involved with the site.
I've been using Sync Pro on Android for a long while and love it (/r/redditsync/). I don't think they have an iOS app. If you have an Android device I would highly recommend it.
Even though they said they wouldn't do this, I'm pretty sure that at some point down the line they'll pull what Twitter did and change the terms of service for their API to make it basically impossible to have a third party app and force everyone to download the official reddit app. It's only a matter of time.
But honestly, restricting your access to reddit to only desktop is probably better for you in the end.
Seems to depend on if your company has any dealings with Australia
> They can also contain an individual if the person “develops, supplies or updates software used, for use, or likely to be used, in connection with: (a) a listed carriage service; or (b) an electronic service that has one or more end users in Australia.”
You can download Node directly from its website or use NVM for Windows if you want to be able to manage Node versions better.
Microsoft will be launching WSL2 and their new Terminal soon-ish. I haven't used WSL before, but it should allow for more Linux-ish workflow and for Linux programs to run. WSL2 is said to be a much improved version of it.
Vagrant boxes give you an environment that can be as close a match as possible to your eventual production environment. Immediate benefits:
All server side software is isolated there: Apache, nginx, mysql, php etc.
You can pollute that server environment with all sorts of experimental configurations and still easily return to a default state (e.g. try out using memcache)
Communities have created complex configurations that get you easily started with a new technology. (e.g. https://www.drupal.org/project/vdd provides a complete environment for drupal development all race ready)
Because the environment is easily rebuilt from a recipe, you can use lots of default user/pass for things like mysql etc...
Vagrant Share or ngrok will allow you to share a link to your VM to the outside world. Now you can share your work in progress with anyone without exposing a local setup (apache installed on your machine)
You share a directory with the vagrant box so that you can use phpStorm on your Mac (or whatever) and the vagrant box serves that directory from the VM
You are expected to know programming. Gone are the days of knowing just CSS and HTML. A competent front-end dev, even a junior, should know basic JavaScript (even if it's through a library like jQuery).
You should know the basics of version control software like git. Not a mastery of it, but the basics (checkout, commit, push, pull).
Resourcefulness and persistence. These are personality qualities that are hard to interview for, but are important to posses. Even if you don't know something, you should be able to figure out how to figure it out, and then figure it out (or figure out that it's likely beyond your experience to do, and thus know when to defer to a more senior developer). It's common for developers of any skill level to tackle problems they've never tackled before, and it's expected that they can do the research necessary to get it done.
Similar to #3, you know how to break down a problem into small, achievable bits so as to arrive at a solution one baby step at a time.
You'll want to be sure that you know how basic CSS works: cascading/inheritance, selector types, box model, positioning (i.e. you know the difference between IDs and classes, borders/padding/margin, relative vs absolute positioning etc)
Obviously HTML, but that's pretty basic stuff.
If all you need is the first packet (like trying to find the origin server of a website behind Cloudflare), then you can do it in a fraction of the time on a single machine.
https://github.com/robertdavidgraham/masscan
(Good defcon talk on masscan, but I cbf to google it)
Scenario : different browsers require different conventions for some css attributes. It's a huge pain to keep up with all of them so it would be great if there were a be tool to take care of all of that for us.
Bourbon for Sass used to do this for us which was alright. But they deprecated that functionality and advertise the use of Autoprefixer. Autoprefixer looks at all of your css (as output by sass) and will insert all the tedious browser prefixes for us.
So essentially we have the following
Sass code --> CSS code --> CSS code with Prefixes --> ...
Hence a pre-css stage, and a post-css stage.
Das Keyboard 4 Professional, Cherry MX Brown switches. Thing is a productivity beast.