Samsung Galaxy Note 8 Wifi Problem [SOLVED]

Filed under: — Aviran Mordo

So I got a new Samsung Galaxy Note 8, which is a pretty great gadget. I worked and installed all my favorite apps and everything was peachy.

At some point I got an OTN update to android 4.1.2 and ever since my Note 8 will not connect to my home wifi network. It will find all my neighbors wireless networks, but for some reason it will not find my own wifi SSID. Even when I stood less than one meter away from my wifi router it refused to find my network.

After browsing some forums some recommended to install wifi fixer apps, which I did (I had to use an access point while tethering from my phone), but it did not help.

Then another advice was to do a factory reset to the device, but still no change. It found all the surrounding networks, but not mine. I have to mention that all my other devices (laptops, phones, iPad and other wifi enable devices had no problems connecting to the network)

After almost giving up and sending the tablet to be fixed I went into the wifi router and looked at the settings. I remembered that few weeks ago I changed the default channel from being automatic to channel 13, in order to avoid collisions with the surrounding networks.
So in a last attempt I changed the channel to be auto and lo and behold my Galaxy Note 8 found my network.

I guess Samsung have some kind of weird bug that the wireless adapter will not work with channel 13. So now everything is good and I got back wireless connectivity on my Note. Too bad that I had to do a factory reset which caused me to lose everything I installed and configured for several hours.


Continuous Delivery - Part 7 - Cultural Change

Filed under: — Aviran Mordo

Previous chapter: Backward and forward compatibility

In order for continuous delivery to work the organization has to go a cultural change and switch to Dev-Centric Culture.

Continuous delivery gives a lot of responsibility in the hand of the developer and as such the developer need to have a sense of ownership. At Wix we say that it is the developer’s responsibility to bring a product / feature to production, and he is responsible from the feature inception to the actual delivery of the product and maintaining it on the production environment.

In order to do that several things have to happen.

Know the business :
The developer has to know the business and be connected to the product he is developing. By understanding the product the developers makes better decisions and better products. Developers are pretty smart people and they don’t need to have product specs in their face (nobody actually reads them). Our developers work together with the product mangers to determine what the product for the feature should be. Remember while the actual product may have several features bundled together for it to be valuable for the customer, we develop per feature and deploy it as soon as it is ready. This way both the product manager and the developer get to test and experience each feature on production (it is only exposed to them via Feature toggle) and determine if it is good enough, and may cause the direction of the product to change not according to plan, and actually develop a different next feature than the planned one.

Take ownership
Developers are taking ownership on the whole process, which means that they are the ones that need to eventually deploy to production. This statement actually changes the roles of several departments. What the company needs to do is to remove every obstacle in the developers way to deploy quickly on his own to production.

The operations department will no longer be doing the deployments. What they will do from now on is to create the automated tooling that will allow the developers to deploy on his own.
Operations together with dev will create the tooling to make the production environment visible and easy to understand to developers. Developers should not start a shell console (ssh) in order to view and know what is going on with the servers. We created web views for monitored metrics of both system and application metrics and exceptions.


Wix files registration statement with the SEC to go public

Filed under: — Aviran Mordo

Wixpress Ltd., a leading web development and design platform, commercially known as Wix.com, announced today that it has confidentially submitted a draft registration statement to the U.S. Securities and Exchange Commission for a possible initial public offering of its ordinary shares. The proposed offering is expected to commence after the U.S. Securities and Exchange Commission completes its review process, subject to market conditions and other conditions.

Being a Wix employee there is not much I can add to the official statement but congratulations to us ;-)

Powered by WordPress